View Single Post
Old 11-18-07, 02:54 AM   #107
L4D & DoW2 ftw!
Gaco's Avatar
Join Date: Jul 2004
Location: Denmark
Posts: 3,143
Default Re: Post your final config for retail crysis here!

Originally Posted by Nanosuitguy
Gaco, what's the differance between making a system.cfg and making a autoexec.cfg? is there no difference at all? Works the same way?
I could try and explain, but I'll let this guy do it

Originally Posted by

This file doesn't exist by default, so you need to create it by going to your \Program Files\Electronic Arts\Crytek\Crysis directory, right-clicking on an empty spot and selecting 'New>Text Document'. Then rename this .txt file to System.cfg (not System.cfg.txt). By default Crysis looks for the presence of this file each time it starts, and if the file exists and contains valid commands, they will be automatically executed when the game loads up. As such, this file is the perfect place to store most of the commands you wish to apply to Crysis at startup.

The format for entering a command in a config file is different to that of commands used in the console. If you want to disable motion blur for example, the console command is r_motionblur 0, but when entered in the config file, it needs to be r_motionblur=0, and every command needs to be on a separate line.

Note further that some people recommend creating an autoexec.cfg file in the same directory, instead of, or in addition to System.cfg. This is fine, since any commands in such a file will also be executed automatically when Crysis loads up. However it appears that any commands in an autoexec.cfg file are applied after the game has loaded, and not necessarily during startup, and this may impact on whether certain commands are successful or not, so on balance I recommend using System.cfg. The help text for several of the console commands also refers to System.cfg, so it's best to use this file (e.g. see the help text for r_Driver).

Importantly: Some system commands still cannot be altered by using System.cfg, autoexec.cfg or any other custom user .cfg files. It appears they can only be altered when entered in an original Crysis system file, such as one one of the difficulty .cfg files (e.g. diff_normal.cfg). These commands are denoted by (system) on the following pages, and you should see the Diff_ file section further below for more details.

Finally, you can always execute commands in any existing or custom .cfg file you place in the same directory as Game.cfg by using the exec command. E.g. create a Mytweaks.cfg file, fill it with various commands, and then within Crysis, at any time you can open the console, type exec Mytweaks.cfg and they will all be executed straight away - though clearly commands which need to be altered at startup won't work this way.
Case: Antec P182 case + 3x 120mm Scythe Slipstream SY1225SL12M @ ~900 RPM
Motherboard: Asus P5Q Deluxe
CPU: Intel Core2 Q6600@3.3ghz w. Noctua NH-U12P
RAM: 4Gb Crucial Tracer PC-8500
Graphics: XFX Radeon HD 5970 Black Edition
Harddiscs: 2xRaptorX 150gb 10.000 RPM in RAID0
Soundcard: X-Fi Xtreme Gamer
Sound: Sennheiser HD600 Headphones + headamp
Keyboard: Logitech DiNovo Edge
Mouse: Razor Orochi
Monitor: Samsung 2232BW (22" 1680*1050)
OS: Windows 7 Professional 64bit
Gaco is offline   Reply With Quote