Zandronum Chat @ irc.zandronum.com
#zandronum
Get the latest version: 3.0
Source Code

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0002781Zandronum[All Projects] Bugpublic2016-07-14 03:202016-08-21 07:26
ReporterTiger 
Assigned To 
PrioritynormalSeverityminorReproducibilityalways
StatusnewResolutionopen 
PlatformDesktopOSMicrosoft WindowsOS VersionWindows 10
Product Version2.1 
Target VersionFixed in Version 
Summary0002781: Invasion Spawner fails if sector height changes
DescriptionIf a sector reference height changes during the count down phase, the invasion spawner will never spawn the creature\THING. In addition, the same outcome will occur if changing the Z-Height level of the invasion spawner to match with the sector reference's height.


Using: Zandronum 3.0-alpha-r160703-1614
File Attached: 7Zip using PPMd algorithm
Steps To ReproducePlace Invasion Spawner on a sector reference that is scripted to 'Floor_RaiseByValue()' via ACS. When the sector's height changes and the appropriate wave is set for that spawner to activate, the spawner simply will fail and stuck with an impossible way to finish the map if the monster is stuck in limbo.
Additional InformationI have attached a test PWAD that demonstrate this effect. I have three 'Doom Imp' Invasion Spawners and two unique sector references.
* First, the far left side, the Imp will spawn on the traditional parent height of '0'. The Doom imp will spawn just fine at this location.
* Second, middle, the sector is raised (static) to 24 Map Units which also contains a Doom imp spawner, the invasion spawner will work with no changes from the spawner from the far left.
* Lastly, the far right - contains a scripted sector reference that raises by a certain value which also contains an Invasion spawner. The spawner at this side will fail to execute.
Attached Files7z file icon ImpTest.7z [^] (2,037 bytes) 2016-07-14 03:20

- Relationships

-  Notes
User avatar (0015507)
Tiger (reporter)
2016-08-20 18:19

To further add, I have ran another test on SkullTag 97b - which required me to modify the provided PWAD, the bug also occurs there as well.

So this has been in issue since forever.

Issue Community Support
Only registered users can voice their support. Click here to register, or here to log in.
Supporters: mifu
Opponents: No one explicitly opposes this issue yet.

- Issue History
Date Modified Username Field Change
2016-07-14 03:20 Tiger New Issue
2016-07-14 03:20 Tiger File Added: ImpTest.7z
2016-08-20 18:19 Tiger Note Added: 0015507
2016-08-21 07:26 Torr Samaho Product Version 3.0-beta => 2.1






Questions or other issues? Contact Us.

Links


Copyright © 2000 - 2018 MantisBT Team
Powered by Mantis Bugtracker