I've been having a weird problem with my CFG's. When I join a game I can't do anything at all until I open console and do "exec scout_c" (or whatever class I'm spawned as) before I can play the game. Even when I am playing and I change class to sniper (where my CFG gives me different viewmodel settings) the settings will not take effect until i exec my sniper_c.cfg in the console. I'm pretty confused by this and I don't know if anyone else has had this problem. I also use brossel's crosshair switcher if that's relevant.
https://pastebin.com/mgqdF9Bw here's my scout cfg if it matters, all my class cfg's look exactly like this with the exception of the viewmodels at the very top, which are enabled for some classes and disabled for others.
I've been having a weird problem with my CFG's. When I join a game I can't do anything at all until I open console and do "exec scout_c" (or whatever class I'm spawned as) before I can play the game. Even when I am playing and I change class to sniper (where my CFG gives me different viewmodel settings) the settings will not take effect until i exec my sniper_c.cfg in the console. I'm pretty confused by this and I don't know if anyone else has had this problem. I also use brossel's crosshair switcher if that's relevant.
https://pastebin.com/mgqdF9Bw here's my scout cfg if it matters, all my class cfg's look exactly like this with the exception of the viewmodels at the very top, which are enabled for some classes and disabled for others.
Does your scout.cfg file have the line "exec scout_c" inside it? Same for each other class.
Does your scout.cfg file have the line "exec scout_c" inside it? Same for each other class.
if you're using mastercomfig it switched at some point to using a custom folder instead of filenames https://docs.mastercomfig.com/en/latest/customization/custom_configs/
docsYou can use user customization files to override specific settings in mastercomfig.
These are autoexec.cfg, which runs at game launch, and the 9 class configs (scout.cfg, soldier.cfg, pyro.cfg, demoman.cfg, heavyweapons.cfg, engineer.cfg, medic.cfg, sniper.cfg, and spy.cfg) which run on switching to a new class. All of these files go into a folder called user you create in tf/cfg.
if you're using mastercomfig it switched at some point to using a custom folder instead of filenames https://docs.mastercomfig.com/en/latest/customization/custom_configs/
[quote=docs]You can use user customization files to override specific settings in mastercomfig.
These are autoexec.cfg, which runs at game launch, and the 9 class configs (scout.cfg, soldier.cfg, pyro.cfg, demoman.cfg, heavyweapons.cfg, engineer.cfg, medic.cfg, sniper.cfg, and spy.cfg) which run on switching to a new class. All of these files go into a folder called user you create in tf/cfg.[/quote]
ireif you're using mastercomfig it switched at some point to using a custom folder instead of filenames https://docs.mastercomfig.com/en/latest/customization/custom_configs/
docsYou can use user customization files to override specific settings in mastercomfig.
These are autoexec.cfg, which runs at game launch, and the 9 class configs (scout.cfg, soldier.cfg, pyro.cfg, demoman.cfg, heavyweapons.cfg, engineer.cfg, medic.cfg, sniper.cfg, and spy.cfg) which run on switching to a new class. All of these files go into a folder called user you create in tf/cfg.
this is pretty messy (for me at least) i have a binds.cfg that the class.cfg executes but it doesn't read from tf/cfg/user/binds.cfg, it still reads from tf/custom/mystuff/cfg/binds.cfg.
edit: tried it out just now, if you want to execute other *.cfg files in tf/cfg/user/ you have to call them with exec user/*.cfg
[quote=ire]if you're using mastercomfig it switched at some point to using a custom folder instead of filenames https://docs.mastercomfig.com/en/latest/customization/custom_configs/
[quote=docs]You can use user customization files to override specific settings in mastercomfig.
These are autoexec.cfg, which runs at game launch, and the 9 class configs (scout.cfg, soldier.cfg, pyro.cfg, demoman.cfg, heavyweapons.cfg, engineer.cfg, medic.cfg, sniper.cfg, and spy.cfg) which run on switching to a new class. All of these files go into a folder called user you create in tf/cfg.[/quote][/quote]
this is pretty messy (for me at least) i have a binds.cfg that the class.cfg executes but it doesn't read from tf/cfg/user/binds.cfg, it still reads from tf/custom/mystuff/cfg/binds.cfg.
edit: tried it out just now, if you want to execute other *.cfg files in tf/cfg/user/ you have to call them with exec user/*.cfg
simple fix: rename scout_c.cfg (and any affected class cfgs) to scout.cfg
better fix: find out why they're called scout_c.cfg etc, report back
either way pls dump scout.cfg if it exists (if it doesnt, either create it and add "exec scout_c" to scout.cfg or rename scout_c like above)
(also before anyone says, if you exec a .cfg u dont need to include the .cfg extension. i think u can exec any file as exec by supplying an extension but i havent tested, only came up with the idea when i saw lowspecgamers doom eternal vid)
2nd also: refactor your configs so you have your null movement and sens and stuff in autoexec or reset so you only exec them once (and therefore only have to change them once should you want to) (you might want to look into scripting more if you dont know how to do that)
simple fix: rename scout_c.cfg (and any affected class cfgs) to scout.cfg
better fix: find out why they're called scout_c.cfg etc, report back
either way pls dump scout.cfg if it exists (if it doesnt, either create it and add "exec scout_c" to scout.cfg or rename scout_c like above)
(also before anyone says, if you exec a .cfg u dont need to include the .cfg extension. i think u can exec any file as exec by supplying an extension but i havent tested, only came up with the idea when i saw lowspecgamers doom eternal vid)
2nd also: refactor your configs so you have your null movement and sens and stuff in autoexec or reset so you only exec them once (and therefore only have to change them once should you want to) (you might want to look into scripting more if you dont know how to do that)
Pizzza-blyatsimple fix: rename scout_c.cfg (and any affected class cfgs) to scout.cfg
better fix: find out why they're called scout_c.cfg etc, report back
either way pls dump scout.cfg if it exists (if it doesnt, either create it and add "exec scout_c" to scout.cfg or rename scout_c like above)
(also before anyone says, if you exec a .cfg u dont need to include the .cfg extension. i think u can exec any file as exec by supplying an extension but i havent tested, only came up with the idea when i saw lowspecgamers doom eternal vid)
2nd also: refactor your configs so you have your null movement and sens and stuff in autoexec or reset so you only exec them once (and therefore only have to change them once should you want to) (you might want to look into scripting more if you dont know how to do that)
thank you for the advice. I will try this. Somewhere I could have absolutely sworn that the thing to do now was calling them scout_c or pyro_c or engineer_c rather than the normal classname.cfg. I haven't played in a very long time but I definitely remember this being a thing some point relatively recently like a year ago.
Yeah I know that the null movement stuff should be in an autoexec but I made all these cfg's in like 2014 and by the time I knew that it should just go in an autoexec it didn't matter to me because that's never really caused me any problems so I never bothered to do that,
[quote=Pizzza-blyat]simple fix: rename scout_c.cfg (and any affected class cfgs) to scout.cfg
better fix: find out why they're called scout_c.cfg etc, report back
either way pls dump scout.cfg if it exists (if it doesnt, either create it and add "exec scout_c" to scout.cfg or rename scout_c like above)
(also before anyone says, if you exec a .cfg u dont need to include the .cfg extension. i think u can exec any file as exec by supplying an extension but i havent tested, only came up with the idea when i saw lowspecgamers doom eternal vid)
2nd also: refactor your configs so you have your null movement and sens and stuff in autoexec or reset so you only exec them once (and therefore only have to change them once should you want to) (you might want to look into scripting more if you dont know how to do that)[/quote]
thank you for the advice. I will try this. Somewhere I could have absolutely sworn that the thing to do now was calling them scout_c or pyro_c or engineer_c rather than the normal classname.cfg. I haven't played in a very long time but I definitely remember this being a thing some point relatively recently like a year ago.
Yeah I know that the null movement stuff should be in an autoexec but I made all these cfg's in like 2014 and by the time I knew that it should just go in an autoexec it didn't matter to me because that's never really caused me any problems so I never bothered to do that,
SevenSomewhere I could have absolutely sworn that the thing to do now was calling them scout_c or pyro_c or engineer_c
This is a deprecated mastercomfig feature. If you want to continue using mastercomfig, make sure you're on the newest version and move your custom configs into a subdirectory called "user" eg. /cfg/user/scout.cfg
Also make sure that if you are calling execs inside your class configs and you move them into the user subdirectory that you use exec user/configname.cfg. A lot of people get stuck on that when porting their config folder to new mastercomfig.
If you don't want to continue using mastercomfig, rename your class configs back to their original class names without the _c.
[quote=Seven]Somewhere I could have absolutely sworn that the thing to do now was calling them scout_c or pyro_c or engineer_c[/quote]
This is a deprecated mastercomfig feature. If you want to continue using mastercomfig, make sure you're on the newest version and move your custom configs into a subdirectory called "user" eg. /cfg/user/scout.cfg
Also make sure that if you are calling execs inside your class configs and you move them into the user subdirectory that you use exec user/configname.cfg. A lot of people get stuck on that when porting their config folder to new mastercomfig.
If you don't want to continue using mastercomfig, rename your class configs back to their original class names without the _c.
scrambledSevenSomewhere I could have absolutely sworn that the thing to do now was calling them scout_c or pyro_c or engineer_c
This is a deprecated mastercomfig feature. If you want to continue using mastercomfig, make sure you're on the newest version and move your custom configs into a subdirectory called "user" eg. /cfg/user/scout.cfg
Also make sure that if you are calling execs inside your class configs and you move them into the user subdirectory that you use exec user/configname.cfg. A lot of people get stuck on that when porting their config folder to new mastercomfig.
If you don't want to continue using mastercomfig, rename your class configs back to their original class names without the _c.
can we just post this thread next time mastercom asks why we just want a simple gfx.cfg
[quote=scrambled][quote=Seven]Somewhere I could have absolutely sworn that the thing to do now was calling them scout_c or pyro_c or engineer_c[/quote]
This is a deprecated mastercomfig feature. If you want to continue using mastercomfig, make sure you're on the newest version and move your custom configs into a subdirectory called "user" eg. /cfg/user/scout.cfg
Also make sure that if you are calling execs inside your class configs and you move them into the user subdirectory that you use exec user/configname.cfg. A lot of people get stuck on that when porting their config folder to new mastercomfig.
If you don't want to continue using mastercomfig, rename your class configs back to their original class names without the _c.[/quote]
can we just post this thread next time mastercom asks why we just want a simple gfx.cfg
crackbabydumpstercan we just post this thread next time mastercom asks why we just want a simple gfx.cfg
exec this
https://github.com/mastercoms/mastercomfig/blob/release/config/mastercomfig/cfg/comfig/comfig.cfg
then exec one of these
https://github.com/mastercoms/mastercomfig/tree/release/config/cfg/presets
Would probably be shit in comparison to what features the comfig has to offer but its there.
In an ideal world the the config wouldn't undergo any design changes breaking old features, but shit happens I guess.
https://docs.mastercomfig.com/en/stable/setup/install/
[quote=crackbabydumpster]
can we just post this thread next time mastercom asks why we just want a simple gfx.cfg[/quote]
exec this
https://github.com/mastercoms/mastercomfig/blob/release/config/mastercomfig/cfg/comfig/comfig.cfg
then exec one of these
https://github.com/mastercoms/mastercomfig/tree/release/config/cfg/presets
Would probably be shit in comparison to what features the comfig has to offer but its there.
In an ideal world the the config wouldn't undergo any design changes breaking old features, but shit happens I guess.
https://docs.mastercomfig.com/en/stable/setup/install/