Does anyone know what this setting does? When I start up ET (Win XP Pro w/sp2), I get all these ‘Check com_crashed’ messages after the names of the pk3 files in etmain. If I open the console and type ‘/com_crashed 1’ and close et/restart…those messages are gone.
I have no idea what that setting is for/does though…anyone out there have an idea? SD maybe? 
Is this happening with 2.56 or 2.60?
I believe this problem has been addressed in 2.60, but have not tested it.
With 2.56, I start the game with a .bat as described below (which was a sticky on the old shrub forums)
Background
Every time you restart ET it defaults back to 800x600 no matter what you have in your autoexec.cfg
It’s not a shrub bug, read Lekdevil.NL’s explanation of the problem;
It’s not a Shrub bug, but a flaw in the way the ET deals with mods and with crash detection.
Last things first. Whenever you start ET, it creates a file called “profile.pid” in the homedir\etmain\profiles\profilename (e.g. “D:\Games\ETfull.2.55a\etmain\profiles\Lekdevil.NL”). If you exit ET, this file gets deleted again.
If you start ET, and it detects that “profile.pid” is already present, the program assumes that it has crashed on the previous run and resets all cvars that are marked as “unsafe” in etconfig.cfg to their default values.
Sounds pretty straightforward so far, doesn’t it?
Things get ugly when you connect to a server running a mod (any mod, not just shrub). As in all games based on the Q3A code, the client creates a separate directory for each mod name used on the server it connects to, as in homedir\modname (e.g. “D:\Games\ETfull.2.55a\shrubet”). In this directory, a new “profiles\profilename” subdirectory gets created, in which a new etconfig.cfg file gets stored. A new “profile.pid” file also gets created in there.
Now here’s the problem. Whenever you exit ET after playing on a server running a mod, only the profile.pid file in the mod directory gets deleted, and not the one in the “etmain…” directory. Hence, when you start ET again, it thinks is crashed previously and resets the cvars.
Solution: write a batch script that deletes the profile.pid file and then runs the ET program. Use that script to start ET.
The Solution
del etmain\profiles\TLMael\profile.pid
del shrubet\profiles\TLMael\profile.pid
et.exe %*
Point the shortcut on your desktop to etstart.bat instead of et.exe.
If you are using ASE edit the configuration of your browser so that it runs that batch file when an ET game is started. In ASE it can be found under View->Options->Games->Wolfenstein: Enemy Territory->Program Location.
com_crashed is set everytime your client crashes. You just have to type /com_crashed 0 in the console for it to go away
BTW if you use ASE it’s better to make a new config with your default settings and put that in the config space in the game configuration window…
^ or just put those settings in an “autoexec.cfg” file kept inside etmain.
I know resolution (cvar: r_mode x - click for r_mode numbers = which resolution) is reset on check_com crashed, er not sure on others since i keep all my cusomised settings in my autoexec.cfg
prior to 2.60, it is also set every time you play on a server with fs_game set to something other than etmain. From my testing, its pretty well fixed in 2.6, but If you never want 2.6 to reset your settings, you can add +set com_ignorecrash 1 in your command line (this must be in the command line, as the com_crashed stuff happens before your .cfg files are loaded).
