|Anonymous | Login | Signup for a new account||2019-03-19 17:10 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|
|0003469||Zandronum||[All Projects] Bug||public||2018-08-28 02:24||2019-03-10 20:28|
|Target Version||3.1||Fixed in Version|
|Summary||0003469: Client fires weapon too early after map resets in 3.1|
|Description||The 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 Reproduce||changemap_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.
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?
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.
|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...|
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:
But 3.0 is still partially wrong as the bind will sometimes fire the rocket and sometimes not (no weapon desync though).
|It seems to be a 3.1 regression.|
Torr Samaho (administrator)
|https://bitbucket.org/zandronum/zandronum-sandbox-stable/commits/6bf9997a595a230594dcc6d1871b43b8a78bb666 [^] also seems to fix this problem.|
|Only registered users can voice their support. Click here to register, or here to log in.|
|Supporters:||No one explicitly supports this issue yet.|
|Opponents:||No one explicitly opposes this issue yet.|
|2018-08-28 02:24||unknownna||New Issue|
|2018-08-28 02:24||unknownna||Status||new => confirmed|
|2018-08-28 02:25||unknownna||Relationship added||related to 0001116|
|2018-08-28 09:54||Edward-san||Note Added: 0019444|
|2018-08-28 09:54||Edward-san||Status||confirmed => feedback|
|2018-08-28 09:56||Edward-san||Note Edited: 0019444||View Revisions|
|2018-08-28 10:28||unknownna||Note Added: 0019445|
|2018-08-28 10:28||unknownna||Status||feedback => new|
|2018-08-28 11:47||Edward-san||Note Added: 0019446|
|2018-08-28 18:04||unknownna||Note Added: 0019447|
|2018-08-28 19:31||unknownna||Note Added: 0019448|
|2018-08-28 19:31||unknownna||Summary||Client fires weapon too early after map resets => Client fires weapon too early after map resets in 3.1|
|2018-08-28 19:31||unknownna||Description Updated||View Revisions|
|2018-08-28 19:31||unknownna||Steps to Reproduce Updated||View Revisions|
|2018-08-28 22:20||Edward-san||Product Version||3.0 => 3.1-beta|
|2019-02-17 21:00||Torr Samaho||Target Version||=> 3.1|
|2019-03-10 20:28||Torr Samaho||Note Added: 0020438|
Questions or other issues? Contact Us.
|Copyright © 2000 - 2019 MantisBT Team|