MantisBT - Zandronum
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0003492Zandronum[All Projects] Bugpublic2018-09-12 12:542022-02-27 22:43
Reporterunknownna 
Assigned To 
PriorityurgentSeveritymajorReproducibilityalways
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product Version3.1-beta 
Target Version3.1Fixed in Version3.1 
Summary0003492: Client fires weapon even earlier than before when respawning in 3.1
DescriptionAfter double checking the "client fires weapon too early when respawning" issue between 3.0 and 3.1, it turns out that this is actually a regression in 3.1 where the client fires the weapon even earlier than before, leading to puffs being off and projectiles even disappearing quicker than before.
Steps To Reproduceplayer_sprite_desync_test_02.wad

1. zandronum -host -iwad doom2.wad -file player_sprite_desync_test_02.wad +deathmatch 1 +sv_weaponstay 1 +sv_cheats 1
2. Connect a client to the server with an emulated ping of 160.
3. Join the game.
4a. Copy-paste "kill;wait 30;+use;+forward;wait 25;god;+attack;-forward;wait 110;-use;-forward;-attack" into the console. Rockets won't come out when they should and ammo is wasted.
If that doesn't work, do step 4b instead.
4b. Copy-paste "kill;wait 30;+use;+forward;wait 49;god;+attack;-forward;wait 110;-use;-forward;-attack" into the console. Rockets will come out, but no animation will be displayed or ammo used.
5. Spectate and re-enter the binds that work to reproduce the desync every time.
Additional Information
TagsNo tags attached.
Relationships
related to 0001116new  Client fires weapon too early after respawning 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2018-09-12 12:54unknownnaNew Issue
2018-09-12 12:55unknownnaSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=11782#r11782
2018-09-12 12:56unknownnaRelationship addedrelated to 0001116
2018-09-12 14:52Edward-sanProduct Version3.0 => 3.1-beta
2019-02-17 20:59Torr SamahoTarget Version => 3.1
2019-04-07 20:07Edward-sanNote Added: 0020479
2019-04-07 20:07Edward-sanStatusnew => feedback
2022-02-27 22:39KaminskyNote Added: 0022150
2022-02-27 22:39KaminskyStatusfeedback => resolved
2022-02-27 22:39KaminskyFixed in Version => 3.1
2022-02-27 22:39KaminskyResolutionopen => fixed
2022-02-27 22:39KaminskyAssigned To => Kaminsky
2022-02-27 22:43KaminskyNote Edited: 0022150bug_revision_view_page.php?bugnote_id=22150#r13576
2022-02-27 22:43KaminskyAssigned ToKaminsky =>

Notes
(0020479)
Edward-san   
2019-04-07 20:07   
Please check with the build from 0003470:0020476 .
(0022150)
Kaminsky   
2022-02-27 22:39   
(edited on: 2022-02-27 22:43)
Based on the feedback from:'https://zandronum.com/tracker/view.php?id=3469 [^]' and'https://zandronum.com/tracker/view.php?id=3470 [^]' and the similarity between those tickets and this one, it's very likely that this issue has also been fixed and can be marked as resolved. Please feel free to re-open this ticket if necessary.