0000706: Moving down sector elevator desyncs height of spawned projectiles

Notes
(0002809) Edward-san (developer) 2012-03-12 16:49 edited on: 2012-03-12 16:51	It seems that the client thinks the elevator speed is lower than the right one. In fact, when I shoot with any hitscan weapon the puff's position is lower than yours. Also, when you wait a lot, at a certain point there's a high speed lowering down. The server's current elevator is near the stopping position, but the client thinks the elevator's current position is a lot higher. This effect is visible with the second record demo. You have to wait a lot of time, I don't know how to measure the right time this happens.

(0002827) Torr Samaho (administrator) 2012-03-18 21:02	Can somebody create a minimal example wad?

(0002965) unknownna (updater) 2012-03-28 17:21	Edward-san, can you reproduce the bug with my example WAD?

(0002966) Edward-san (developer) 2012-03-28 19:07	Yes, just wait a bit and begin shooting with the pistol. At the beginning there's nothing notable, but wait a minute and refire again. The spawned projectile is positioned lower than the cross.

(0003159) TIHan (reporter) 2012-04-07 00:24 edited on: 2012-04-07 00:25	Me and Edward had a good long discussion about this, which I was able to reproduce the issue in two ways: 1. With unlagged off and with 500 ping - the ping determines the gap between where you fired and where it actually hits - with hitscan weapons. 2. With unlagged on, I start the floor moving down with 500 ping, everything feels good. If I bring the ping down to 0 while the floor is moving, you can clearly see the gap in hitscan and projectiles. Notes: Apparently projectile weapons do have a gap, but it's very hard to notice without fluctuating the ping constantly. This is due to how latency works with floors; as we have no prediction of moving sectors and/or no unlagged on projectile weapons right when they fire (which we do not want that). This needs to be thoroughly discussed and probably do something about it after 98e.

(0005769) Edward-san (developer) 2013-01-13 13:35	zandronum 1.0 is released, so I believe this should be fixed in 1.1.

**Issue Community Support**
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.

Issue Community Support

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.

Issue History
Date Modified	Username	Field	Change
2012-03-12 16:04	Edward-san	New Issue
2012-03-12 16:04	Edward-san	File Added: elevatorbug.cld
2012-03-12 16:49	Edward-san	Note Added: 0002809
2012-03-12 16:51	Edward-san	Note Edited: 0002809	View Revisions
2012-03-12 16:51	Edward-san	File Added: elevatorbug1.cld
2012-03-18 21:02	Torr Samaho	Note Added: 0002827
2012-03-18 21:03	Torr Samaho	Status	new => feedback
2012-03-28 17:21	unknownna	File Added: hr2_floor_test_01.wad
2012-03-28 17:21	unknownna	Note Added: 0002965
2012-03-28 19:07	Edward-san	Note Added: 0002966
2012-03-28 19:07	Edward-san	Status	feedback => new
2012-04-07 00:24	TIHan	Note Added: 0003159
2012-04-07 00:24	TIHan	Assigned To	=> TIHan
2012-04-07 00:24	TIHan	Status	new => acknowledged
2012-04-07 00:25	TIHan	Note Edited: 0003159	View Revisions
2012-04-29 01:55	TIHan	Relationship added	related to 0000791
2012-04-29 17:19	TIHan	Relationship added	related to 0000055
2012-06-09 13:22	Torr Samaho	Category	General => Bug
2013-01-13 13:35	Edward-san	Note Added: 0005769
2014-10-12 14:02	Torr Samaho	Relationship added	related to 0001957