MantisBT - Zandronum |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0002093 | Zandronum | [All Projects] Bug | public | 2015-02-07 16:51 | 2018-09-30 21:42 |
|
Reporter | Konda | |
Assigned To | | |
Priority | low | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | |
Platform | | OS | | OS Version | |
Product Version | 1.3 | |
Target Version | 3.0 | Fixed in Version | 3.0 | |
|
Summary | 0002093: Taking away PowerTimeFreezer from the player causes the colormap from another powerup to disappear and reappear after a moment |
Description | If you take a powerup that uses a colormap (like the invulnerability sphere), and also take a powerup which gives PowerTimeFreezer (like the time freeze sphere), and then remove PowerTimeFreezer from a player via an ACS script, the colormap of the invulnerability sphere (or any other powerup with a colormap) will disappear for a very short period of time and reappear. |
Steps To Reproduce | I made an example map where you reproduce the bug:
1. Go to MAP01
2. Take the invulnerability sphere
3. Take the time freeze sphere
4. Press the switch |
Additional Information | The example wad contains the time freeze sphere sprites so you don't need to load skulltag_data with this example wad.
The switch in the example map executes an ACS script that takes away PowerTimeFreezer from the player.
I think this bug is OS-independent because along with Windows 8.1, the same bug appears when I'm using Arch Linux. |
Tags | No tags attached. |
Relationships | |
Attached Files | timefreezertest.wad (10,531) 2015-02-07 16:51 https://zandronum.com/tracker/file_download.php?file_id=1406&type=bug
timefreezertest_gz.wad (10,906) 2015-02-07 17:43 https://zandronum.com/tracker/file_download.php?file_id=1407&type=bug |
|
Issue History |
Date Modified | Username | Field | Change |
2015-02-07 16:51 | Konda | New Issue | |
2015-02-07 16:51 | Konda | File Added: timefreezertest.wad | |
2015-02-07 17:28 | Konda | Note Added: 0011605 | |
2015-02-07 17:32 | Konda | Note Added: 0011606 | |
2015-02-07 17:32 | Konda | Note Deleted: 0011606 | |
2015-02-07 17:32 | Konda | Note Edited: 0011605 | bug_revision_view_page.php?bugnote_id=11605#r6581 |
2015-02-07 17:36 | Konda | Note Edited: 0011605 | bug_revision_view_page.php?bugnote_id=11605#r6582 |
2015-02-07 17:38 | Edward-san | Note Added: 0011607 | |
2015-02-07 17:39 | Edward-san | Note Edited: 0011607 | bug_revision_view_page.php?bugnote_id=11607#r6584 |
2015-02-07 17:42 | Konda | Note Edited: 0011605 | bug_revision_view_page.php?bugnote_id=11605#r6585 |
2015-02-07 17:43 | Konda | File Added: timefreezertest_gz.wad | |
2015-02-07 17:44 | Konda | Note Added: 0011608 | |
2017-07-15 17:23 | Konda | Note Added: 0018040 | |
2017-07-15 17:26 | Konda | Note Edited: 0018040 | bug_revision_view_page.php?bugnote_id=18040#r10781 |
2017-07-15 23:34 | Ru5tK1ng | Status | new => resolved |
2017-07-15 23:34 | Ru5tK1ng | Resolution | open => fixed |
2017-07-15 23:34 | Ru5tK1ng | Fixed in Version | => 3.0 |
2017-07-15 23:34 | Ru5tK1ng | Target Version | => 3.0 |
2018-09-30 21:42 | Blzut3 | Status | resolved => closed |
Notes |
|
(0011605)
|
Konda
|
2015-02-07 17:28
(edited on: 2015-02-07 17:42) |
|
I forgot to add a few more details:
1. This bug also appears in multiplayer
2. This bug doesn't appear in GZDoom 323, though I had to add the Decorate definition of the time freeze sphere to the example wad before running it with gzdoom
3. This bug appears in the latest testing build for Zandronum 2.0 (150118-1152)
4. This bug doesn't appear in GZDoom 900
5. In Zandronum 2.0 (150118-1152) multiplayer, sometimes the bug appears, and sometimes it doesn't
|
|
|
(0011607)
|
Edward-san
|
2015-02-07 17:38
(edited on: 2015-02-07 17:39) |
|
Can you provide the example wad with the time freeze decorate definition?
|
|
|
(0011608)
|
Konda
|
2015-02-07 17:44
|
|
Done. timefreezertest_gz.wad contains the decorate definition. |
|
|
(0018040)
|
Konda
|
2017-07-15 17:23
(edited on: 2017-07-15 17:26) |
|
ok I tried this in 3.0-alpha-r170709-2004 and the issue is gone, thanks for the effort and dedication guys much appreciated
edit: the issue was still present in 2.1.2
|
|