MantisBT - Zandronum
View Issue Details
0002604Zandronum[All Projects] Bugpublic2016-01-30 19:552018-09-30 21:42
Edward-san 
Edward-san 
normalmajoralways
closedfixed 
3.0-beta 
3.03.0 
0002604: Automap 'textured display' mode glitches with status bar
For some reason, when using the automap in 'textured display' mode, the status bar, except the mugshot, would be overwritten by the active sector when moving the display (follow mode off), as if the status bar were static.

Happens only with the software renderer. Doesn't happen in either GZDoom 1.8.6 or GZDoom 2.x git.
- load doom2 map01
- open the automap, with texture display on
- disable the follow mode
- use the 'up' key to move the visual such that the visible sector is put on the status bar.
See the attached screenshot.
No tags attached.
png Screenshot_Doom_20160130_205606.png (41,112) 2016-01-30 19:56
/tracker/file_download.php?file_id=1717&type=bug
png

txt sbarinfo.txt (4,334) 2016-02-06 01:25
/tracker/file_download.php?file_id=1727&type=bug
Issue History
2016-01-30 19:55Edward-sanNew Issue
2016-01-30 19:55Edward-sanFile Added: Screenshot_Doom_20160130_204820.png
2016-01-30 19:56Edward-sanFile Added: Screenshot_Doom_20160130_205606.png
2016-01-30 19:56Edward-sanFile Deleted: Screenshot_Doom_20160130_204820.png
2016-01-30 21:31WaTaKiDNote Added: 0014258
2016-01-30 21:33Edward-sanDescription Updatedbug_revision_view_page.php?rev_id=8607#r8607
2016-01-30 21:40DuskNote Added: 0014259
2016-01-30 21:40DuskStatusnew => confirmed
2016-02-06 01:25DuskFile Added: sbarinfo.txt
2016-02-06 01:26DuskNote Added: 0014328
2016-10-19 14:43Edward-sanNote Added: 0016059
2016-10-19 14:43Edward-sanAssigned To => Edward-san
2016-10-19 14:43Edward-sanStatusconfirmed => feedback
2016-10-19 15:28Edward-sanNote Edited: 0016059bug_revision_view_page.php?bugnote_id=16059#r9792
2016-10-20 00:19DuskNote View State: 0014259: private
2016-10-20 00:19DuskNote View State: 0014259: public
2016-10-29 22:40Edward-sanNote Added: 0016116
2016-10-29 22:40Edward-sanStatusfeedback => assigned
2016-10-29 22:40Edward-sanStatusassigned => feedback
2016-10-29 22:40Edward-sanOSUbuntu =>
2016-10-29 22:40Edward-sanOS Version14.04 x86-64 =>
2016-10-29 22:40Edward-sanPlatformLinux =>
2016-12-24 22:42DuskTarget Version => 3.0
2017-08-06 19:17DuskStatusfeedback => needs review
2017-08-07 18:23Edward-sanNote Added: 0018151
2017-08-07 18:23Edward-sanStatusneeds review => needs testing
2017-08-07 18:26Edward-sanNote Edited: 0018151bug_revision_view_page.php?bugnote_id=18151#r10858
2017-09-07 20:34DuskStatusneeds testing => resolved
2017-09-07 20:34DuskFixed in Version => 3.0
2017-09-07 20:34DuskResolutionopen => fixed
2018-09-30 21:42Blzut3Statusresolved => closed

Notes
(0014258)
WaTaKiD   
2016-01-30 21:31   
using:'https://www.dropbox.com/s/9yte408mrfkjmhs/zandronum-3.0-r150715-0725-4094854-windows.zip?dl=0 [^]'

i am unable to reproduce this, in neither ogl, software, nor with a fresh config
(0014259)
Dusk   
2016-01-30 21:40   
Confirmed on Ubuntu 15.04.
(0014328)
Dusk   
2016-02-06 01:26   
Torr pointed out the possibility that this would be due to the Zandronum HUD code. Indeed, using an SBARINFO patch works around the issue, see attached. It is just the stock sbarinfo/doom.txt with "base Doom" added.
(0016059)
Edward-san   
2016-10-19 14:43   
(edited on: 2016-10-19 15:28)
I managed to fix the issue with these changes:'https://bitbucket.org/zandronum/zandronum-sandbox/branches/compare/zandronum/zandronum-sandbox:f16bde4923c6%0DTorr_Samaho/zandronum:default [^]' . Please check that changeset f16bde4 works also in windows and in all game modes.

(0016116)
Edward-san   
2016-10-29 22:40   
WaTaKiD can reproduce the issue on windows with vid_hw2d off.
(0018151)
Edward-san   
2017-08-07 18:23   
(edited on: 2017-08-07 18:26)
Added a patch to Zandronum 3.0 upstream with this commit:'https://bitbucket.org/Torr_Samaho/zandronum/commits/f0e5871080e4 [^]' ( available in the new 3.0-alpha-170806-2040 ). Please check with your favourite wads!