While cloaked in first person, in spectator or while alive, spy's arms don't have the cloak effect.
Is there any way to fix this, or to know what causes the problem? I have tried to verify cache, uninstalling mods, removing cfgs, etc.
edit: Happened seemingly after transparent viewmodels were installed.
While cloaked in first person, in spectator or while alive, spy's arms [url=https://i.imgur.com/Kw8YzVI.jpg]don't have the cloak effect[/url].
Is there any way to fix this, or to know what causes the problem? I have tried to verify cache, uninstalling mods, removing cfgs, etc.
edit: Happened seemingly after transparent viewmodels were installed.
removing your autoexec does not reset your settings, you have to run the game with the -default launch option
removing your autoexec does not reset your settings, you have to run the game with the -default launch option
yttrium you have to run the game with the -default launch option
I tried this, still didn't work. Thanks for the tip, though!
[quote=yttrium] you have to run the game with the -default launch option[/quote]
I tried this, still didn't work. Thanks for the tip, though!
yttriumremoving your autoexec does not reset your settings, you have to run the game with the -default launch option
-default only sets your settings to default for THAT launch, and prevents you from changing them. its good for quickly trouble shooting
it doesn't reset your settings, remove your autoexec and custom folder and use -autconfig and host_writeconfig (in console) for that
[quote=yttrium]removing your autoexec does not reset your settings, you have to run the game with the -default launch option[/quote]
-default only sets your settings to default for THAT launch, and prevents you from changing them. its good for quickly trouble shooting
it doesn't reset your settings, remove your autoexec and custom folder and use -autconfig and host_writeconfig (in console) for that
gemmyttriumremoving your autoexec does not reset your settings, you have to run the game with the -default launch option
-default only sets your settings to default for THAT launch, and prevents you from changing them. its good for quickly trouble shooting
it doesn't reset your settings, remove your autoexec and custom folder and use -autconfig and host_writeconfig (in console) for that
It just forces them for that boot and would be a good way to see if it's a config issue or not, without completely wiping settings.
I could have explained writeconfig and that sort of thing but I didn't want to basically delete his config files without seeing if it would even help.
OP, what other launch options do you run with? What are your system specs and OS?
[quote=gemm][quote=yttrium]removing your autoexec does not reset your settings, you have to run the game with the -default launch option[/quote]
-default only sets your settings to default for THAT launch, and prevents you from changing them. its good for quickly trouble shooting
it doesn't reset your settings, remove your autoexec and custom folder and use -autconfig and host_writeconfig (in console) for that[/quote]
It just forces them for that boot and would be a good way to see if it's a config issue or not, without completely wiping settings.
I could have explained writeconfig and that sort of thing but I didn't want to basically delete his config files without seeing if it would even help.
OP, what other launch options do you run with? What are your system specs and OS?
yttriumIt just forces them for that boot and would be a good way to see if it's a config issue or not, without completely wiping settings.
I could have explained writeconfig and that sort of thing but I didn't want to basically delete his config files without seeing if it would even help.
OP, what other launch options do you run with? What are your system specs and OS?
Ok, mild necro. I stopped playing TF2 for a while and when I finally came back the glitch stayed.
default didn't work.
Launch options: -w 1400 -h 1050 -novid -nojoy -useforcedmparms -noforcemspd -noforcemaccel -dxlevel 81 -reuse -high -threads 8 -full
Specs: 16GB ram, 8 threads 4 cores intel I7 @ 2.60GHz, Windows 10
[quote=yttrium]
It just forces them for that boot and would be a good way to see if it's a config issue or not, without completely wiping settings.
I could have explained writeconfig and that sort of thing but I didn't want to basically delete his config files without seeing if it would even help.
OP, what other launch options do you run with? What are your system specs and OS?[/quote]
Ok, mild necro. I stopped playing TF2 for a while and when I finally came back the glitch stayed.
default didn't work.
Launch options: -w 1400 -h 1050 -novid -nojoy -useforcedmparms -noforcemspd -noforcemaccel -dxlevel 81 -reuse -high -threads 8 -full
Specs: 16GB ram, 8 threads 4 cores intel I7 @ 2.60GHz, Windows 10
useforcedmparms stands for use forced man paris arms
useforcedmparms stands for use forced man paris arms
pyxelizeuse forced man paris arms
Of course! What a dunce I was, just unforce the arms so they become invisible!
[quote=pyxelize]use forced man paris arms[/quote]
Of course! What a dunce I was, just unforce the arms so they become invisible!
do everything in this little github snippet from mastercomms (here)
reinstall/update graphics drivers
verify game files
completely remove your custom folder (you can rename it to have a _ at the end and it wont be read by tf2, also works)
if none of that works try literally just deleting the team fortress 2 folder and just reinstall from scratch
post your cfg/custom if that doesnt work
do everything in this little github snippet from mastercomms ([url=https://github.com/mastercoms/mastercomfig#clean-up]here[/url])
reinstall/update graphics drivers
verify game files
completely remove your custom folder (you can rename it to have a _ at the end and it wont be read by tf2, also works)
if none of that works try literally just deleting the team fortress 2 folder and just reinstall from scratch
post your cfg/custom if [i]that[/i] doesnt work
Reinstalling worked, after readding my CFGs one at a time then mods, I found the issue. Outdated HUD screwed some stuff up.
Reinstalling worked, after readding my CFGs one at a time then mods, I found the issue. Outdated HUD screwed some stuff up.