Viktor Kvasnica

Members
  • Posts

    77
  • Joined

  • Last visited

Posts posted by Viktor Kvasnica

  1. On 1/27/2021 at 8:50 PM, UTC-10 said:

    Just thought I'd add a post that the update 1.93 solved the keybind problem. 

    I went back, put an older version of usercfg (that had had the problem) in line and got TLD to create an updated usercfg, and no problem with keybinds.  So it was fixed. 

    Thanks for the info, I am glad to hear that.

  2. 20 hours ago, UTC-10 said:

    With the above hint, I went back to my TheLongDarkNoSync folder, commented out the usercfg.69558 file and started the game.  Got in and *voila* the keybinds were what they should have been.  I went back to the TLDNS folder, looked and found a new usercfg.69558 file that exhibited two salient characteristics common to my earlier usercfg files (i.e. usercfg.69021) where my keybinds had held - file size 7,306 bytes and Modified Date of October 17, 2020.  

    The commented out usercfg file had 6,201 bytes and a normal modified date.  When the update occurred, that file had been about 1,000 bytes smaller. 

    I do not know what is happening other than now my keybinds do not reset.  I was surprised on the Hesitant Prospect update that the usercfg.69558 files that had been created had been about 5 K Bytes (and I lost badges I earned, got other badges I did not earn, and lost all my feats, and keybinds reset).  

    I just checked again.  The keybinds held but the badges and feats remain as they were changed during the Hesitant Prospect update. 
     

    As I know by far, the unlocked feats and completed challenges are stored in the profile file, not in the settings file. You might try to rename the whole "TheLongDarkNoSync" folder and let the game create new settings file (with all settings reverted to their respective default values).

    I had several settings files with different extensions/builds, one even without a build extension ("user001.cfg"). They all could be a source of some conflict. I had only one settings file "usercfg.69021" afterwards.

    I tested the new Hesitant Prospect update now: key bindings were set to defaults again; feats and challenges were as I remembered; I have a new "usercfg.69558" settings file (besides the "usercfg.69021"). New key bindings are saved properly to the new settings file "usercfg.69558".

  3. On 12/6/2020 at 5:24 PM, peteloud said:

    I followed your suggestion and it seems to be saving the new keybind.  I saved, exited and retarted a couple of times and it was still keeping the new keybind. 

    My sound level seem to have been changed.  I don't know if this is anything to do with the new changing the keybind. It is a problem which seemed to appear with the recent updates.  I haven't checked it out properly so it could be something completely different.

    I am glad it helped you too.

    Regarding the sound level problem... The game created settings file with all settings set to their default value, thus the audio levels will be default too. You can check the in-game audio settings if they are set properly as you need them to be.

  4. Hi folks,

    same problem here after the v1.88 hotfix (build 69021).

    After reading a couple of associated topics, I have managed to solve this issue by renaming the "TheLongDarkNoSync" folder to "TheLongDarkNoSync.bak" (in "...\AppData\Local\Hinterland\") - thus creating a backup copy of this folder and letting the game create a new one with the settings file. The key bindings are properly saving now.

    Vic

    • Upvote 3
  5. Hi folks,

    same problem here after the v1.88 hotfix (build 69021).

    After reading a couple of associated topics, I have managed to solve this issue by renaming the "TheLongDarkNoSync" folder to "TheLongDarkNoSync.bak" (in "...\AppData\Local\Hinterland\") - thus creating a backup copy of this folder and letting the game create a new one with the settings file. The key bindings are properly saving now.

    Vic

    • Upvote 1
  6. Hi folks,

    same here. And such a good progress it was: day 8, tons of food, very good and repaired clothing (warmth bonus 14 °C), steadily gaining sustainability, survived supply-run to the Dam (got surprised by the wolf, freezing and over-weighted, had to make emergency fire in the upper cave and made it to the Camp Office during freezing and windy night, barely)... I lost about hour or so and have an automatic backup (regular backup via Acronis). The good side of this is I have been given a second chance returning from the damn Dam. :) Looking forward to get this fixed though.