Welcome, Guest. Please login or register.
Did you miss your activation email?
October 01, 2020, 04:58:38 am

Login with username, password and session length
Search:     Advanced search
Savage: XR is a new patch for Savage, created by the Newerth.com staff. The XR1.1 Client is out now! Download it now!
190045 Posts in 11004 Topics by 18533 Members
Latest Member: Skuzie
* Home Forum Wiki Help Search Login Register
+  Newerth Forums
|-+  Archive
| |-+  Savage XR Videos
| | |-+  Small tip for smoother recording
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: Small tip for smoother recording  (Read 4438 times)
Melee enthusiast
Newerth Shoutcaster
Hero Member
Posts: 687

Duels Duels Duels

View Profile WWW
« on: January 22, 2016, 10:48:07 pm »

Savage assumes that players walk in a straight line between server updates (20 server fps = 50ms), but if a player switches direction between server updates, the game has to fix their position when a new update arrives, and they will be teleported a bit from where they were moving to where they actually went.

This makes for jittery movement, so Savage uses a variable called cl_lerpshift (default = 0.4). This delays all other players' positions by 0.6 of a server frame (30ms), so that when the game makes a correction to their position, they don't have to teleport as far.

When recording gameplay for movies, you can reduce the jitter even more by increasing that delay. Use the command cl_lerpshift 0 (this delays players' positions by a full frame) to reduce jitter even more and make your recording smoother.

cl_lerpshift 0.4 (default setting)
cl_lerpshift 0 (smooth recording setting, do not use this for gameplay)

Newerth Donator
Hero Member
Posts: 666

View Profile WWW
« Reply #1 on: January 22, 2016, 10:55:11 pm »

Good tip, thanks!
Pages: [1] Go Up Print 
« previous next »
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2006-2007, Simple Machines Valid XHTML 1.0! Valid CSS!
Page created in 0.021 seconds with 20 queries.