Closed lllLORD2000lll closed 1 year ago
I wouldn't be asking if that information was there.
- sm_closestpos C++ extension to efficiently find the closest replay position for calculating time-difference and velocity-difference.
Literally in readme.md
Author
You literally just did.
Thank Nuko for being kind and actually holding your hand to help you with your "issue", that you'd have found on your own if that info was there.
Solution: works only shavit_hud_timedifference "1" and only in cvar force
That's not a solution. That's just misleading and you're using an outdated version of the timer. It literally says in the change log of 3.0.0 "shavit_hud_timedifference renamed to shavit_replay_timedifference"
Use the updated version of the timer and the correct convars to avoid such problems and misleading people reading the issues for further reference.
That's not a solution. That's just misleading and you're using an outdated version of the timer. It literally says in the change log of 3.0.0 "shavit_hud_timedifference renamed to shavit_replay_timedifference"
Previously, this cvar included lagging behind WR anywhere on the map. What value does cvar shavit_replay_timedifference take initially? And has its principle of operation changed?
It looked like this
plugin.shavit-replay-recorder.cfg
Previously, this cvar included lagging behind WR anywhere on the map.
It still does that.
What value does cvar shavit_replay_timedifference take initially?
It was changed to a default of 1
And has its principle of operation changed?
No
plugin.shavit-replay-recorder.cfg
plugin.shavit-replay-playback.cfg
in b4 he asks where those are located
Going to close this.
Check for timedifference cvars in the cfg/sourcemod/plugin.shavit-*.cfg
files if you want to enable it.
sm_closestpos
can be useful too of course.
And you might have to enable it in !hud
if it's not shown.
I did this before, but now it doesn't work. After a certain update, it stopped working.