Upvote Upvoted 3 Downvote Downvoted
1 2
Autoexec not working.
posted in Q/A Help
1
#1
2 Frags +

My autoexec won't load when I launch TF2. Executing it through the console doesn't work either. If I try to exec "autoexec.cfg", nothing happens and nothing is said in console as if it worked. When I try to exec "autoexec", without .cfg, it says it couldn't be found. I've tried placing it in the tf folder's cfg folder, I've tried placing it in a cfg folder in /custom/ and I've tried placing it in /custom/ by itself. None of the 3 worked.

Help?

My autoexec won't load when I launch TF2. Executing it through the console doesn't work either. If I try to exec "autoexec.cfg", nothing happens and nothing is said in console as if it worked. When I try to exec "autoexec", without .cfg, it says it couldn't be found. I've tried placing it in the tf folder's cfg folder, I've tried placing it in a cfg folder in /custom/ and I've tried placing it in /custom/ by itself. None of the 3 worked.

Help?
2
#2
1 Frags +

should be in custom/anotherfolder/cfg

should be in custom/anotherfolder/cfg
3
#3
0 Frags +

http://i.imgur.com/HVoI1Ub.png

[img]http://i.imgur.com/HVoI1Ub.png[/img]
4
#4
4 Frags +

make sure the file extension is actually a .cfg not a text file called autoexec.cfg with .txt hidden at the end

make sure the file extension is actually a .cfg not a text file called autoexec.cfg with .txt hidden at the end
5
#5
16 Frags +
scybezshould be in custom/anotherfolder/cfg

really? mine is common/teamfortress2/tf/cfg

[quote=scybez]should be in custom/anotherfolder/cfg[/quote]

really? mine is common/teamfortress2/tf/cfg
6
#6
4 Frags +
martenscybezshould be in custom/anotherfolder/cfg
really? mine is common/teamfortress2/tf/cfg

Both should work the same way.

[quote=marten][quote=scybez]should be in custom/anotherfolder/cfg[/quote]

really? mine is common/teamfortress2/tf/cfg[/quote]
Both should work the same way.
7
#7
1 Frags +
EdLolingtonmake sure the file extension is actually a .cfg not a text file called autoexec.cfg with .txt hidden at the end

The type of file is CFG like it should be.

[quote=EdLolington]make sure the file extension is actually a .cfg not a text file called autoexec.cfg with .txt hidden at the end[/quote]

The type of file is CFG like it should be.
8
#8
0 Frags +

bump

bump
9
#9
1 Frags +

Can you manually exec other files in cfg?

Can you manually exec other files in cfg?
10
#10
1 Frags +

Does executing your class configs work?

Does executing your class configs work?
11
#11
0 Frags +

I'll have to try that later.

I'll have to try that later.
12
#12
0 Frags +

Executing class configs come up as it not being there, regardless if i add .cfg or not to the end of the exec command. I placed a class config in all areas that it would seem appropriate (tf's cfg folder and /custom/cfg/).

Executing class configs come up as it not being there, regardless if i add .cfg or not to the end of the exec command. I placed a class config in all areas that it would seem appropriate (tf's cfg folder and /custom/cfg/).
13
#13
0 Frags +

Is the autoexec file actually a cfg file rather than a generic file without an extension? Also, sometimes the Source Engine doesn't like spaces (for example, you can't watch a demo that has a space in it). Try replacing the spaces with underscores?

[s]Is the autoexec file actually a cfg file rather than a generic file without an extension? [/s]Also, sometimes the Source Engine doesn't like spaces (for example, you can't watch a demo that has a space in it). Try replacing the spaces with underscores?
14
#14
0 Frags +

I tried removing the spaces from the folder name and that didn't work.

I'm not sure why this isn't working. My HUD is working just fine and I have that set in the tf folder and the folder inside of the custom folder.

I tried removing the spaces from the folder name and that didn't work.

I'm not sure why this isn't working. My HUD is working just fine and I have that set in the tf folder and the folder inside of the custom folder.
15
#15
0 Frags +

your configs should be in /custom/randomname/cfg not /custom/cfg

your configs should be in /custom/randomname/cfg not /custom/cfg
16
#16
-2 Frags +

That's what it's in @_@

That's what it's in @_@
17
#17
4 Frags +
kirbyThat's what it's in @_@kirby(tf's cfg folder and /custom/cfg/).
[quote=kirby]That's what it's in @_@[/quote]
[quote=kirby](tf's cfg folder and /custom/cfg/).[/quote]
18
#18
0 Frags +

Have you tried installing someone elses config to see if your cfg files are broken?

Have you tried installing someone elses config to see if your cfg files are broken?
19
#19
1 Frags +

This happened to me too. For some reason, TF2 was reading the file from /tf/cfg, and NOT from /tf/custom/userstuff/cfg. Regardless of the changes I made to the autoexec (or any other config in the custom folder), TF2 would read from the regular cfg folder in /tf/. I don't know why it did that. I backed up my TF folder, then deleted it entirely. Reinstalled the custom stuff (hud, configs including autoexec) in the proper location (tf/custom/userstuff) and it worked.

Pain in the ass, but shouldn't take more than 20min to rectify. I suppose you could edit the files in /tf/cfg but then you'll have multiple copies of your configs floating around and it gets to be a mess. Especially if tf2 decided to start reading from the correct location at some point in the future.

This happened to me too. For some reason, TF2 was reading the file from /tf/cfg, and NOT from /tf/custom/userstuff/cfg. Regardless of the changes I made to the autoexec (or any other config in the custom folder), TF2 would read from the regular cfg folder in /tf/. I don't know why it did that. I backed up my TF folder, then deleted it entirely. Reinstalled the custom stuff (hud, configs including autoexec) in the proper location (tf/custom/userstuff) and it worked.

Pain in the ass, but shouldn't take more than 20min to rectify. I suppose you could edit the files in /tf/cfg but then you'll have multiple copies of your configs floating around and it gets to be a mess. Especially if tf2 decided to start reading from the correct location at some point in the future.
20
#20
0 Frags +
Goat_kirbyThat's what it's in @_@kirby(tf's cfg folder and /custom/cfg/).

Maybe I messed up with my writing somewhere. I have my cfg folder inside of /custom/randomfolder.

#18 All I have is the same movement script I've used for the last year and Chris' max FPS config.

#19 Even if it was reading it from /tf/cfg, it should still work. But I know it's reading my custom folder and its contents as my custom HUD works. I'll probably just reinstall TF2. I remember that upon first reinstalling it that it was giving me some error about the search path in /custom/. Not sure how I fixed it. I want to think TF2 is completely ignoring that folder, but that wouldn't make sense as my HUD works. I do, however, have my custom HUD in my custom folder as well as the TF folder, but it was working before adding it to the TF folder.

[quote=Goat_][quote=kirby]That's what it's in @_@[/quote]
[quote=kirby](tf's cfg folder and /custom/cfg/).[/quote][/quote]

Maybe I messed up with my writing somewhere. I have my cfg folder inside of /custom/randomfolder.

#18 All I have is the same movement script I've used for the last year and Chris' max FPS config.

#19 Even if it was reading it from /tf/cfg, it should still work. But I know it's reading my custom folder and its contents as my custom HUD works. I'll probably just reinstall TF2. I remember that upon first reinstalling it that it was giving me some error about the search path in /custom/. Not sure how I fixed it. I want to think TF2 is completely ignoring that folder, but that wouldn't make sense as my HUD works. I do, however, have my custom HUD in my custom folder as well as the TF folder, but it was working before adding it to the TF folder.
21
#21
0 Frags +

bump

bump
22
#22
-1 Frags +

SteamApps\common\Team Fortress 2\tf\custom\MY CUSTOMIZED\config\cfg

as per the instructions here - http://tf2cfg.info/help.php

adding the \config\cfg folders got it working for me.

With autoexec residing in the cfg folder.

good luck

SteamApps\common\Team Fortress 2\tf\custom\MY CUSTOMIZED\config\cfg

as per the instructions here - http://tf2cfg.info/help.php

adding the \config\cfg folders got it working for me.

With autoexec residing in the cfg folder.

good luck
23
#23
0 Frags +

Did you make any recent changes to your config? If so detail them out.

Did you make any recent changes to your config? If so detail them out.
24
#24
0 Frags +

#22 I'll try that

Think, no. I installed a brand new HDD and did a fresh config install w/ Chris' max FPS.

#22 I'll try that

Think, no. I installed a brand new HDD and did a fresh config install w/ Chris' max FPS.
25
#25
1 Frags +

You should upload your entire cfg folder somewhere and share it. I'll take a look through it to see if I can find anything wacky.

You should upload your entire cfg folder somewhere and share it. I'll take a look through it to see if I can find anything wacky.
26
#26
0 Frags +

http://www.mediafire.com/?fxq08tm8s9jd6qn

http://www.mediafire.com/?fxq08tm8s9jd6qn
27
#27
0 Frags +

Dumb question, but do you have autoexec.cfg saved as all files?

Dumb question, but do you have autoexec.cfg saved as all files?
28
#28
-1 Frags +

All files are set to their appropriate file types.

All files are set to their appropriate file types.
29
#29
4 Frags +

Okay so I found the problem.

Basically since you got a new hard drive you haven't unchecked the Windows Explorer setting to "Hide extensions for known file types". Currently yours is checked. You need this unchecked so you can see the actual file name for your cfg.

So if that doesn't make sense, here's a step by step visual of what I'm saying..

Turn off the "Hide extensions for known file types" setting:

Show Content
Show Content

Change the file name from this:

Show Content

To this:

Show Content
Okay so I found the problem.

Basically since you got a new hard drive you haven't unchecked the Windows Explorer setting to "Hide extensions for known file types". Currently yours is checked. You need this unchecked so you can see the actual file name for your cfg.

So if that doesn't make sense, here's a step by step visual of what I'm saying..

Turn off the "Hide extensions for known file types" setting:
[spoiler][img]http://i.imgur.com/7yesHLz.jpg[/img][/spoiler]
[spoiler][img]http://i.imgur.com/qar0GQU.jpg[/img][/spoiler]

Change the file name from this:
[spoiler][img]http://i.imgur.com/4cOCZim.jpg[/img][/spoiler]

To this:
[spoiler][img]http://i.imgur.com/O31osc4.jpg[/img][/spoiler]
30
#30
7 Frags +

Sorry for the almost 2 months thread necro, but if this can be of assistance to anyone, it'll be worth it.

TL;DR: make sure your .cfg file is in the default encoding (ANSI) when using "Save As..." on your notepad.

I was having a problem with my autoexec not loading by all means, and even displaying an "Unknown Command" text on the console when it was being read (but still not loaded). Upon starting TF2 without said autoexec.cfg it wouldn't give me that text anymore, so something was up. I searched a lot of threads trying to remedy my problem and nothing of this nature came up, so I guess this post can benefit someone.

I would've changed its encoding to Unicode when trying to put a bind that had a custom character and would only be stored if using another encoding. Didn't thought it would be a problem at that point, so I went along with it. Make sure you keep it default.

P.S.: Actually saving with UTF-8 will make it readable by TF2 while retaining the special characters.

Sorry for the almost 2 months thread necro, but if this can be of assistance to anyone, it'll be worth it.

[b]TL;DR[/b]: make sure your .cfg file is in the default encoding (ANSI) when using "Save As..." on your notepad.

I was having a problem with my autoexec not loading by all means, and even displaying an "Unknown Command" text on the console when it was being read (but still not loaded). Upon starting TF2 without said autoexec.cfg it wouldn't give me that text anymore, so something was up. I searched a lot of threads trying to remedy my problem and nothing of this nature came up, so I guess this post can benefit someone.

I would've changed its encoding to Unicode when trying to put a bind that had a custom character and would only be stored if using another encoding. Didn't thought it would be a problem at that point, so I went along with it. Make sure you keep it default.

P.S.: Actually saving with UTF-8 will make it readable by TF2 while retaining the special characters.
1 2
Please sign in through STEAM to post a comment.