Corrupted quicksaves in devbuild

Forum rules
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.

Post a reply

Smilies
:D :) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :geek: :ugeek: :!: :?: :idea: :arrow: :| :mrgreen: :3: :wub: >:( :blergh:
View more smilies

BBCode is OFF
Smilies are ON

Topic review
   

Expand view Topic review: Corrupted quicksaves in devbuild

Re: Corrupted quicksaves in devbuild

by Boondorl » Sun Jul 27, 2025 9:42 pm

Looks like quick saves are instant unlike any other form of saving/loading in the engine. This means it's now saving out the player's predicted state which causes it to crash when it loads back in because none of the prediction data is saved out.

Edit: Yeah, quick save rotator was completely broken lol. Should hopefully be fixed soon.

Corrupted quicksaves in devbuild

by Xeotroid » Sat Jul 26, 2025 6:51 pm

Starting with devbuild gzdoom-x64-g4.15pre-349-g5bd8c7f3b, the game creates corrupted saves when using quicksave rotation. Manual saves appear to work fine. Older devbuilds also crash upon loading the corrupted saves. The wipe transition happens as normal, then the behaviour varies:
* The game crashes with a crash dump
* The game crashes without a crash dump
* The game doesn't crash immediately; the player has no weapons and can look around, any other input crashes the game with a crash dump
* I swear I've seen the player show up with only the fists that were positioned higher on the screen than they should once or twice before crashing
I've attached a crash report from the latest devbuild, gzdoom-x64-g4.15pre-408-g443e89975. This one is 26 kB. For some reason, -349 produces a 150kB report that's too big to upload here.
Attachments
CrashReport.zip
(26.21 KiB) Downloaded 2 times

Top