|Anonymous | Login | Signup for a new account||2019-05-19 13:09 UTC|
|My View | View Issues | Change Log | Roadmap | Zandronum Issue Support Ranking | Rules | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000540||Zandronum||[All Projects] Bug||public||2011-07-30 13:32||2018-08-27 21:30|
|Target Version||Fixed in Version||3.1|
|Summary||0000540: Weapon selection is desynced between clients|
|Description||After some heavy testing I found another nasty player sprite and/or a coop spy issue and managed to reproduce it. Sometimes your client will think that other clients are firing their weapons when they truly aren't firing them. The weapon selection is desynced between the clients. It can look like your opponent is firing his chaingun when it's actually being selected on his end. You don't hear any attack sounds or see any bullet puffs, but decals are spawned. I recorded a demo of it with 3287.|
|Steps To Reproduce||I alternate between selecting the fist and chaingun while repeatedly tapping +attack in a fast manner. I sometimes allow my client to attack with the fist before selecting the chaingun, but I never allow my client to attack with the chaingun. I make sure that I lower the chaingun before it's fully raised on my end. After a while, the other client will start to think that the chaingun fully raised on your end.|
Demos recorded with build 3287:
I have a demo of de-sync. It seems like when there's packet loss going to the server, the client goes out of sync.
Furthermore when this happened, when I reached 0 rockets it fired another one shortly thereafter, which can be very glitchy.
Thus, a solution is maybe every so often re-transmit the ammo from the server to the client?
|This interestingly enough seems to have been fixed in 3.1 with the unlagged fixes and the addition of a "movement regulator buffer?". I could reproduce it in 3.0 on a local server very quickly, but not in the latest 3.1 alpha build, even when double checking.|
The movement buffer regulator shouldn't miraculously fix weapon sync issues as the only thing it does is change the way the buffer itself empties.
This is most likely due to 0002607 getting fixed, which was a bit before I introduced the movement buffer regulator.
This issue is already marked as resolved.
If you feel that is not the case, please reopen it and explain why.
|Supporters:||No one explicitly supports this issue yet.|
|Opponents:||No one explicitly opposes this issue yet.|
|2011-07-30 13:32||unknownna||New Issue|
|2011-07-30 13:32||unknownna||Status||new => confirmed|
|2011-07-30 13:35||unknownna||Note Added: 0002017|
|2011-07-30 13:40||unknownna||Relationship added||related to 0000193|
|2011-07-30 15:56||unknownna||Relationship added||related to 0000423|
|2011-08-07 17:17||unknownna||Relationship added||related to 0000553|
|2012-06-09 13:22||Torr Samaho||Category||General => Bug|
|2013-02-09 18:35||Watermelon||Note Added: 0005974|
|2015-07-21 12:46||unknownna||Relationship added||has duplicate 0002356|
|2018-08-27 06:53||unknownna||Relationship added||related to 0001041|
|2018-08-27 17:55||unknownna||Note Added: 0019438|
|2018-08-27 17:56||unknownna||Assigned To||=> Leonard|
|2018-08-27 17:56||unknownna||Status||confirmed => resolved|
|2018-08-27 17:56||unknownna||Resolution||open => fixed|
|2018-08-27 17:56||unknownna||Fixed in Version||=> 3.1|
|2018-08-27 21:30||Leonard||Note Added: 0019441|
Questions or other issues? Contact Us.
|Copyright © 2000 - 2019 MantisBT Team|