0001089: Desync when opening polydoor gets blocked

Notes
(0004854) Dusk (developer) 2012-09-30 01:00	'https://bitbucket.org/CrimsonDusk/neurosphere/changeset/61bb1e54cf4e6b4e9ed138ec7042a59b48b7ddcb [^]' Though it does increase the net usage a bit if the client actively pushes against the moving poly door... is this something to be worried about?

(0004859) Torr Samaho (administrator) 2012-09-30 07:30	This doesn't seem to fully fix the problem (the differences of online and offline behavior are more pronounced with higher ping). From what I can say the position of the poly object on the client is not the problem, the problem is that the client mispredicts its position (by ignoring the collusion of the poly door and the player body). In order to fix this, the client needs to predict the player movement caused by the collusion.

(0012585) Edward-san (developer) 2015-06-07 17:32 edited on: 2015-06-07 17:41	Should be really fixed with'https://bitbucket.org/crimsondusk/zandronum-sandbox-stable/commits/0fd0372edcdb82e0277f33de49037d05554b6459 [^]' . Applying the same code Torr used for 0002079 to the sliding polyobjects seems to do the trick.

(0012643) Edward-san (developer) 2015-06-10 21:15	Here's the build with the fix:'https://www.dropbox.com/s/2rcaczix5sgwbdl/zandronum-2.1-150607-1730-0fd0372-windows.zip?dl=0 [^]' .

(0012644) unknownna (updater) 2015-06-10 21:50	Seems to work fine for me with that build.

(0012676) Torr Samaho (administrator) 2015-06-13 09:59	I added your patch.

(0012681) cobalt (updater) 2015-06-13 12:16	Issue addressed by commit 0fd0372edcdb: - Fixed: Blocked sliding polyobjects were not handled properly online (addresses 1089). Committed by Edoardo Prezioso [edward-san] on Sunday 07 June 2015 19:30:06 Changes in files: docs/zandronum-history.txt \| 1 + src/po_man.cpp \| 12 +++++++++++- 2 files changed, 12 insertions(+), 1 deletions(-)

**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:	No one explicitly supports this issue yet.
Opponents:	No one explicitly opposes this issue yet.

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:

No one explicitly supports this issue yet.

Opponents:

No one explicitly opposes this issue yet.

Issue History
Date Modified	Username	Field	Change
2012-09-30 00:56	Dusk	New Issue
2012-09-30 00:56	Dusk	Status	new => assigned
2012-09-30 00:56	Dusk	Assigned To	=> Dusk
2012-09-30 01:00	Dusk	Note Added: 0004854
2012-09-30 01:00	Dusk	Status	assigned => needs review
2012-09-30 07:30	Torr Samaho	Note Added: 0004859
2012-09-30 07:31	Torr Samaho	Status	needs review => feedback
2015-06-07 17:32	Edward-san	Note Added: 0012585
2015-06-07 17:32	Edward-san	Assigned To	Dusk => Edward-san
2015-06-07 17:32	Edward-san	Status	feedback => needs review
2015-06-07 17:33	Edward-san	Note Edited: 0012585	View Revisions
2015-06-07 17:33	Edward-san	Target Version	=> 2.1
2015-06-07 17:34	Edward-san	Note Edited: 0012585	View Revisions
2015-06-07 17:41	Edward-san	Note Edited: 0012585	View Revisions
2015-06-10 21:15	Edward-san	Note Added: 0012643
2015-06-10 21:50	unknownna	Note Added: 0012644
2015-06-13 09:59	Torr Samaho	Note Added: 0012676
2015-06-13 09:59	Torr Samaho	Status	needs review => needs testing
2015-06-13 12:16	cobalt	Note Added: 0012681
2015-06-24 22:45	Dusk	Status	needs testing => resolved
2015-06-24 22:45	Dusk	Fixed in Version	=> 2.2
2015-06-24 22:45	Dusk	Resolution	open => fixed
2015-06-24 22:47	Dusk	Fixed in Version	2.2 => 2.1
2018-09-30 21:37	Blzut3	Status	resolved => closed

Relationships