MantisBT - Zandronum
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0003956Zandronum[All Projects] Bugpublic2021-12-23 09:212022-02-20 20:10
ReporterZalewa 
Assigned ToKaminsky 
PrioritynormalSeveritymajorReproducibilityalways
StatusresolvedResolutionfixed 
PlatformMicrosoftOSWindowsOS VersionXP/Vista/7
Product Version3.1 
Target Version3.2Fixed in Version3.2 
Summary0003956: +compatflags, +compatflags2 cmdline arguments broken in Zandronum 3.1
Description
Quote from WaTaKiD
upon further inspection, it seems the compatflags and compatflags2 fields dont work at all

regarding compatflags/compatflags2 i think this is a zan 3.1 regression

Steps To Reproduce1. Start Zandronum with: zandronum -host -iwad doom2.wad +map map01 +compatflags " -1" +dmflags " -1"
2. or with: zandronum -host -iwad doom2.wad +map map01 +compatflags 2 +compatflags2 2

In Zandronum 3.0 both of these set the flags as ordered.
In Zandronum 3.1 the dmflags are set, but the compatflags and compatflags2 aren't.

Additional InformationPreviously incorrectly reported as negative values not working: 0003949

Found by WaTaKiD here: 0003938:0021985 and 0003938:0021986

zacompatflags aren't affected.
TagsNo tags attached.
Relationships
related to 0003944closed Zalewa Doomseeker dmflags, dmflags2, etc, number fields dont accept negative values 
related to 0003949resolved Zalewa Zandronum The game ignores a negative value in "+compatflags -2147483648" command line argument 
Attached Filesjpg the_problem_is_worse_though.jpg (29,085) 2021-12-23 09:22
https://zandronum.com/tracker/file_download.php?file_id=2697&type=bug
jpg

jpg meanwhile_in_zan_3p0.jpg (53,613) 2021-12-23 09:22
https://zandronum.com/tracker/file_download.php?file_id=2698&type=bug
jpg
Issue History
Date ModifiedUsernameFieldChange
2021-12-23 09:21ZalewaNew Issue
2021-12-23 09:22ZalewaFile Added: zandronum_eval_flags_doesnt_really_work_either.jpg
2021-12-23 09:22ZalewaFile Deleted: zandronum_eval_flags_doesnt_really_work_either.jpg
2021-12-23 09:22ZalewaFile Added: the_problem_is_worse_though.jpg
2021-12-23 09:22ZalewaFile Added: meanwhile_in_zan_3p0.jpg
2021-12-23 09:22ZalewaRelationship addedrelated to 0003944
2021-12-23 09:23ZalewaRelationship addedrelated to 0003949
2021-12-23 09:25ZalewaSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=13499#r13499
2022-01-10 04:27KaminskyNote Added: 0022075
2022-01-10 04:27KaminskyAssigned To => Kaminsky
2022-01-10 04:27KaminskyStatusnew => needs testing
2022-02-20 05:38KaminskyTarget Version => 3.2
2022-02-20 17:15DrinkyBirdNote Added: 0022139
2022-02-20 20:10KaminskyStatusneeds testing => resolved
2022-02-20 20:10KaminskyFixed in Version => 3.2
2022-02-20 20:10KaminskyResolutionopen => fixed

Notes
(0022075)
Kaminsky   
2022-01-10 04:27   
The issue should now be fixed with this commit:'https://osdn.net/projects/zandronum/scm/hg/zandronum-stable/commits/5bd56174e3225b3e63f38ecaeb4305723cf1594b [^]'
(0022139)
DrinkyBird   
2022-02-20 17:15   
Tested using the given steps on the latest commit of zandronum-stable, and compatflags and compatflags2 were both set correctly.