 |
I figured out how to reproduce the effect and I know what causes it. Load the test file and start a new game. Then do ChangeMap to another map, can be any. Bam. Instant freeze after the melting screen is gone. What causes it? At the top of the ZScript file, you'll see there's a CVar type object defined. If you comment that out, it won't freeze anymore. Also, the cvar test is not invoked at all -- there's no calls to it, or anything. test.pk3 (2,386 bytes) |
|
|
FYI, the problem is that any variable in a serialized class muxt be a serializable type or be declared transient. I guess this will require a compile time check at least for all subclasses of Thinker which have to be fully serializable. But that's for later. I think fixing the freeze is the more important issue for now. |
|
|
Agreed. I don't see any harm requiring the transient flag for now, as we can store the results straight to string/float/color/ints easily enough. |
|
|
My lame attempt to fix the freeze was to add I_FreezeTime(false); line to D_ErrorCleanup() function. Although it won't fly because I_FreezeTime() calls must be balanced. Found no way to do so with the existing interface. Platform specific backend needs to report time frozen state somehow. Or probably we should remove the balance requirement. |
|
|
This cannot fall through to D_ErrorCleanup. It must be caught at a higher level so that proper cleanup of the serializer can be done. |
- Anonymous
