[Awesome 0.90 gameplay video with music]

Some terrific eye candy from Beta all-stock gameplay, montoged over a tUnE-yArDs track. VTOLs, SSTO planes, Mk3 Shuttle Systems, Duna aircraft, landers, space stations, ground bases, dancing Kebals...you name it.

Hope you enjoy!

[Access violation]

I'm having this same issue. Trying a (second) clean install after manually deleting the KSP steamapps directory. Will try with read-only and report back with logs.

After new install - first launch was from steam. Made no settings changes. Created a career mode game. Clicked research building and exited, clicked mission control building and exited, clicked VAB and crashed on load. All subfolders in KSP dir are read only.

No error log was generated by KSP. The windows exception threw:

Problem Event Name: APPCRASH

Application Name: KSP.exe

Application Version: 4.5.2.26843

Application Timestamp: 53bac1e4

Fault Module Name: StackHash_9412

Fault Module Version: 6.3.9600.17114

Fault Module Timestamp: 53648f16

Exception Code: c0000374

Exception Offset: PCH_32_FROM_ntdll+0x000735D4

OS Version: 6.3.9600.2.0.0.256.48

Locale ID: 1033

Additional Information 1: 9412

Additional Information 2: 9412035320650541430a04df3fd15444

Additional Information 3: e944

Additional Information 4: e944766475f9417af6648122c8da6800

which isn't very helpful.

Next I tried deleting settings.cfg and launching from KSP.exe. Game loads, clicked VAB...no crash this time, but graphics don't load properly. Turned off antialiasing and lowered render and texture settings. No improvement, outside a comforting pixelated patina. Guessing at where the controls were, I was able to build a little ship and launch it. Physics hit okay...in fact things worked well except for some unexpected behavior with the inertial path reticule. Decided to try to go full screen and raise the render quality a bit. Game didn't crash but monitor lost input until I opened task manager. Forced a quit, no error logging of any kind.

Downloaded and installed GeForce 344.11 drivers for my GTX 560. Deleted settings.cfg and launched from KSP.exe. Same issues. Exiting the VAB crashed the game and threw a KSP error log this time though:

Unity Player [version: Unity 4.5.2f1_9abb1b59b47c]

KSP.exe caused an Access Violation (0xc0000005)

in module KSP.exe at 001b:00685c7d.

Error occurred at 2014-10-09_224218.

C:\Program Files\Steam\steamapps\common\Kerbal Space Program\KSP.exe, run by Arophon.

91% memory in use.

3309 MB physical memory [277 MB free].

0 MB paging file [487 MB free].

2048 MB user address space [61 MB free].

Write to location 00000000 caused an access violation.

Context:

EDI: 0x00122524 ESI: 0x7e4d071c EAX: 0x0000244a

EBX: 0x00000000 ECX: 0x00000000 EDX: 0x00000024

EIP: 0x00685c7d EBP: 0x09ccf680 SegCs: 0x0000001b

EFlags: 0x00010212 ESP: 0x09ccf650 SegSs: 0x00000023

Bytes at CS:EIP:

66 0f 7f 01 66 0f 7f 41 10 66 0f 7f 41 20 66 0f

[Access violation]

I'm having this same issue. Trying a (second) clean install after manually deleting the KSP steamapps directory. Will try with read-only and report back with logs.

[Show off your awesome KSP pictures!]

I've long enjoyed this thread, so it's time to contribute. A friend and I compare KSP missions and designs, but the screenshot function on Linux has a tendency to crash the game, so I've just been snapping shots on my iPhone and uploading them to iCloud. Sometimes the interference is annoying, but occasionally the shot looks more "real" than a screenshot, somehow. Enjoy! https://www.icloud.com/photostream/#A8JtdOXmGa4uOi

[The Linux compatibility thread!]

After the 'change two bits' fix, I haven't run into a mod that hasn't worked, actually. I'll edit that post.

Can you (or someone) link where you found that 'change two bits' fix? I have no idea what you're talking about and searching the forums just points back to this thread.

Specifically I'm trying to get the Troublemaker life support and crew transfer mod to work on linux, although I would also be interested in recommendations for other life support mods.

Thanks (and thanks for the hilo/Hilo tip).

[The Linux compatibility thread!]

it's not clear, but sounds like you're copying the DLL files in to .local/share/Steam/SteamApps/common/Kerbal Space Program/Plugins/ ? That was how plugins were installed in previous versions, but 0.20 moved a lot of things around.

Now, all of a plugin's files live in a plugin-specific directory under .local/share/Steam/SteamApps/common/Kerbal Space Program/GameData .

That was exactly it, thanks stibbons for being so perceptive.

The threaded optimizations for my Nvidia seems to help as well, although it's not dramatic.

[The Linux compatibility thread!]

As promised a bit earlier up the thread, a list of mods that work with KSP.x86_64 (ver 0.20.2):

Working mods:

Mechjeb 2.0.8

SubAssembly (with fix found on the forums)

KSP Stock Part Expansion (KSPx)

H.O.M.E. 1.0.3

B9

Crew Manifest

Tri-Struts

Hyper-Edit

Kethane

Haystack

Quantum Struts

Common Berthing Mechanism

Thanks for the list. All of the parts images associated with the above do work on my Fedora. A couple of them are not "selectable" in the VAB editor, but this probably not the place for that conversation.

What I actually need is a better understanding of how the plugin .dll files are supposed to work with KSP for linux (I don't need any flak for using the "worst" distro, I've got it all tuned up and I don't feel like starting over right now). It didn't surprise me that just moving the .dll into the plugins directory didn't give me any game functionality, but it did interest me that there was not a good guide to installing plugins on linux.

My Crew Manifest, for example, doesn't work with the plugin files in the plugins directory. I noticed they included the source files. I am using the Steam KSP install, 64-bit, nVidia drivers.