MantisBT - Zandronum
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000465Zandronum[All Projects] Bugpublic2011-05-23 11:362018-09-30 22:56
Reporterunknownna 
Assigned ToTorr Samaho 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version98d 
Target VersionFixed in Version2.0 
Summary0000465: "compat_oldweaponswitch" doesn't work properly in "nointermission" maps
DescriptionI noticed this while testing duel32-rc2.pk3. The lobby map has "nointermission" defined in the MAPINFO lump. With some ping, this means that you'll enter the map before you're actually there. You pick up a weapon, but don't switch to it.
Steps To Reproduce1. Start a DM server with the example WAD loaded and compat_oldweaponswitch set to 1.
2. Connect a client to the server with an emulated ping of 251 ms.
3. Join the game.
4. "send_password <password>" in the console.
5. "bind <key> "rcon nextmap"" in the console.
6. Hold +forward.
7. Press the bound RCON key.
Additional Information"switchonpickup" is also affected by this when compat_oldweaponswitch is set to 0.
TagsNo tags attached.
Relationships
related to 0000193closed Torr Samaho Able to fire weapon before it's passed A_Raise 
Attached Files? nointermission_weap_desync_test_01.wad (778) 2011-05-23 11:36
/tracker/file_download.php?file_id=339&type=bug
Issue History
Date ModifiedUsernameFieldChange
2011-05-23 11:36unknownnaNew Issue
2011-05-23 11:36unknownnaFile Added: nointermission_weap_desync_test_01.wad
2011-05-23 11:38unknownnaRelationship addedrelated to 0000193
2012-06-09 13:22Torr SamahoCategoryGeneral => Bug
2014-06-11 15:43WatermelonNote Added: 0009043
2014-06-11 15:43WatermelonStatusnew => feedback
2015-06-06 20:01unknownnaNote Added: 0012558
2015-06-06 20:01unknownnaStatusfeedback => new
2015-06-06 20:01unknownnaAssigned To => Torr Samaho
2015-06-06 20:01unknownnaStatusnew => resolved
2015-06-06 20:01unknownnaResolutionopen => fixed
2015-06-06 20:47unknownnaFixed in Version => 2.0
2018-09-30 22:56Blzut3Statusresolved => closed

Notes
(0009043)
Watermelon   
2014-06-11 15:43   
Still occur in 2.0?
(0012558)
unknownna   
2015-06-06 20:01   
No, it has surprisingly been fixed.