I cannot play in comp or have fun in it. I've been getting lag every 10-20 seconds with sound loops. I tried vanilla tf2 and verifying my files. Any solution? Here is a link to a demo I recorded: https://www.dropbox.com/s/bt55t1hr8sofolj/lag.dem?dl=0
TF2 comp lag
posted in
Q/A Help
I cannot play in comp or have fun in it. I've been getting lag every 10-20 seconds with sound loops. I tried vanilla tf2 and verifying my files. Any solution? Here is a link to a demo I recorded: https://www.dropbox.com/s/bt55t1hr8sofolj/lag.dem?dl=0
is tf2 installed on your main hard drive (the same one that houses your windows installation) or on a secondary hard drive?
if it's the latter, reinstall it on your main hard drive.
otherwise, check your DPC latency.
is tf2 installed on your main hard drive (the same one that houses your windows installation) or on a secondary hard drive?
if it's the latter, reinstall it on your main hard drive.
otherwise, check your DPC latency.
if it's the latter, reinstall it on your main hard drive.
otherwise, check your DPC latency.
joshuawnis tf2 installed on your main hard drive (the same one that houses your windows installation) or on a secondary hard drive?
if it's the latter, reinstall it on your main hard drive.
otherwise, check your DPC latency.
Yes, it is installed on my ssd which also has windows on it.
[quote=joshuawn]is tf2 installed on your main hard drive (the same one that houses your windows installation) or on a secondary hard drive?
if it's the latter, reinstall it on your main hard drive.
otherwise, check your DPC latency.[/quote]
Yes, it is installed on my ssd which also has windows on it.
if it's the latter, reinstall it on your main hard drive.
otherwise, check your DPC latency.[/quote]
Yes, it is installed on my ssd which also has windows on it.
http://www.resplendence.com/latencymon
use this tool while you're playing tf2. after the 10 second freeze/sound loop occurs, pause the scan and see if it's caused by an abnormally high DPC or ISR execution time.
also, ensure that you don't have any antivirus or malware suites running in the background.
http://www.resplendence.com/latencymon
use this tool while you're playing tf2. after the 10 second freeze/sound loop occurs, pause the scan and see if it's caused by an abnormally high DPC or ISR execution time.
also, ensure that you don't have any antivirus or malware suites running in the background.
use this tool while you're playing tf2. after the 10 second freeze/sound loop occurs, pause the scan and see if it's caused by an abnormally high DPC or ISR execution time.
also, ensure that you don't have any antivirus or malware suites running in the background.
joshuawnhttp://www.resplendence.com/latencymon
use this tool while you're playing tf2. after the 10 second freeze/sound loop occurs, pause the scan and see if it's caused by an abnormally high DPC or ISR execution time.
also, ensure that you don't have any antivirus or malware suites running in the background.
Here are screenshots of the results
http://puu.sh/q6R7z/30757246ba.png
http://puu.sh/q6Rbi/f0cce91028.png
I'm pretty sure this is a fault on Valves part and not mine. I do fine in any TF2 mode except for competitive. The screenshots were even the same with lag and no lag.
[quote=joshuawn]http://www.resplendence.com/latencymon
use this tool while you're playing tf2. after the 10 second freeze/sound loop occurs, pause the scan and see if it's caused by an abnormally high DPC or ISR execution time.
also, ensure that you don't have any antivirus or malware suites running in the background.[/quote]
Here are screenshots of the results
http://puu.sh/q6R7z/30757246ba.png
http://puu.sh/q6Rbi/f0cce91028.png
I'm pretty sure this is a fault on Valves part and not mine. I do fine in any TF2 mode except for competitive. The screenshots were even the same with lag and no lag.
use this tool while you're playing tf2. after the 10 second freeze/sound loop occurs, pause the scan and see if it's caused by an abnormally high DPC or ISR execution time.
also, ensure that you don't have any antivirus or malware suites running in the background.[/quote]
Here are screenshots of the results
http://puu.sh/q6R7z/30757246ba.png
http://puu.sh/q6Rbi/f0cce91028.png
I'm pretty sure this is a fault on Valves part and not mine. I do fine in any TF2 mode except for competitive. The screenshots were even the same with lag and no lag.
even if your symptoms isolated in competitive matchmaking, freezes & sound loops aren't normal. engine stalls due to parts of the VAC authentication & scanning methods choking would cause similar issues, but they shouldn't happen in such a consistent manner nor in isolation.
what are your current launch options?
regardless of the same issues occurring with vanilla TF2, upload your normally used autoexec.cfg. if it loads any additional config files with the exec command, upload those too.
even if your symptoms isolated in competitive matchmaking, freezes & sound loops aren't normal. engine stalls due to parts of the VAC authentication & scanning methods choking would cause similar issues, but they shouldn't happen in such a consistent manner nor in isolation.
what are your current launch options?
regardless of the same issues occurring with vanilla TF2, upload your normally used autoexec.cfg. if it loads any additional config files with the exec command, upload those too.
what are your current launch options?
regardless of the same issues occurring with vanilla TF2, upload your normally used autoexec.cfg. if it loads any additional config files with the exec command, upload those too.
joshuawneven if your symptoms isolated in competitive matchmaking, freezes & sound loops aren't normal. engine stalls due to parts of the VAC authentication & scanning methods choking would cause similar issues, but they shouldn't happen in such a consistent manner nor in isolation.
what are your current launch options?
regardless of the same issues occurring with vanilla TF2, upload your normally used autoexec.cfg. if it loads any additional config files with the exec command, upload those too.
My launch options are:
-dxlevel 90 -full -w WIDTH -h HEIGHT -console -novid -useforcedmparms -noforcemaccel -noforcemspd
and I use this config
https://www.dropbox.com/sh/zajzketx79hkwbd/AACCAqPPDWOZHzqULfQWQu98a?dl=0
[quote=joshuawn]even if your symptoms isolated in competitive matchmaking, freezes & sound loops aren't normal. engine stalls due to parts of the VAC authentication & scanning methods choking would cause similar issues, but they shouldn't happen in such a consistent manner nor in isolation.
what are your current launch options?
regardless of the same issues occurring with vanilla TF2, upload your normally used autoexec.cfg. if it loads any additional config files with the exec command, upload those too.[/quote]
My launch options are:
-dxlevel 90 -full -w WIDTH -h HEIGHT -console -novid -useforcedmparms -noforcemaccel -noforcemspd
and I use this config
https://www.dropbox.com/sh/zajzketx79hkwbd/AACCAqPPDWOZHzqULfQWQu98a?dl=0
what are your current launch options?
regardless of the same issues occurring with vanilla TF2, upload your normally used autoexec.cfg. if it loads any additional config files with the exec command, upload those too.[/quote]
My launch options are:
-dxlevel 90 -full -w WIDTH -h HEIGHT -console -novid -useforcedmparms -noforcemaccel -noforcemspd
and I use this config
https://www.dropbox.com/sh/zajzketx79hkwbd/AACCAqPPDWOZHzqULfQWQu98a?dl=0
dxlevel should only be specified on the first launch of the game; it will persist across all game launches after it is removed. also, get rid of the "mat_dxlevel 90" in your autoexec.cfg. ensure that cloud saving isn't enabled for tf2 either.
close tf2, get rid of the dxlevel launch option, and relaunch the game see if you still stall during matchmaking.
if you do, try -dxlevel 95 and -dxlevel 98 (removing it after the first launch) to see if you still stall.
i also noticed that -dxlevel behaves erroneously after the meet your match update; dxlevel would revert to 95 regardless of what i specified. i had to use +mat_dxlevel to force specific modes.
ensure that this isn't the case for you by going into console after the game launches & typing in mat_dxlevel.
otherwise, +mat_dxlevel 90, +mat_dxlevel 95, and +mat_dxlevel 98 can be used to substitute the respective -dxlevel launch options (and just like -dxlevel, it should be removed after the first launch).
also, get rid of useforcedmparms, noforcemaccel, and noforcemspd. those launch options are deprecated; rawinput will handle it all.
dxlevel should only be specified on the first launch of the game; it will persist across all game launches after it is removed. also, get rid of the "mat_dxlevel 90" in your autoexec.cfg. ensure that cloud saving isn't enabled for tf2 either.
close tf2, get rid of the dxlevel launch option, and relaunch the game see if you still stall during matchmaking.
if you do, try -dxlevel 95 and -dxlevel 98 (removing it after the first launch) to see if you still stall.
i also noticed that -dxlevel behaves erroneously after the meet your match update; dxlevel would revert to 95 regardless of what i specified. i had to use +mat_dxlevel to force specific modes.
ensure that this isn't the case for you by going into console after the game launches & typing in mat_dxlevel.
otherwise, +mat_dxlevel 90, +mat_dxlevel 95, and +mat_dxlevel 98 can be used to substitute the respective -dxlevel launch options (and just like -dxlevel, it should be removed after the first launch).
also, get rid of useforcedmparms, noforcemaccel, and noforcemspd. those launch options are deprecated; rawinput will handle it all.
close tf2, get rid of the dxlevel launch option, and relaunch the game see if you still stall during matchmaking.
if you do, try -dxlevel 95 and -dxlevel 98 (removing it after the first launch) to see if you still stall.
i also noticed that -dxlevel behaves erroneously after the meet your match update; dxlevel would revert to 95 regardless of what i specified. i had to use +mat_dxlevel to force specific modes.
ensure that this isn't the case for you by going into console after the game launches & typing in mat_dxlevel.
otherwise, +mat_dxlevel 90, +mat_dxlevel 95, and +mat_dxlevel 98 can be used to substitute the respective -dxlevel launch options (and just like -dxlevel, it should be removed after the first launch).
also, get rid of useforcedmparms, noforcemaccel, and noforcemspd. those launch options are deprecated; rawinput will handle it all.
I never kept the launch options in after the first launch. I tried dx 95 and removed the unnecessary options you told me to get rid of, but there is no change. Check my dx level by typing mat_dxlevel. I didn't have these problems in the early beta of mm though. Don't know how Valve ruined it for me.
I never kept the launch options in after the first launch. I tried dx 95 and removed the unnecessary options you told me to get rid of, but there is no change. Check my dx level by typing mat_dxlevel. I didn't have these problems in the early beta of mm though. Don't know how Valve ruined it for me.
Please
sign in through STEAM
to post a comment.