in your enemy territory folder, search all subfolders for "autoexec.cfg", if you find one, delete it. make sure you do not have any files called autoexec.cfg anywhere in the et folder.

make a copy of the cfg that you use (the one that you keep having to execute when you enter the game) and save it as "autoexec.cfg" in the ETMAIN folder.

join a server (whatever mod) and be happy that you no longer have to execute that damned cfg file ever time! woot!!

PumpkiN wrote (View Post): › in your enemy territory folder, search all subfolders for "autoexec.cfg", if you find one, delete it. make sure you do not have any files called autoexec.cfg anywhere in the et folder. make a copy of the cfg that you use (the one that you keep having to execute when you enter the game) and save it as "autoexc.cfg" in the ETMAIN folder. join a server (whatever mod) and be happy that you no longer have to execute that damned cfg file ever time! woot!!

There is also a slight possibility that there are other autoexec files that are named like "autoexec_???.cfg" that may need to be deleted as well. And PumpkiN has a typo in his post. Name the file "autoexec.cfg" (not autoexc.cfg). Edit: Looks like PumpkiN already fixed it!

I tried doing this, I only have 1 autoexec.cfg in my etmain folder and deleted my other ones in each mod folder, and pump told me to put in customaspect 1 customheight and customwidth so I did.

Started up ET, it was still default. So I manually exec autoexec.cfg and it worked! Restarted the game, still back at default.

So somehow autoexec.cfg isn't autoexec'ing.

Gotta go to work, ill be on around 8pm PST tonight.

might also want to re-iterate the whole point of this.. we both had similar symptoms: start up et and it would load default resolution. we would then need to execute the config to get the resolution to fix itself.

i was able to solve my issue with what i posted, he has not had as much luck.

a thing to note, we both tried checked to see if autoexec was loaded when game loads by changing sens in the file, loading game and checking sens in game. turns out the autoexec file is not loaded during game startup..

brings up the question of when is autoexec actually loaded?

and also why did this solve my issue and not his when the symtoms were identical?

is there a windows equivalent to chmox a+r?

attrib +r

know what chmod is, not sure what chmox is though?

!wtf @ beck and miller?

I noticed when I start up the game, open up console when I get into the game, I scroll up, it says r_mode "4" 800x640 or something..... where in the fuck is ET getting this r_mode from? Or is that just the default. I'm at a loss as to what to do.

they are talking about a linux command "chmod" (at least beck is) that just changes permissions of a file. it might be the case that the file does not have executable permissions.. (maybe read? i dont know that notation of a+r.. i just know the octal form..)


the r_mode is what i was forgetting that one day when we were talking on xfire. in addition to the three, you should set r_mode to -1 (that means custom)


also here is a cool reference i just found

http://www.antman.info/wolf/cvar/

I had it originally set to r_mode -1 but would crash due to openGL wouldnt go to 1980x whatever out of silent mod. and I would have to do it twice, i guess it would set to default on the second try and start up on default resolution. It would work on the seond 'Join Game' from xfire.

I guess what im gonna have to do is, delete my autoexec.cfg and my etconfig.cfg and start from scratch to see if it fixes it like pumpkin, maybe pumpkin send me your autoexec.cfg and ill use that to see if it works.

i never deleted any of my etconfig files.. i know from experience though, that etconfig files get overwritten every time you exit the game so any modifications made in there are lost.

here is what is kind of confusing me about your situation. when we first started talking about this, you said that you had no resolution stuff in your config, so i told you to add those three lines etc..

but at the same time you said that if you executed your config, it would fix the resolution issue..

im just trying to figure out how in the world that would be possible..

Fixed:

Why it wasn't working, I had r_mode "-1" and r_customheight and r_customwidth but not r_customaspect. So I deleted r_mode and left it out, then pump told me to add the customaspect and I didnt redo the r_mode. So I just put r_mode -1 in my config and it works now.

glad to hear you got it figured out!