Project

General

Profile

Bug #3856

Settings file is being reset when launching a new instance of the game

Added by Baleine almost 10 years ago. Updated over 8 years ago.

Status:
Closed
Severity:
Low
Assignee:
-
Category:
Application
Target version:
-
Start date:
12/16/2014
% Done:

100%

Version:
Platform:
Linux
Expansion:
Language:
English (US)
Mod Related:
No
Votes:
Arrow u r green
Arrow d r red

Description

I open the game without a settings.cfg.
When I launch the game a standard settings is being created with read-write permissions for the current user (that is all right)

Go to settings and change some stuff (for example I set resolution to 1920x1080 and activated fullscreen)

Close the game and run it again.

Go to settings. At this precise moment, the settings.cfg is overwritten with standard settings info.


Related issues

Related to Kerbal Space Program - Bug #4918: Gamepad corrupts settings file / resets every time starting KSPClosed05/04/2015

History

#1 Updated by RexKramer almost 10 years ago

Are you clicking the Apply or Accept buttons before exiting settings?

#2 Updated by Baleine almost 10 years ago

Of course I saved the settings after the first changes.
I have edited the file to check its content and I saw the changes I made.

#3 Updated by Baleine almost 10 years ago

Okay, I've spotted the problem. It's purely a problem of locale

Here's an except of the player.log produced when I load the game :
KSP Version]: 0.90.0.0 (LinuxPlayer) BETA ====================================

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

FormatException: Unknown char: .
at System.Double.Parse (System.String s, NumberStyles style, IFormatProvider provider) [0x00000] in <filename unknown>:0
at System.Single.Parse (System.String s) [0x00000] in <filename unknown>:0
at AxisBinding.Load (.ConfigNode node) [0x00000] in <filename unknown>:0
at GameSettings.ParseCfg () [0x00000] in <filename unknown>:0
at GameSettings.Awake () [0x00000] in <filename unknown>:0

However, when setting environment variable LC_ALL=C, settings are properly loaded and shown in Settings scene.

I'm sorry. I should have checked the player.log previously.

#5 Updated by Squelch over 9 years ago

  • Status changed from New to Confirmed
  • % Done changed from 0 to 10

While I cannot confirm this directly, evidence from #4918#note-5 supports this, and it appears to affect Linux and OSX

#6 Updated by Squelch over 9 years ago

  • Related to Bug #4918: Gamepad corrupts settings file / resets every time starting KSP added

#7 Updated by kalle over 9 years ago

I have this problem on a fresh install from Steam on Linux.

Default locale is LANG=sv_SE.UTF-8

Export LC_ALL=C before launching steam resolves the issue. Maybe it's the locale's decimal comma that trips the parser?

#8 Updated by Baleine over 9 years ago

The easiest "fire and forget solution" if you launch the game from steam is to set the game launch options (accessible in game properties) to :
"LC_ALL=C command"

If not with steam, you can create a sh script to run the game.

Since the team doesn't seems to care about that locale minor issue, this ticket should probably be closed.

#9 Updated by Squelch over 9 years ago

Baleine wrote:

The easiest "fire and forget solution" if you launch the game from steam is to set the game launch options (accessible in game properties) to :
"LC_ALL=C command"

If not with steam, you can create a sh script to run the game.

That workaround is the recommended course of action for now.

Since the team doesn't seems to care about that locale minor issue, this ticket should probably be closed.

That is far from the case, and a read of the recent DevNotes will reveal localisations are being worked on.

#10 Updated by sal_vager almost 9 years ago

  • Status changed from Confirmed to Resolved
  • % Done changed from 10 to 100

This is resolved in the current build, 1028, as it was being caused by controller axis/button bindings throwing exceptions.

#11 Updated by TriggerAu over 8 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF