You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For shits and giggles, I'm playing the Cosmogenesis mod, which is an insane slaughtermap wad. As expected I have died many times thus far and plan to do so many more times.
After one otherwise uneventful face rocket, the game itself face-rocketed and gave me this error:
I tried reloading my save a few times to no avail. I tried restarting the map to no avail. I switched to Sunlust, which... worked. But Cosmogenesis was still broken.
I deleted all the gy_ dictionary data from my config file and that did fix it. Is there perhaps some limit to gravestone amounts that can be stored for a map? Or did some value get corrupted? I kept a backup of that broken config in case it would be useful to examine it.
Playing with: GZDoom 4.8.2
Additional mods used: Target Spy v2.0.1
The text was updated successfully, but these errors were encountered:
I had the same crash happen last night with far fewer gravestones present on the map, so I don't think it's due to the amount. Going to see if I can figure out a way to reproduce the issue.
For shits and giggles, I'm playing the Cosmogenesis mod, which is an insane slaughtermap wad. As expected I have died many times thus far and plan to do so many more times.
After one otherwise uneventful face rocket, the game itself face-rocketed and gave me this error:
I tried reloading my save a few times to no avail. I tried restarting the map to no avail. I switched to Sunlust, which... worked. But Cosmogenesis was still broken.
I deleted all the gy_ dictionary data from my config file and that did fix it. Is there perhaps some limit to gravestone amounts that can be stored for a map? Or did some value get corrupted? I kept a backup of that broken config in case it would be useful to examine it.
Playing with: GZDoom 4.8.2
Additional mods used: Target Spy v2.0.1
The text was updated successfully, but these errors were encountered: