Nvm. I figured it out. I screwed up the #'s in the autoexec.cfg files
Account Details | |
---|---|
SteamID64 | 76561198170090679 |
SteamID3 | [U:1:209824951] |
SteamID32 | STEAM_0:1:104912475 |
Country | United States |
Signed Up | March 10, 2018 |
Last Posted | March 16, 2018 at 11:08 PM |
Posts | 3 (0 per day) |
Game Settings | |
---|---|
In-game Sensitivity | |
Windows Sensitivity | |
Raw Input | |
DPI |
|
Resolution |
|
Refresh Rate |
Hardware Peripherals | |
---|---|
Mouse | |
Keyboard | |
Mousepad | |
Headphones | |
Monitor |
@mastercoms, ok I get my system stats for my cl_ settings
[*CLOSED] This thread is resolved, lol
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
For the past few months I have been trying ways to make my cl_interp work at all. I have used configs, scripts, suggestions from Teamfortress.tv (old thread from a few years ago), and even by watching some Youtube videos. BUT, every time I do this I either lose packets, it doesn't work through complications, or even does too little to help.
Since the Jungle Inferno Update clusterf***, I was wondering if anyone have a very up-to-date, ACCURATE + PRECISE cl_interp setting(s) without pulling my hair out trying to make it work. ALSO I would really be grateful if their where cl_interp ratios and update rates to go along with it as well. It would be much appreciated.
(*P.S. the settings I've tried range around cl_interp of 0.03ish or 0.015 with ratios of 1 or 2, and update rates of around 66ish. Also I have used this thread but not sure if it works anymore, here.)