0002589: Negative COMPATFLAGS value when setting 'Ignore Y offsets[...]'

Chat on our Discord Server Get the latest version: 3.2
Source Code

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0002589

Zandronum

[All Projects] Bug

public

2016-01-23 23:54

2016-01-24 13:19

Reporter

FascistCat

Assigned To

Priority

normal

Severity

minor

Reproducibility

always

Status

closed

Resolution

no change required

Platform

Microsoft

Windows

OS Version

XP/Vista/7

Product Version

3.0-beta

Target Version

Fixed in Version

Summary

0002589: Negative COMPATFLAGS value when setting 'Ignore Y offsets[...]'

Description

When 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 Reproduce

1. 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 Information

Using [ZandroDev3.0-151228-1140] build.

Attached Files

Relationships

Notes
(0014167) Dusk (developer) 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 (reporter) 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 (developer) 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 (reporter) 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.

**Issue Community Support**
This issue is already marked as resolved. If you feel that is not the case, please reopen it and explain why.
Supporters:	No one explicitly supports this issue yet.
Opponents:	No one explicitly opposes this issue yet.

Issue History
Date Modified	Username	Field	Change
2016-01-23 23:54	FascistCat	New Issue
2016-01-24 00:01	Dusk	Note Added: 0014167
2016-01-24 00:01	Dusk	Status	new => closed
2016-01-24 00:01	Dusk	Resolution	open => no change required
2016-01-24 00:39	FascistCat	Note Added: 0014168
2016-01-24 00:39	FascistCat	Status	closed => feedback
2016-01-24 00:39	FascistCat	Resolution	no change required => reopened
2016-01-24 00:39	FascistCat	Note View State: 0014168: private
2016-01-24 00:39	FascistCat	Note View State: 0014168: public
2016-01-24 01:24	Dusk	Note Added: 0014169
2016-01-24 01:25	Dusk	Note Edited: 0014169	View Revisions
2016-01-24 02:02	FascistCat	Note Added: 0014170
2016-01-24 02:02	FascistCat	Status	feedback => new
2016-01-24 13:19	Dusk	Status	new => closed
2016-01-24 13:19	Dusk	Resolution	reopened => no change required

Questions or other issues? Contact Us.

Links

Doom and Doom II are the property of id Software.