Zandronum Chat on our Discord Server Get the latest version: 3.1
Source Code

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0003470Zandronum[All Projects] Bugpublic2018-08-28 02:392021-10-13 18:53
Reporterunknownna 
Assigned ToTorr Samaho 
PriorityurgentSeveritymajorReproducibilityalways
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product Version3.1-beta 
Target Version3.1Fixed in Version3.1-beta 
Summary0003470: Client fires weapon too early when joining the game in 3.1
DescriptionThe client fires the weapon too early when joining the game in 3.1, leading to your first few shots being thrown off. It's very important to have this fixed, especially for CTF games.
Steps To Reproducechangemap_weap_desync.wad

1. zandronum -host -iwad doom2.wad -file changemap_weap_desync.wad
2. Connect a client to the server. No ping emulation should be needed.
3. Copy-paste "join;wait 14;+attack;wait 1;-attack" into the console. Spectate and re-enter the bind to reproduce the desync every time.
Attached Files

- Relationships
related to 0001116new Client fires weapon too early after respawning 

-  Notes
User avatar (0019449)
unknownna (updater)
2018-08-28 19:49

The client firing the weapon too early is a 3.1 regression.

However, the client can sometimes fire the weapon too late in 3.0. I'll try to reproduce the 3.0 issues better.
User avatar (0019450)
Edward-san (developer)
2018-08-28 22:30

This time I can reproduce this pretty much always.

I cannot guarantee I can have a look at this because of IRL stuff, though.
User avatar (0020427)
Torr Samaho (administrator)
2019-02-24 17:26
edited on: 2019-02-24 17:38

I looked into this. The fix for 0002748 introduced this.

BTW: Offline, the player fires using the example. So I'd say it's not the client firing too early, but the server incorrectly not processing the player attack.

User avatar (0020435)
Torr Samaho (administrator)
2019-03-03 21:26

'https://bitbucket.org/zandronum/zandronum-sandbox-stable/commits/6bf9997a595a230594dcc6d1871b43b8a78bb666 [^]' seems to fix the issue, but I have no idea whether this has any side effects.
User avatar (0020436)
Edward-san (developer)
2019-03-04 15:21

Yes, I can confirm the fix for this specific issue. Considering that there are many similar reports, could it be possible to have a test build so that others can test it on these, too?
User avatar (0020476)
Torr Samaho (administrator)
2019-04-07 19:51

Here is a Win32 binary with the fix:'http://www.mediafire.com/file/sjqgl380l95dc2b/ZandroDev3.1-WeapSyncFixTest.7z [^]'
User avatar (0021076)
StrikerMan780 (reporter)
2019-12-04 06:11
edited on: 2019-12-04 06:12

Can confirm that the binary Torr posted above my comment works.

User avatar (0021194)
EpicTyphlosion (reporter)
2020-02-10 03:39

As a person who has participated in the Zandronum Competition Alliance, I can confirm that some of the people I have played with and against have experienced this. There was once a long scuffle in the ZCA Discord server where someone showed a GIF of them firing an SSG point-blank at another player and not dealing any damage due to this very bug. Everyone kept trying to discern whether or not it was his ping or something like that, but Water later stepped in and confirmed that it was this very bug.

Whoever is in charge of fixing this bug, please expedite. This has been ruining CTF games for years now, and everyone's completely sick of it.
User avatar (0021214)
Torr Samaho (administrator)
2020-02-16 20:57

A fix for the issue is ready for testing, see above. Can you confirm that the fix works? Do you need more info regarding the testing?
User avatar (0021301)
Torr Samaho (administrator)
2020-05-01 18:49

I'll add the fix to the main repository to include it in the upcoming 3.1 beta build.
User avatar (0021782)
Soul (reporter)
2021-10-10 10:40

Upon testing, this appears to be fixed now.
User avatar (0021784)
Kaminsky (developer)
2021-10-13 18:53

Thanks for testing it out. I'll mark this as resolved now.

Issue Community Support
This issue is already marked as resolved.
If you feel that is not the case, please reopen it and explain why.
Supporters: EpicTyphlosion Soul
Opponents: No one explicitly opposes this issue yet.

- Issue History
Date Modified Username Field Change
2018-08-28 02:39 unknownna New Issue
2018-08-28 02:39 unknownna Status new => confirmed
2018-08-28 02:40 unknownna Relationship added related to 0001116
2018-08-28 19:49 unknownna Note Added: 0019449
2018-08-28 20:01 unknownna Summary Client fires weapon too early when joining the game => Client fires weapon too early when joining the game in 3.1
2018-08-28 20:01 unknownna Description Updated View Revisions
2018-08-28 20:01 unknownna Steps to Reproduce Updated View Revisions
2018-08-28 22:20 Edward-san Product Version 3.0 => 3.1-beta
2018-08-28 22:30 Edward-san Note Added: 0019450
2019-02-17 21:01 Torr Samaho Target Version => 3.1
2019-02-24 17:26 Torr Samaho Note Added: 0020427
2019-02-24 17:38 Torr Samaho Note Edited: 0020427 View Revisions
2019-03-03 21:26 Torr Samaho Note Added: 0020435
2019-03-04 15:21 Edward-san Note Added: 0020436
2019-04-07 19:51 Torr Samaho Note Added: 0020476
2019-04-07 20:04 Edward-san Assigned To => Torr Samaho
2019-04-07 20:04 Edward-san Status confirmed => feedback
2019-12-04 06:11 StrikerMan780 Note Added: 0021076
2019-12-04 06:12 StrikerMan780 Note Edited: 0021076 View Revisions
2020-02-10 03:39 EpicTyphlosion Note Added: 0021194
2020-02-16 20:57 Torr Samaho Note Added: 0021214
2020-05-01 18:49 Torr Samaho Note Added: 0021301
2020-05-02 12:10 Torr Samaho Status feedback => needs testing
2021-10-10 10:40 Soul Note Added: 0021782
2021-10-13 18:53 Kaminsky Note Added: 0021784
2021-10-13 18:53 Kaminsky Status needs testing => resolved
2021-10-13 18:53 Kaminsky Fixed in Version => 3.1-beta
2021-10-13 18:53 Kaminsky Resolution open => fixed






Questions or other issues? Contact Us.

Links


Copyright © 2000 - 2024 MantisBT Team
Powered by Mantis Bugtracker