MantisBT - Zandronum
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0004440Zandronum[All Projects] Suggestionpublic2024-11-15 06:552025-03-20 13:01
Reporterunknownna 
Assigned To 
PrioritynormalSeverityfeatureReproducibilityN/A
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0004440: Ping-based unlagged breaks with "cl_usemovebuffer 1"
DescriptionThe ping-based unlagged doesn't seem to be compatible with the new movement buffer.

However, with the implementation of the new system of the clock offset shifting combined with the new movement buffer, it should be safe to phase out the ping-based unlagged like it was desired by the team earlier.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2024-11-15 06:55unknownnaNew Issue
2024-11-15 17:58KaminskyNote Added: 0024145
2024-11-15 20:09unknownnaNote Added: 0024148
2024-11-15 20:09unknownnaStatusnew => feedback
2025-03-20 13:01unknownnaNote Added: 0024265
2025-03-20 13:01unknownnaStatusfeedback => new
2025-03-20 13:01unknownnaStatusnew => closed
2025-03-20 13:01unknownnaResolutionopen => fixed

Notes
(0024145)
Kaminsky   
2024-11-15 17:58   
I have to agree that if the new clock offset system (and the other changes I recently made) have improved or fixed issues with the gametic-based unlagged, then it's probably better if we finally got rid of the ping-based unlagged, as was suggested many years ago. I think many more people prefer the gametic-based unlagged anyways, which undoubtedly performs better than ping-based, so I wouldn't have anything against phasing the latter out. This would simplify things too, as there'd be fewer settings for users to needlessly play around with.
(0024148)
unknownna   
2024-11-15 20:09   
Yeah, I'd say just go ahead and remove it. It's ok now.
(0024265)
unknownna   
2025-03-20 13:01   
Since the ping-unlagged will get removed eventually, this issue can be closed.