MantisBT - Zandronum
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0003469Zandronum[All Projects] Bugpublic2018-08-28 02:242021-10-13 18:53
Reporterunknownna 
Assigned ToKaminsky 
PriorityurgentSeveritymajorReproducibilityalways
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product Version3.1-beta 
Target Version3.1Fixed in Version3.1-beta 
Summary0003469: Client fires weapon too early after map resets in 3.1
DescriptionThe client fires the weapon too early after map resets since 3.1. This, like the respawn issue, is very important to have fixed as the first few kills in a duel can make a considerable difference in the game.
Steps To Reproducechangemap_weap_desync.wad

1. zandronum -host -iwad doom2.wad -file changemap_weap_desync.wad +survival 1 +sv_survivalcountdowntime 1
2. Connect a client to the server. No ping emulation should be needed.
3a. Copy-paste "join;wait 48;+attack;wait 1;-attack" into the console. No rockets will come out.
If that doesn't work, use the bind in step 3b instead.
3b. Copy-paste "join;wait 49;+attack;wait 1;-attack" into the console.
4. Spectate and repeat step 3a or 3b. It should desync rather quickly.
Additional Information
TagsNo tags attached.
Relationships
related to 0001116resolved Kaminsky Client fires weapon too early after respawning 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2018-08-28 02:24unknownnaNew Issue
2018-08-28 02:24unknownnaStatusnew => confirmed
2018-08-28 02:25unknownnaRelationship addedrelated to 0001116
2018-08-28 09:54Edward-sanNote Added: 0019444
2018-08-28 09:54Edward-sanStatusconfirmed => feedback
2018-08-28 09:56Edward-sanNote Edited: 0019444bug_revision_view_page.php?bugnote_id=19444#r11733
2018-08-28 10:28unknownnaNote Added: 0019445
2018-08-28 10:28unknownnaStatusfeedback => new
2018-08-28 11:47Edward-sanNote Added: 0019446
2018-08-28 18:04unknownnaNote Added: 0019447
2018-08-28 19:31unknownnaNote Added: 0019448
2018-08-28 19:31unknownnaSummaryClient fires weapon too early after map resets => Client fires weapon too early after map resets in 3.1
2018-08-28 19:31unknownnaDescription Updatedbug_revision_view_page.php?rev_id=11735#r11735
2018-08-28 19:31unknownnaSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=11737#r11737
2018-08-28 22:20Edward-sanProduct Version3.0 => 3.1-beta
2019-02-17 21:00Torr SamahoTarget Version => 3.1
2019-03-10 20:28Torr SamahoNote Added: 0020438
2019-04-07 20:07Edward-sanNote Added: 0020478
2019-04-07 20:07Edward-sanStatusnew => feedback
2021-10-10 10:40SoulNote Added: 0021783
2021-10-13 18:53KaminskyNote Added: 0021785
2021-10-13 18:53KaminskyStatusfeedback => resolved
2021-10-13 18:53KaminskyFixed in Version => 3.1-beta
2021-10-13 18:53KaminskyResolutionopen => fixed
2021-10-13 18:53KaminskyAssigned To => Kaminsky

Notes
(0019444)
Edward-san   
2018-08-28 09:54   
(edited on: 2018-08-28 09:56)
I cannot reproduce this. Does this require some ping/spikes emulation?

N.B: I tried with ping 160 but it didn't work at all. The rocket comes out, with a little delay from the firing animation.

What about the network settings?
(0019445)
unknownna   
2018-08-28 10:28   
The binds are meant to be used without any ping emulation. I use a local connection to the server.
It might be a 3.1 regression, judging from a quick test between 3.0 and 3.1.
(0019446)
Edward-san   
2018-08-28 11:47   
I can't seem to reproduce this reliably. I got only one instance of this after a lot of runnings, but I didn't get any relevant information. I'll check again and see if I'm lucky enough...
(0019447)
unknownna   
2018-08-28 18:04   
After trying it again between 3.0 and 3.1-alpha 180520-0650, I can't seem to get the NULL rocket issue in 3.0 after map resets. It must be a 3.1 regression then.

As for network settings, I use:

cl_connectiontype 1
cl_ping_unlagged 0
cl_ticsperupdate 1
cl_unlagged 1

But 3.0 is still partially wrong as the bind will sometimes fire the rocket and sometimes not (no weapon desync though).
(0019448)
unknownna   
2018-08-28 19:31   
It seems to be a 3.1 regression.
(0020438)
Torr Samaho   
2019-03-10 20:28   
'https://bitbucket.org/zandronum/zandronum-sandbox-stable/commits/6bf9997a595a230594dcc6d1871b43b8a78bb666 [^]' also seems to fix this problem.
(0020478)
Edward-san   
2019-04-07 20:07   
Please check with the build in 0003470:0020476 .
(0021783)
Soul   
2021-10-10 10:40   
Upon testing, this appears to be fixed now.
(0021785)
Kaminsky   
2021-10-13 18:53   
Thanks for testing it out. I'll mark this as resolved now.