MantisBT - Zandronum |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0002504 | Zandronum | [All Projects] Bug | public | 2015-10-26 03:08 | 2018-09-30 22:12 |
|
| Reporter | StrikerMan780 | |
| Assigned To | Torr Samaho | |
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | |
| Platform | | OS | | OS Version | |
| Product Version | 3.0-beta | |
| Target Version | 3.0 | Fixed in Version | 3.0 | |
|
| Summary | 0002504: SkyPicker with 0 for TID doesn't use default sky. |
| Description | Setting the tag for SkyPicker to 0 is supposed to make the sky for that sector use the map default, and not use any SkyBox things. See:'http://zdoom.org/wiki/Classes:SkyPicker [^]'
Unfortunately, in 3.0, this broke. Now, it uses the first skybox thing with an ID of 0. |
| Steps To Reproduce | Make a map, give it a skybox with a skybox viewpoint of TID 0.
Make one sector with F_SKY1 as the ceiling, no special tags or skypicker objects in it. This will use the skybox as intended.
Now, make another sector, with F_SKY1 as the ceiling, and a Skybox Picker in it with the first Arg set to 0. Make sure it is set to apply to the ceiling.
The 2nd sky sector will use the skybox, when it shouldn't. |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | |
| Attached Files |  SkyTest.wad (6,172) 2015-11-01 13:58
/tracker/file_download.php?file_id=1674&type=bug |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2015-10-26 03:08 | StrikerMan780 | New Issue | |
| 2015-10-26 05:28 | StrikerMan780 | Note Added: 0013689 | |
| 2015-11-01 13:58 | Torr Samaho | File Added: SkyTest.wad | |
| 2015-11-01 14:04 | Torr Samaho | Note Added: 0013717 | |
| 2015-11-01 14:04 | Torr Samaho | Assigned To | => Torr Samaho |
| 2015-11-01 14:04 | Torr Samaho | Status | new => feedback |
| 2015-11-01 19:28 | StrikerMan780 | Note Added: 0013728 | |
| 2015-11-01 19:28 | StrikerMan780 | Status | feedback => assigned |
| 2015-11-01 19:36 | WaTaKiD | Note Added: 0013729 | |
| 2015-11-04 22:43 | StrikerMan780 | Note Added: 0013742 | |
| 2015-11-07 16:52 | Torr Samaho | Note Added: 0013747 | |
| 2015-11-07 16:52 | Torr Samaho | Status | assigned => feedback |
| 2015-11-08 00:55 | StrikerMan780 | Note Added: 0013749 | |
| 2015-11-08 00:55 | StrikerMan780 | Status | feedback => assigned |
| 2015-11-08 11:10 | Torr Samaho | Note Added: 0013752 | |
| 2015-11-08 11:10 | Torr Samaho | Status | assigned => feedback |
| 2015-11-25 13:09 | StrikerMan780 | Note Added: 0013878 | |
| 2015-11-25 13:09 | StrikerMan780 | Status | feedback => assigned |
| 2015-11-25 20:32 | Torr Samaho | Note Added: 0013879 | |
| 2015-11-28 09:52 | Torr Samaho | Note Added: 0013890 | |
| 2015-11-28 09:52 | Torr Samaho | Status | assigned => needs testing |
| 2015-11-29 20:16 | WaTaKiD | Note Added: 0013916 | |
| 2016-01-31 23:51 | Ru5tK1ng | Status | needs testing => resolved |
| 2016-01-31 23:51 | Ru5tK1ng | Resolution | open => fixed |
| 2016-01-31 23:51 | Ru5tK1ng | Fixed in Version | => 3.0 |
| 2016-01-31 23:51 | Ru5tK1ng | Target Version | => 3.0 |
| 2018-09-30 22:12 | Blzut3 | Status | resolved => closed |
|
Notes |
|
|
|
|
|
|
|
|
3.0 seems to work exactly like GZDoom 1.8.6 and the latest GZDoom git version, so it's (G)ZDoom bug. Can you confirm this? |
|
|
|
|
|
Where can I obtain a copy of 1.8.6? |
|
|
|
|
|
|
|
|
GZDoom 1.8.6 = Broken
GZDoom 1.8.0 = Broken
GZDoom 1.7.1 = Works |
|
|
|
|
|
As I said above, for me even the latest GZDoom git version is affected. If this is the same for you, please report the bug at the ZDoom or GZDoom forum (depending on whether this also happens in ZDoom). |
|
|
|
|
|
|
|
|
|
Thanks! Please leave a note when ZDoom has a fix for this. |
|
|
|
|
|
|
|
|
|
I backported the fixes from the GZDoom repo, but looks like the GCC fix for the fix is not in the GZDoom repo yet. |
|
|
|
|
|
The GCC fix for the fix is now also in the GZDoom repo and I backported it. |
|
|
|
|
|