MantisBT - Zandronum
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0002036Zandronum[All Projects] Bugpublic2014-12-28 21:412018-09-30 23:11
ReporterEdward-san 
Assigned ToTorr Samaho 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version1.3 
Target Version1.4Fixed in Version2.0 
Summary0002036: More evident player desync on a gap between raising or lowering floors
DescriptionIt started to happen since the monsters jumping fix ( changeset 201bf3fa917b ) . Watch the demo I attached.
Steps To Reproduce- Host a server with'http://www.ifocserv.net/ftp/Random/MAP01_LiftGapTest2.wad [^]' ;
- join with a client and go to the moving floors;
- stay between two floors without falling down;
- watch the 'attempt to fall' when the floors raises or lowers
Additional Information
TagsNo tags attached.
Relationships
related to 0002035closed  Less evident player desync on a gap between raising floors 
Attached Files? floor_gap_desync.cld (79,927) 2014-12-28 21:41
/tracker/file_download.php?file_id=1352&type=bug
Issue History
Date ModifiedUsernameFieldChange
2014-12-28 21:41Edward-sanNew Issue
2014-12-28 21:41Edward-sanFile Added: floor_gap_desync.cld
2014-12-28 21:42Torr SamahoNote Added: 0011109
2014-12-28 21:54Edward-sanDescription Updatedbug_revision_view_page.php?rev_id=6175#r6175
2014-12-28 21:55Edward-sanNote Added: 0011113
2014-12-28 21:59DuskRelationship addedrelated to 0002035
2014-12-29 13:07cobaltAssigned To => Torr Samaho
2014-12-29 13:07cobaltStatusnew => needs testing
2014-12-29 13:07cobaltTarget Version => 1.4
2014-12-29 13:07cobaltSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=6181#r6181
2014-12-29 13:07cobaltNote Added: 0011122
2014-12-29 13:08Torr SamahoNote Added: 0011123
2014-12-29 13:09Torr SamahoNote Edited: 0011123
2014-12-29 13:10Torr SamahoNote Edited: 0011123bug_revision_view_page.php?bugnote_id=11123#r6184
2014-12-29 13:10Torr SamahoNote Revision Dropped: 11123: 0006182
2014-12-29 13:10Torr SamahoNote Revision Dropped: 11123: 0006183
2014-12-29 13:13Torr SamahoNote Edited: 0011123bug_revision_view_page.php?bugnote_id=11123#r6185
2014-12-29 13:20Torr SamahoNote Edited: 0011123bug_revision_view_page.php?bugnote_id=11123#r6186
2014-12-29 13:40Edward-sanNote Added: 0011124
2014-12-29 13:41Edward-sanNote Edited: 0011124bug_revision_view_page.php?bugnote_id=11124#r6188
2014-12-29 13:45Torr SamahoNote Added: 0011125
2014-12-29 13:48Torr SamahoNote Edited: 0011125bug_revision_view_page.php?bugnote_id=11125#r6190
2014-12-29 13:48Torr SamahoNote Revision Dropped: 11125: 0006189
2015-01-01 18:13ArcoNote Added: 0011175
2015-01-01 18:13ArcoStatusneeds testing => resolved
2015-01-01 18:13ArcoFixed in Version => 2.0
2015-01-01 18:13ArcoResolutionopen => fixed
2018-09-30 23:11Blzut3Statusresolved => closed

Notes
(0011109)
Torr Samaho   
2014-12-28 21:42   
Would be great if you could pinpoint this to the exact changeset.
(0011113)
Edward-san   
2014-12-28 21:55   
Done.
(0011122)
cobalt   
2014-12-29 13:07   
Issue addressed by commit fa2cd4976e95: Fixed problems with the client side Z position prediction near ledges. This partially addresses 2036.
Committed by Benjamin Berkels [Torr Samaho] on Monday 29 December 2014 14:06:42

Changes in files:
 docs/zandronum-history.txt | 1 +
 src/cl_main.cpp | 3 ++-
 2 files changed, 3 insertions(+), 1 deletions(-)
(0011123)
Torr Samaho   
2014-12-29 13:08   
(edited on: 2014-12-29 13:20)
fa2cd4976e95 should address the prediction problems caused by the monster jump fix 201bf3fa917b. The demo still shows problems though when the floor is raised. Can you check in which changeset the remaining problems were introduced or confirm that it was never working better? Or are the remaining problems what you are referring to in 0002035?

EDIT: Yes, it seems as if the demo is now showing the problems reported in 0002035 / caused by 5c693134fc20.

EDIT2: Once again the problem seems to be that P_OldAdjustFloorCeil messes up floorz near ledges.
(0011124)
Edward-san   
2014-12-29 13:40   
(edited on: 2014-12-29 13:41)
In other words, the bug in this ticket is fixed, not partially. The rest can be discussed in 0002035 , right? ;)
(0011125)
Torr Samaho   
2014-12-29 13:45   
(edited on: 2014-12-29 13:48)
Yeah, but when I wrote the log message I didn't know yet that the remaining issues is what was reported in 0002035 ;).
(0011175)
Arco   
2015-01-01 18:13   
Issue fixed in r150101-1703.