a savegame for immortal lock triggers a "vkWaitForFences failed" message during load <savegame>

[j4reporting]

save_issue774.zip

the savegame attached in issue #771 failes to load on 'newer'(?) HW.
the same savegame loads fine on an old Skylake NUC though.

Not in a local singleplayer game - can't fastload

vkQuake 1.32.0 Server (35659 CRC)

The Immortal Lock
Using protocol fte999
Warning: 2954 models exceeds QS limit of 2048 (max = 4096).
Allocating lightmap compute surface data (109893 KB)
Allocating acceleration structure data (374304 KB)
Allocating indirect draw data (105 KB, 5402 draws)
Allocating indirect IBs (45546 KB)
Allocating visibility buffers (424 KB)

ERROR-OUT BEGIN

Shutting down SDL sound

QUAKE ERROR: vkWaitForFences failed

fastload works:

skill 1
map immortal
fastload  <savegame>

attaching the savegame here as well

[j4reporting]

there is something strange going on.
ironwail 0.8 works, loads the savegame quickly and apparently plays w/o issue.

fastload on vkquake works but entities are totally wrong. I get attacked by hordes of ammo boxes :)
Also equipped weapon is not rendered correctly.

now the $1 million question, why does the savegame work correctly on my slow NUC with load BUT fastload produces the same bodged entities as on the newer faster HW?

[j4reporting]

The savegame has issues. Ironwail does not render items correctly it's just a white something.
User has updated immortal lock from version 1.7 to 1.9 and did not start over, but continued to play his old savegame.

[vsonnier]

skill 1
map immortal
fastload

Following these steps, I get the same bizzare items (everthing is a box !) you get, minus the Vulkan error. Maybe you found a strange corner case where fastload is actually erroneous. I've not found any other combination that works that way.

However as you mentioned there is a de-synchronization between the save (v1.7 ?) and the the actual map v1.9 so it is by nature invalid.

Unfortunatly, we can no longer run it with v1.7 (old version are normally accessible on Slipseer through "History") because it was hosted on Google Drive.

Feel free to close this if you wish.

[j4reporting]

I have the immortal 1.7 somewhere, but as he continued to play with 1.9 this save game is def. damaged.

Could it still be usefull to find some issues with the edict handling? "normal" load on my slow nuc works, but there is a strange NIN box moving up and down ( probably should be a flame?) right below you.
Shoudn't load and fastload have the same result?

Then there is the question why does it crash on faster hw.

[j4reporting]

Ah I forgot, I accidently already tried to load this savegame with version 1.7 and this fails with
Host_Error: Model *2830 not found