Kerbal Space Program

When you get the "reset settings every time" problem you have to delete the settings.cfg to make it go away. Preferably from a backup of course.

This is on English Win 8.1 64bit using Steam version of KSP 1.0.2

(I hope the Edit button does what I think it does.)

I experience the same bug. Fresh startups are fine, but any startup after I set axis bindings is problematic. All settings and bindings are lost (though resolution is correct, so the corruption occurs after that is set), and attempting to bind any axes permanently breaks the Settings screen.

The difference for me is that I'm using a CH Products flight yoke and pedals, not a gamepad. Also worth mentioning, my devices' names end in spaces ("CH PRO PEDALS USB " and "CH FLIGHT SIM YOKE USB "), and the settings.cfg file format appears... inadequate for dealing with this.

Deleting settings.cfg makes the next startup work. It's annoying (but workable, technically) to have to do this every time. I've attempted (unsuccessfully) to "salvage" settings.cfg by deleting sections, but only after it has already been further corrupted by KSP starting up and breaking.

I am on Windows 7 and using the non-Steam version of KSP 1.0.2.

Same here with the Mac version (v1.0.2.842). All kinds of settings are messed up, for example the VAB and in flight camera sensitivity, which makes playing pretty much impossible.

This bug seems to be locale related. settings.cfg diff excerpt:

-VAB_CAMERA_ORBIT_SENS = 0.04
-VAB_CAMERA_ZOOM_SENS = 0.1
-FLT_CAMERA_ORBIT_SENS = 0.04
-FLT_CAMERA_ZOOM_SENS = 0.5
-FLT_CAMERA_WOBBLE = 0.1
-FLT_CAMERA_CHASE_SHARPNESS = 1.5
+VAB_CAMERA_ORBIT_SENS = 0,04
+VAB_CAMERA_ZOOM_SENS = 0,1
+FLT_CAMERA_ORBIT_SENS = 0,04
+FLT_CAMERA_ZOOM_SENS = 0,5
+FLT_CAMERA_WOBBLE = 0,1
+FLT_CAMERA_CHASE_SHARPNESS = 1,5

Node the dots that are replaced with commas.

Edit: It's a locale issue (I'm on a Mac/German locale). If I start KSP with

$> LC_ALL=C "/Users/xxx/Library/Application Support/Steam/SteamApps/common/Kerbal Space Program/KSP.app/Contents/MacOS/KSP"

all settings (gamepad + cameras etc) work as expected.

[email protected] wrote:

This bug seems to be locale related. settings.cfg diff excerpt:

-VAB_CAMERA_ORBIT_SENS = 0.04
-VAB_CAMERA_ZOOM_SENS = 0.1
-FLT_CAMERA_ORBIT_SENS = 0.04
-FLT_CAMERA_ZOOM_SENS = 0.5
-FLT_CAMERA_WOBBLE = 0.1
-FLT_CAMERA_CHASE_SHARPNESS = 1.5
+VAB_CAMERA_ORBIT_SENS = 0,04
+VAB_CAMERA_ZOOM_SENS = 0,1
+FLT_CAMERA_ORBIT_SENS = 0,04
+FLT_CAMERA_ZOOM_SENS = 0,5
+FLT_CAMERA_WOBBLE = 0,1
+FLT_CAMERA_CHASE_SHARPNESS = 1,5

Node the dots that are replaced with commas.

Edit: It's a locale issue (I'm on a Mac/German locale). If I start KSP with

$> LC_ALL=C "/Users/xxx/Library/Application Support/Steam/SteamApps/common/Kerbal Space Program/KSP.app/Contents/MacOS/KSP"

all settings (gamepad + cameras etc) work as expected.

Nice find , and thank you. I will promote this to the Devs for attention. Could you please raise this as a new issue with reproduction steps? I'm assuming this affects Linux 'Nix only platforms, but this needs to be verified.

Starting the game with missing axes from a prior game session is known to cause issues too, so this new finding while related, is not necessarily the cause of this problem.

Having your settings corrupt on you irreversibly when you start KSP with a wireless gamepad (or wireless joystick I presume) asleep is a "normal" priority?

I'd say anything that messes your game badly enough to warrant deleting configuration files is somewhat bigger problem than that.

And, yes, the important thing to bear in mind here is that the wireless things will turn off automatically to save batteries so there's a pretty good chance they're off when user starts KSP.

Here's a workaround until this is fixed:
If you forget to wake up your gamepad in advance and KSP corrupts your config, exit KSP by ALT-F4 (or equivalent) and the corrupted settings will not be written to disk. Then everything will be OK the next time you start KSP.

Provided you woke up your controller of course.