MantisBT - Zandronum
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0002589Zandronum[All Projects] Bugpublic2016-01-23 23:542016-01-24 13:19
ReporterFascistCat 
Assigned To 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionno change required 
PlatformMicrosoftOSWindowsOS VersionXP/Vista/7
Product Version3.0-beta 
Target VersionFixed in Version 
Summary0002589: Negative COMPATFLAGS value when setting 'Ignore Y offsets[...]'
DescriptionWhen you select 'Default' compatibility mode (hence COMPATFLAGS = 0) then you select the 'Ignore Y offsets on masked midtextures', COMPATFLAGS becomes -2147483648. When setting all other COMPATFLAGS except this flag in particular, COMPATFLAGS = 2147483647.
Steps To Reproduce1. Go to Compatilibity Options menu.
2. Set Compatibility Mode to 'Default' (or any other mode).
3. Set 'Ignore Y offsets on masked midtextures' to 'YES'.
Additional InformationUsing [ZandroDev3.0-151228-1140] build.
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2016-01-23 23:54FascistCatNew Issue
2016-01-24 00:01DuskNote Added: 0014167
2016-01-24 00:01DuskStatusnew => closed
2016-01-24 00:01DuskResolutionopen => no change required
2016-01-24 00:39FascistCatNote Added: 0014168
2016-01-24 00:39FascistCatStatusclosed => feedback
2016-01-24 00:39FascistCatResolutionno change required => reopened
2016-01-24 00:39FascistCatNote View State: 0014168: private
2016-01-24 00:39FascistCatNote View State: 0014168: public
2016-01-24 01:24DuskNote Added: 0014169
2016-01-24 01:25DuskNote Edited: 0014169bug_revision_view_page.php?bugnote_id=14169#r8512
2016-01-24 02:02FascistCatNote Added: 0014170
2016-01-24 02:02FascistCatStatusfeedback => new
2016-01-24 13:19DuskStatusnew => closed
2016-01-24 13:19DuskResolutionreopened => no change required

Notes
(0014167)
Dusk   
2016-01-24 00:01   
This is simply because CVars are signed integers. Setting that cvar causes the highest bit in compatflags to be set, which is also the sign bit. No bug here.
(0014168)
FascistCat   
2016-01-24 00:39   
Bitwise speaking it doesn't give problems at all with other flags enabled. But then shouldn't the value be expressed/displayed like an unsigned int? To avoid confusion when setting (and possibly share) compatibility options.

This issue is also present in gzdoom-g2.1.pre-1778-g1a63167.
(0014169)
Dusk   
2016-01-24 01:24   
(edited on: 2016-01-24 01:25)
All integer CVars are signed. You'll have to take it up with ZDoom if that's really a problem.
(0014170)
FascistCat   
2016-01-24 02:02   
Indeed, it's present in ZDoom latest beta build. Will re-evaluate the issue. This ticket can be closed. Thanks.