A Altimor Active member Jun 18, 2024 #1 Time rounding errors with non-pow2 tickrate? Code: setpos_exact 2265 40 200;cl_citadel_forceangles 0 270 0;-forward;+forward;+in_innate1;-in_innate1 and citadel_air_drag_min 0 Attachments 2024-06-18_09-14-53.mp4 2024-06-18_09-14-53.mp4 14.7 MB
Time rounding errors with non-pow2 tickrate? Code: setpos_exact 2265 40 200;cl_citadel_forceangles 0 270 0;-forward;+forward;+in_innate1;-in_innate1 and citadel_air_drag_min 0
A Altimor Active member Jul 4, 2024 #2 confirmed this is a time rounding error, doesn't happen if i modify the game to 64 tick (or most other numbers) Last edited: Jul 5, 2024
confirmed this is a time rounding error, doesn't happen if i modify the game to 64 tick (or most other numbers)
A Altimor Active member Jul 25, 2024 #4 Also happens with downdash. It seems the tick where it finishes lerping to 4.0 drag may or may not get skipped in both cases.
Also happens with downdash. It seems the tick where it finishes lerping to 4.0 drag may or may not get skipped in both cases.
