Upvote Upvoted 3 Downvote Downvoted
Class specific configs?
1
#1
1 Frags +

i had class specific configs working before the steampipe update. after, all the class cfg's went away, leaving me with only autoexec.cfg to use. i tried making my own class specific cfg's, but when i do that, only certain class specific cfg's will load, and sometimes the commands in the cfg's wont work and some of them will carry over into other classes. its just a big mess.

can anybody explain/help me with this?

i had class specific configs working before the steampipe update. after, all the class cfg's went away, leaving me with only autoexec.cfg to use. i tried making my own class specific cfg's, but when i do that, only certain class specific cfg's will load, and sometimes the commands in the cfg's wont work and some of them will carry over into other classes. its just a big mess.

can anybody explain/help me with this?
2
#2
0 Frags +

did you put them in your custom cfg folder?

did you put them in your custom cfg folder?
3
#3
0 Frags +

no, i was putting them under /tf/cfg

no, i was putting them under /tf/cfg
4
#4
1 Frags +
z4chno, i was putting them under /tf/cfg

pop the config in the tf/custom/stuff/cfg folder

[quote=z4ch]no, i was putting them under /tf/cfg[/quote]
pop the config in the tf/custom/stuff/cfg folder
5
#5
0 Frags +
z4chno, i was putting them under /tf/cfg

I have all my configs in there and they work fine. If moving them doesnt work maybe try deleting them and validating?

[quote=z4ch]no, i was putting them under /tf/cfg[/quote]

I have all my configs in there and they work fine. If moving them doesnt work maybe try deleting them and validating?
6
#6
0 Frags +

make sure you're useing the correct directory. I think after steam pipe was released they changed where all you're local files were stored.
now it's Steam\steamapps\common\Team Fortress 2\tf\cfg
I think it used to be Steam\steamapps\USERNAME\team fortress 2\tf\cfg

you can also find the proper directory by clicking "browse local files" in the "local files" tab in tf2 properties.

make sure you're useing the correct directory. I think after steam pipe was released they changed where all you're local files were stored.
now it's Steam\steamapps\common\Team Fortress 2\tf\cfg
I think it used to be Steam\steamapps\USERNAME\team fortress 2\tf\cfg

you can also find the proper directory by clicking "browse local files" in the "local files" tab in tf2 properties.
7
#7
-1 Frags +
Alfiez4chno, i was putting them under /tf/cfgpop the config in the tf/custom/stuff/cfg folder

It isn't necessary to put your cfgs in custom folder.

I have my cfgs in tf/cfg and everything loads fine.

If the op's cfgs doesn't work properly then probably he had the code for each class configs wrong somewhere.

[quote=Alfie][quote=z4ch]no, i was putting them under /tf/cfg[/quote]
pop the config in the tf/custom/stuff/cfg folder[/quote]

It isn't necessary to put your cfgs in custom folder.

I have my cfgs in tf/cfg and everything loads fine.

If the op's cfgs doesn't work properly then probably he had the code for each class configs wrong somewhere.
8
#8
1 Frags +

The thing a lot of people still don't understand about the post-Steampipe update is that you can literally delete every class config file out of your tf/cfg folder. The only place you want (read: the only place TF2 actually looks for) your autoexec.cfg and class specific configs (medic.cfg, etc) are in your tf/custom/customcfg/cfg folder. I find doing this confuses me a lot less and gets rid of the clutter files. You literally do not need any class config file or autoexec file in your tf/cfg folder. Only config.cfg

The thing a lot of people still don't understand about the post-Steampipe update is that you can literally delete every class config file out of your tf/cfg folder. The only place you want (read: the only place TF2 actually looks for) your autoexec.cfg and class specific configs (medic.cfg, etc) are in your tf/custom/customcfg/cfg folder. I find doing this confuses me a lot less and gets rid of the clutter files. You literally do not need any class config file or autoexec file in your tf/cfg folder. Only config.cfg
9
#9
0 Frags +

so if i make all the class cfg's under the custom folder, they'll work?

so if i make all the class cfg's under the custom folder, they'll work?
10
#10
0 Frags +

Yes. For instance the path to your class cfg's will be "tf\custom\customcfgs\cfg\medic.cfg" etc.

Here's a visual:

http://i.imgur.com/sOGWtW9.jpg

Edit: For further visual clarification here is what your tf\cfg (the old place for cfgs) can now look like.

http://i.imgur.com/0GnQ9UH.jpg

Note there are no class cfgs at all in here. That's because TF2 doesn't look for them there anymore.

Yes. For instance the path to your class cfg's will be "tf\custom\customcfgs\cfg\medic.cfg" etc.

Here's a visual:

[img]http://i.imgur.com/sOGWtW9.jpg[/img]

Edit: For further visual clarification here is what your tf\cfg (the old place for cfgs) can now look like.

[img]http://i.imgur.com/0GnQ9UH.jpg[/img]

Note there are no class cfgs at all in here. That's because TF2 doesn't look for them there anymore.
11
#11
2 Frags +

I tried moving my cfgs to said location and custom cfgs stopped loading.

Put them back under tf/cfg and everything works again. Odd.

I tried moving my cfgs to said location and custom cfgs stopped loading.

Put them back under tf/cfg and everything works again. Odd.
12
#12
0 Frags +

What do you mean "stopped loading"?

What do you mean "stopped loading"?
13
#13
0 Frags +
thinkThe thing a lot of people still don't understand about the post-Steampipe update is that you can literally delete every class config file out of your tf/cfg folder. The only place you want (read: the only place TF2 actually looks for) your autoexec.cfg and class specific configs (medic.cfg, etc) are in your tf/custom/customcfg/cfg folder. I find doing this confuses me a lot less and gets rid of the clutter files. You literally do not need any class config file or autoexec file in your tf/cfg folder. Only config.cfg

Uh... dude, no. The root tf/cfg folder works perfectly fine for cfgs. I prefer it because it's a few less clicks away. Wherever you got this information, you are misinformed and are spreading false information. You can use your own custom folder for cfgs, or the root tf/cfg, either work perfectly fine. The thing you want to watch out for is having your cfgs in both places, that will cause confusion.

Moreover, I think that having your config.cfg in your root tf/cfg folder is necessary, and that's one reason why I think it's smarter to just keep the rest of your cfgs in that folder as well, so they're all in one place.

Oh and for the clutter you're talking about in the tf/cfg with all those extra default files, I simple mark those files as hidden, and voila, no more clutter.

[quote=think]The thing a lot of people still don't understand about the post-Steampipe update is that you can literally delete every class config file out of your tf/cfg folder. The only place you want (read: the only place TF2 actually looks for) your autoexec.cfg and class specific configs (medic.cfg, etc) are in your tf/custom/customcfg/cfg folder. I find doing this confuses me a lot less and gets rid of the clutter files. You literally do not need any class config file or autoexec file in your tf/cfg folder. Only config.cfg[/quote]


Uh... dude, no. The root tf/cfg folder works perfectly fine for cfgs. I prefer it because it's a few less clicks away. Wherever you got this information, you are misinformed and are spreading false information. You can use your own custom folder for cfgs, or the root tf/cfg, either work perfectly fine. The thing you want to watch out for is having your cfgs in [b]both[/b] places, that will cause confusion.

Moreover, I think that having your config.cfg in your root tf/cfg folder is necessary, and that's one reason why I think it's smarter to just keep the rest of your cfgs in that folder as well, so they're all in one place.

Oh and for the clutter you're talking about in the tf/cfg with all those extra default files, I simple mark those files as hidden, and voila, no more clutter.
14
#14
0 Frags +
thinkWhat do you mean "stopped loading"?

Any changes, such as viewmodel and sensitivity values aren't executed.

[quote=think]What do you mean "stopped loading"?[/quote]

Any changes, such as viewmodel and sensitivity values aren't executed.
15
#15
0 Frags +

crespi: I never said the root cfg folder doesn't work fine for cfgs. Obviously it works. The reason putting all your cfgs into the new Steampipe custom folder is a good idea is for consolidation purposes. Efficiency. If you're going to have custom things like addons, huds, cfgs, etc, it makes sense to utilize the new system and just put them all in one place- the new custom folder.

Sure you have the option to still use the old way, but you're not utilizing the new efficient Steampipe changes.

crespi: I never said the root cfg folder doesn't work fine for cfgs. Obviously it works. The reason putting all your cfgs into the new Steampipe custom folder is a good idea is for consolidation purposes. Efficiency. If you're going to have custom things like addons, huds, cfgs, etc, it makes sense to utilize the new system and just put them all in one place- the new custom folder.

Sure you have the option to still use the old way, but you're not utilizing the new efficient Steampipe changes.
16
#16
0 Frags +
DewotterthinkWhat do you mean "stopped loading"?
Any changes, such as viewmodel and sensitivity values aren't executed.

That's weird because it is working for me right now when I try. You must be doing it differently from me. Are you trying to do this after you launch tf2? Do it all before you start tf2 that way you make sure you're not editing, saving, and execing the wrong files.

[quote=Dewotter][quote=think]What do you mean "stopped loading"?[/quote]

Any changes, such as viewmodel and sensitivity values aren't executed.[/quote]

That's weird because it is working for me right now when I try. You must be doing it differently from me. Are you trying to do this after you launch tf2? Do it all before you start tf2 that way you make sure you're not editing, saving, and execing the wrong files.
17
#17
0 Frags +
thinkThe only place you want (read: the only place TF2 actually looks for) your autoexec.cfg and class specific configs (medic.cfg, etc) are in your tf/custom/customcfg/cfg folder

I took that as you claiming that tf/cfg doesn't work :s

[quote=think]The only place you want (read: the only place TF2 actually looks for) your autoexec.cfg and class specific configs (medic.cfg, etc) are in your tf/custom/customcfg/cfg folder[/quote]

I took that as you claiming that tf/cfg doesn't work :s
18
#18
0 Frags +

I can see how it could be interpreted like that, so sorry for the miscommunication on my part. The important point I am trying to get across is that it is more efficient (for storage, backup, and migration purposes) to just use the custom folder now. That's why it was made. It consolidates everything. It's beautiful. Valve loves us.

I can see how it could be interpreted like that, so sorry for the miscommunication on my part. The important point I am trying to get across is that it is more efficient (for storage, backup, and migration purposes) to just use the custom folder now. That's why it was made. It consolidates everything. It's beautiful. Valve loves us.
19
#19
1 Frags +
thinkI can see how it could be interpreted like that, so sorry for the miscommunication on my part. The important point I am trying to get across is that it is more efficient (for storage, backup, and migration purposes) to just use the custom folder now. That's why it was made. It consolidates everything. It's beautiful. Valve loves us.

Yeah I mostly agree. I just like the root cfg folder, I don't know why. My favorite part of the new system is the fact you can pack your hud into a vpk file.

[quote=think]I can see how it could be interpreted like that, so sorry for the miscommunication on my part. The important point I am trying to get across is that it is more efficient (for storage, backup, and migration purposes) to just use the custom folder now. That's why it was made. It consolidates everything. It's beautiful. Valve loves us.[/quote]

Yeah I mostly agree. I just like the root cfg folder, I don't know why. My favorite part of the new system is the fact you can pack your hud into a vpk file.
Please sign in through STEAM to post a comment.