MantisBT - Zandronum
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0002885Zandronum[All Projects] Bugpublic2016-10-11 19:002018-09-30 21:55
ReporterDrinkyBird 
Assigned ToTorr Samaho 
PriorityurgentSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version3.0-beta 
Target Version3.0Fixed in Version3.0 
Summary0002885: deathmatch CVar doesn't take effect when used via command-line
DescriptionIn 3.0, using the deathmatch CVar via command-line doesn't take effect, the server always starts in co-op unless you specify +cooperative 0.
Steps To ReproduceHost a 2.1.2 server with at least the following:
  zandronum -host +deathmatch 1
and notice how it starts in DM.

Do the same with 3.0 and notice how it starts in co-op. Try it with other gamemodes and notice how all except DM work.

Now try launching 3.0 with
  zandronum -host +cooperative 0 +deathmatch 1
and notice how it starts in DM.
Additional InformationIsn't platform dependant, was confirmed by me, Hypnotoad, and Dark-Assassin.
TagsNo tags attached.
Relationships
parent of 0002904closed Torr Samaho Crash with hpbar-v15.pk3 + h_phobia.wad on MAP11 if a bot is present before the changemap map change 
parent of 0002960closed Edward-san Strife Crashes when transitioning between two levels in multi-player games 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2016-10-11 19:00DrinkyBirdNew Issue
2016-10-11 19:23unknownnaStatusnew => confirmed
2016-10-11 19:28unknownnaNote Added: 0015902
2016-10-11 19:29unknownnaPrioritynormal => urgent
2016-10-11 19:31Torr SamahoTarget Version => 3.0
2016-10-11 19:36Torr SamahoNote Added: 0015904
2016-10-11 19:43WaTaKiDNote Added: 0015905
2016-10-11 21:00Edward-sanNote Added: 0015908
2016-10-11 22:02Edward-sanNote Edited: 0015908bug_revision_view_page.php?bugnote_id=15908#r9681
2016-10-11 22:33Edward-sanNote Edited: 0015908bug_revision_view_page.php?bugnote_id=15908#r9682
2016-10-12 17:28Torr SamahoNote Added: 0015925
2016-10-12 17:28Torr SamahoAssigned To => Torr Samaho
2016-10-12 17:28Torr SamahoStatusconfirmed => assigned
2016-10-12 19:45Torr SamahoNote Added: 0015932
2016-10-12 19:46Torr SamahoStatusassigned => needs testing
2016-10-12 20:00Edward-sanNote Added: 0015933
2016-10-12 20:26WaTaKiDNote Added: 0015934
2016-10-13 23:21unknownnaNote Added: 0015971
2016-10-13 23:43unknownnaNote Edited: 0015971bug_revision_view_page.php?bugnote_id=15971#r9718
2016-10-19 17:26Edward-sanRelationship addedparent of 0002904
2016-12-08 03:08Ru5tK1ngNote Added: 0016441
2016-12-08 03:08Ru5tK1ngStatusneeds testing => resolved
2016-12-08 03:08Ru5tK1ngResolutionopen => fixed
2016-12-08 03:08Ru5tK1ngFixed in Version => 3.0
2016-12-12 13:58Edward-sanRelationship addedparent of 0002960
2018-09-30 21:55Blzut3Statusresolved => closed

Notes
(0015902)
unknownna   
2016-10-11 19:28   
It started to break in 3.0-151228-1140.
(0015904)
Torr Samaho   
2016-10-11 19:36   
So it was working in 151004-2012? Would be great if somebody can compile the changesets in between to pin point the changeset that broke this.
(0015905)
WaTaKiD   
2016-10-11 19:43   
bingo:'https://bitbucket.org/Torr_Samaho/zandronum/commits/c801abda95a73b72cba2bce1d18b33cf289d4db9 [^]'
(0015908)
Edward-san   
2016-10-11 21:00   
(edited on: 2016-10-11 22:33)
Is it just me or it happens also with 2.2 alpha, too?

[edit] No, it seems I get this problem also when I compile 2.1.2 by myself. The official binary works fine.

I forgot to mention, but I used this offline command:


zandronum -iwad doom2.wad -warp 01 +deathmatch 1
(0015925)
Torr Samaho   
2016-10-12 17:28   
I think I remember what's going on. This is a linker problem and likely surfaces now under Windows since we switched to cmake + VS 2015 and enabled parallel building. I'll have a closer look on how to fix this.
(0015932)
Torr Samaho   
2016-10-12 19:45   
Hopefully, I have figured out how to fix this. Unfortunately, I couldn't reproduce this reliable, so I couldn't test it properly and pushed the fix to the sandbox:
'https://bitbucket.org/zandronum/zandronum-sandbox/commits/c5fde6d1b368547a2f7156cdd8df6a88639b297b [^]'
(0015933)
Edward-san   
2016-10-12 20:00   
It seems it finally fixed in my system, too.
(0015934)
WaTaKiD   
2016-10-12 20:26   
this build contains the above commit: 'https://www.dropbox.com/s/edwqxq5eg8rhhn8/zandronum-3.0-r161012-1942-c5fde6d-windows.zip?dl=0 [^]'

ive used the following command lines
zandronum -host -iwad doom2 +deathmatch 1
zandronum -iwad doom2.wad -warp 01 +deathmatch 1

along with a few other gamemodes, just to be sure, and it seems to work properly now
(0015971)
unknownna   
2016-10-13 23:21   
(edited on: 2016-10-13 23:43)
Starting a DM server seems to work for me now as well.

Edit:

And all the other modes as well.
(0016441)
Ru5tK1ng   
2016-12-08 03:08   
Deathmatch working along with the other game modes confirmed.