exch

I'm using the same mapping as .20. That install still works as intended. Yea, I figured it might be a permission issue, but the entire KSP tree has RW permissions for my user. It's the same as the .20 install, which works correctly. I'll investigate further.

In the torrent of new support requests, It is difficult to find threads possibly related to my issues, so I decided to just plonk them down here, hoping someone has more insight into the issue itself, or at least where the relevant space to report them is located. This concerns a completely fresh install of KSP 0.21 on 3.9.9-1-ARCH #1 SMP PREEMPT Wed Jul 3 22:45:16 CEST 2013 x86_64 GNU/Linux No mods, or anything else added. Changing the mapping of the MODIFIER_KEY; the key that lets you copy parts in the VAB, call up the debug menu during flight, etc. By default, this is something like RightAlt. I've always mapped it to `TAB`, because my OpenBox installation maps Alt to certain windowing functions.. For some reason the change to the `settings.cfg` is ignored by the game and the key is therefore not remapped. Assigning Kerbals to a command pod from inside the VAB does not seem to persist. I can select whichever Kerbal I have available from the roster, but the game always ends up using Jeb when going into flight. This includes an explicit Save button press. When loading up a craft file, the ordering of the staging is not retained. I can re-arrange the staging, then save a craft. When reloading it back into the VAB, the staging is changed.