Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • EDuke32 EDuke32
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 96
    • Issues 96
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Richard Gobeille
  • EDuke32EDuke32
  • Issues
  • #163

Closed
Open
Created Jul 05, 2021 by Dino Bollinger@dibollingerDeveloper

Engine: Settings changes are discarded on game crash (or when terminating the process)

This has been a thorn in my side for as long as I can remember using eduke32, all the way back to the mid-2000s

Basically, if you change any settings, like the volume, resolution, keybindings, you name it, and the game happens to crash, all of it will be reset to the previous values when you next launch the game. This can lead to the user having to redefine all his settings every session if said sessions happen to end with crashes.

This occurs because the eduke32.cfg and settings.cfg files are only written if the game closes normally. It should either be updated immediately on changing the settings, or there should be a handler, if possible, that can write to these files if a crash occurs. (though the latter is impossible if one kills the process, so I suggest immediately persisting the settings if they differ)

Fixing this would be a huge boon to everyone who happens to encounter a crash. Almost everybody who first launches the game is not going to close it immediately after changing the settings, making this situation highly likely. This applies to eduke32, VoidSW, Ion Fury, and any mod that runs on eduke32.

Edited Jul 05, 2021 by Dino Bollinger
Assignee
Assign to
Time tracking