by Nightfall » Tue Jul 14, 2015 3:42 pm
Consider the following example WADs: exit_test2.wad contains a map that flings the player through a corridor fast enough that the player trips two exit lines at the same time, causing the map to be exited twice.
This has some funny effects, such as UNLOADING scripts executed twice, as demonstrated by test_unloading.pk3 which prints a message inside an UNLOADING script. In this particular map the message is printed twice, while normally it is only printed once. On Zandronum it's also caused the map rotation system skipping maps and it's requiring gross hacks to fix.
I find that this double exiting is the root problem and should be fixed on ZDoom's end, if for no other reason, I really don't think that UNLOADING scripts should execute twice...
- Attachments
-
exit_test2.wad- (1.42 KiB) Downloaded 32 times
-
- test_unloading.pk3
- (927 Bytes) Downloaded 34 times
Consider the following example WADs: exit_test2.wad contains a map that flings the player through a corridor fast enough that the player trips two exit lines at the same time, causing the map to be exited twice.
This has some funny effects, such as UNLOADING scripts executed twice, as demonstrated by test_unloading.pk3 which prints a message inside an UNLOADING script. In this particular map the message is printed twice, while normally it is only printed once. On Zandronum it's also caused the map rotation system skipping maps and it's requiring gross hacks to fix.
I find that this double exiting is the root problem and should be fixed on ZDoom's end, if for no other reason, I really don't think that UNLOADING scripts should execute twice...