MantisBT - Zandronum |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0003949 | Zandronum | [All Projects] Bug | public | 2021-12-19 12:42 | 2021-12-23 10:14 |
|
Reporter | Zalewa | |
Assigned To | Zalewa | |
Priority | normal | Severity | minor | Reproducibility | always |
Status | resolved | Resolution | invalid | |
Platform | Microsoft | OS | Windows | OS Version | XP/Vista/7 |
Product Version | 3.1 | |
Target Version | | Fixed in Version | | |
|
Summary | 0003949: The game ignores a negative value in "+compatflags -2147483648" command line argument |
Description | Passing +compatflags -2147483648 as a command line argument should enable the compat_maskedmidtex compat flag. It doesn't:
- compatflags are 0
- compat_maskedmidtex is false
If "compatflags -2147483648" is set from the console, the game accepts it just fine, so it appears that only parsing the command line is broken. |
Steps To Reproduce | 1. Run "zandronum.exe -iwad doom2.wad +map map01 +compatflags -2147483648". |
Additional Information | The dmflags, compatflags and zaflags are all signed 32-bit integers. The compat_maskedmidtex is the only flag that uses the most significant bit of a 32-bit integer. |
Tags | No tags attached. |
Relationships | related to | 0003956 | resolved | Kaminsky | Zandronum | +compatflags, +compatflags2 cmdline arguments broken in Zandronum 3.1 | related to | 0003944 | closed | Zalewa | Doomseeker | dmflags, dmflags2, etc, number fields dont accept negative values |
|
Attached Files | zandronum_eval_flags_doesnt_really_work_either.jpg (150,812) 2021-12-23 09:08 https://zandronum.com/tracker/file_download.php?file_id=2693&type=bug

the_problem_is_worse_though.jpg (29,085) 2021-12-23 09:11 https://zandronum.com/tracker/file_download.php?file_id=2694&type=bug

meanwhile_in_zan_3p0.jpg (53,613) 2021-12-23 09:14 https://zandronum.com/tracker/file_download.php?file_id=2695&type=bug

eval_working.png (159,680) 2021-12-23 10:08 https://zandronum.com/tracker/file_download.php?file_id=2699&type=bug

|
|
Issue History |
Date Modified | Username | Field | Change |
2021-12-19 12:42 | Zalewa | New Issue | |
2021-12-19 12:42 | Zalewa | Relationship added | related to 0003944 |
2021-12-19 13:54 | WaTaKiD | Note Added: 0021929 | |
2021-12-19 14:48 | Kaminsky | Status | new => acknowledged |
2021-12-22 03:14 | Blzut3 | Note Added: 0021972 | |
2021-12-22 09:22 | Zalewa | Assigned To | => Zalewa |
2021-12-22 09:22 | Zalewa | Status | acknowledged => assigned |
2021-12-22 09:23 | Zalewa | Note Added: 0021975 | |
2021-12-22 11:12 | Zalewa | Note Added: 0021976 | |
2021-12-22 11:45 | Zalewa | Assigned To | Zalewa => |
2021-12-22 11:45 | Zalewa | Status | assigned => acknowledged |
2021-12-23 03:27 | Blzut3 | Note Added: 0021989 | |
2021-12-23 09:08 | Zalewa | File Added: zandronum_eval_flags_doesnt_really_work_either.jpg | |
2021-12-23 09:09 | Zalewa | Note Added: 0021990 | |
2021-12-23 09:11 | Zalewa | File Added: the_problem_is_worse_though.jpg | |
2021-12-23 09:12 | Zalewa | Note Added: 0021991 | |
2021-12-23 09:14 | Zalewa | File Added: meanwhile_in_zan_3p0.jpg | |
2021-12-23 09:14 | Zalewa | Note Edited: 0021991 | bug_revision_view_page.php?bugnote_id=21991#r13495 |
2021-12-23 09:23 | Zalewa | Relationship added | related to 0003956 |
2021-12-23 09:24 | Zalewa | Note Added: 0021992 | |
2021-12-23 09:24 | Zalewa | Status | acknowledged => resolved |
2021-12-23 09:24 | Zalewa | Resolution | open => invalid |
2021-12-23 09:24 | Zalewa | Assigned To | => Zalewa |
2021-12-23 09:24 | Zalewa | Note Edited: 0021992 | bug_revision_view_page.php?bugnote_id=21992#r13497 |
2021-12-23 10:08 | Blzut3 | File Added: eval_working.png | |
2021-12-23 10:14 | Blzut3 | Note Added: 0021994 | |
Notes |
|
|
to recap our findings on discord:
also an issue in zan 3.0 where the flag was backported
also an issue in gzdoom 1.8.6
fixed in gzdoom 4.7.0 |
|
|
(0021972)
|
Blzut3
|
2021-12-22 03:14
|
|
Actually kind of surprised it got noticed in GZDoom (unless it was an incidental fix from a rewrite or something).
I'm guessing the issue is that it's assuming the dash is starting a new command line parameter instead of being part of the console command. It can be worked around in the mean time by putting a space before the minus sign, or even sending "+compatflags -2147483648" as one argument. Obviously not something we'd want to use permanently though. |
|
|
(0021975)
|
Zalewa
|
2021-12-22 09:23
|
|
Quote from Blzut3 Obviously not something we'd want to use permanently though.
But I will use it right now :D |
|
|
(0021976)
|
Zalewa
|
2021-12-22 11:12
|
|
Quote from Blzut3 It can be worked around in the mean time by putting a space before the minus sign, or even sending "+compatflags -2147483648" as one argument.
So, I tried that, and unfortunately it only works when launching an offline game. When I add "-host" to the command line, the server starts with compatflags 0. |
|
|
(0021989)
|
Blzut3
|
2021-12-23 03:27
|
|
OK, another work around which works with -host in my testing: +eval 0x80000000 compatflags |
|
|
(0021990)
|
Zalewa
|
2021-12-23 09:09
|
|
Quote from Blzut3 OK, another work around which works with -host in my testing: +eval 0x80000000 compatflags
Unfortunately no: zandronum_eval_flags_doesnt_really_work_either.jpg
It sets the value, but only up to the max signed value. |
|
|
(0021991)
|
Zalewa
|
2021-12-23 09:12
(edited on: 2021-12-23 09:14) |
|
the_problem_is_worse_though.jpg
meanwhile_in_zan_3p0.jpg
'https://zandronum.com/tracker/view.php?id=3938#c21985 [^]'
'https://zandronum.com/tracker/view.php?id=3938#c21986 [^]'
Quote from WaTaKiD upon further inspection, it seems the compatflags and compatflags2 fields dont work at all
to reproduce:
set all the flags fields to a value of 2 and start the server, then check them on the server, compatflags and compatflags2 will return 0 instead of 2
[...]
regarding compatflags/compatflags2 i think this is a zan 3.1 regression unless im doing something terribly wrong, requires even further inspection
|
|
|
(0021992)
|
Zalewa
|
2021-12-23 09:24
|
|
Since the problem is different and there has been some discussion here already about the negative values, I'm closing this ticket and opened a new one at 0003956.
|
|
|
(0021994)
|
Blzut3
|
2021-12-23 10:14
|
|
Huh, that's quite interesting. It definitely does work for me on Linux (attached screenshot). Although I wouldn't be surprised if it was a libc difference in that case or something. There's probably another expression you could pass to eval to get it to work, but yeah something is weird with compatflag handling regardless. |
|