Upvote Upvoted 0 Downvote Downvoted
Console Output on Launch
posted in Q/A Help
1
#1
-2 Frags +

For as long as I can remember, right after launch my console has been displaying odd output. Things like,

Can't use cheat cvar fog_start in multiplayer, unless the server has sv_cheats set to 1.

There are a good amount of these lines for various cvars that tf2 seems to want to exec, even though I've never set them to exec in the first place. There is also an output of

Unknown command "sv_backspeed"

in the mix.

The obvious thing I checked was the config.cfg file, and sure enough almost all of these were there. However, because of steam cloud I haven't been able to modify the config.cfg permanently. I've tried pretty much every fix I've found through googling (eg. http://forums.steampowered.com/forums/showthread.php?p=22112149) but they haven't worked. I've ended up having to read-only my config.cfg file (both in cfg/ and in the steam cloud path under userdata/) and manually edit the files myself. While this works for the most part any change I make in game is only temporary now (since it cannot be written to the config.cfg file.) Slightly annoying, but I can live with, although if anybody knows of a real fix let me know.

However, and this brings me to the real question, not all of the "bad" output is gone. I still have the following lines:

Connection to game coordinator established.
CTFGCClientSystem::PostInitGC
CTFGCClientSystem - adding listener
Loading default settings for high sensitivity
Loading default settings for high sensitivity
------------Autoexec loading.------------
------------Chris' dx9frames config loading.-----------
------------Chris' dx9frames config loaded.------------ 
Not playing a local game.
------------Autoexec loaded.-------------
Can't use cheat cvar fog_start in multiplayer, unless the server has sv_cheats set to 1.
Can't use cheat cvar fog_end in multiplayer, unless the server has sv_cheats set to 1.
Can't use cheat cvar fog_startskybox in multiplayer, unless the server has sv_cheats set to 1.
Can't use cheat cvar fog_endskybox in multiplayer, unless the server has sv_cheats set to 1.
Can't use cheat cvar r_farz in multiplayer, unless the server has sv_cheats set to 1.

The first three lines seem like "good" output so I'm not really worried about them. The same thing goes for chris' frames/autoexec lines (I just left them in so you can see that the problems occur before and after the autoexec is executed, not during). However, everything else seems like it shouldn't be there. I've grepped the lines and searched my entire tf/ directory and the only hits are in bin/client.dll and bin/client.dylib, both of which are uneditable files. Is there anyway for me to remove these offending lines, or am I just stuck with a bunch of sv_cheats cvars and some unknown high sensitivity setting that really want to execute on launch?

For as long as I can remember, right after launch my console has been displaying odd output. Things like,
[code]Can't use cheat cvar fog_start in multiplayer, unless the server has sv_cheats set to 1.[/code]
There are a good amount of these lines for various cvars that tf2 seems to want to exec, even though I've never set them to exec in the first place. There is also an output of
[code]Unknown command "sv_backspeed"[/code] in the mix.

The obvious thing I checked was the config.cfg file, and sure enough almost all of these were there. However, because of steam cloud I haven't been able to modify the config.cfg permanently. I've tried pretty much every fix I've found through googling (eg. http://forums.steampowered.com/forums/showthread.php?p=22112149) but they haven't worked. I've ended up having to read-only my config.cfg file (both in cfg/ and in the steam cloud path under userdata/) and manually edit the files myself. While this works for the most part any change I make in game is only temporary now (since it cannot be written to the config.cfg file.) Slightly annoying, but I can live with, although if anybody knows of a real fix let me know.

However, and this brings me to the real question, not all of the "bad" output is gone. I still have the following lines:

[code]
Connection to game coordinator established.
CTFGCClientSystem::PostInitGC
CTFGCClientSystem - adding listener
Loading default settings for high sensitivity
Loading default settings for high sensitivity
------------Autoexec loading.------------
------------Chris' dx9frames config loading.-----------
------------Chris' dx9frames config loaded.------------
Not playing a local game.
------------Autoexec loaded.-------------
Can't use cheat cvar fog_start in multiplayer, unless the server has sv_cheats set to 1.
Can't use cheat cvar fog_end in multiplayer, unless the server has sv_cheats set to 1.
Can't use cheat cvar fog_startskybox in multiplayer, unless the server has sv_cheats set to 1.
Can't use cheat cvar fog_endskybox in multiplayer, unless the server has sv_cheats set to 1.
Can't use cheat cvar r_farz in multiplayer, unless the server has sv_cheats set to 1.
[/code]

The first three lines seem like "good" output so I'm not really worried about them. The same thing goes for chris' frames/autoexec lines (I just left them in so you can see that the problems occur before and after the autoexec is executed, not during). However, everything else seems like it shouldn't be there. I've grepped the lines and searched my entire tf/ directory and the only hits are in bin/client.dll and bin/client.dylib, both of which are uneditable files. Is there anyway for me to remove these offending lines, or am I just stuck with a bunch of sv_cheats cvars and some unknown high sensitivity setting that really want to execute on launch?
2
#2
3 Frags +

Are they doing you harm?

Are they doing you harm?
3
#3
0 Frags +

No, not at all since all the commands are blocked by sv_cheats. However, they clog up the console and can make it confusing to figure out if I really do have a problem with my configs.

No, not at all since all the commands are blocked by sv_cheats. However, they clog up the console and can make it confusing to figure out if I really do have a problem with my configs.
Please sign in through STEAM to post a comment.