Commands haven't been removed, just locked. You have to change them in the System.cfg for now.
Two that I use are:
r_motionblur = 0 ; gets rid of annoying motionblur
r_glow = 0; gets rid of ugly lens flare
Also some poster on page two listed the ones you need to change FOV

so...about 40 usable cvars. The individual sys_spec_xxxx can be modified, but none of their related commands like e_shadows or r_usePOM can be accessed. This game is extremely UNMODDABLE in its current state. The cvars should be locked smartly, not like this. This is the wrong way to do it.

The console in Crysis worked just fine. Some commands were locked in multiplayer. Granted, there were a few that they didn't catch, but it worked well overall. Again, Crytek changes for the worse what doesn't need to be changed.

So you can in fact turn off stuff like DOF and Blur?

Looks like r_glow doesn't work, which is rather disappointing, but the r_motionblur one does work, as do the FOV ones and the no intro one.

keep getting different stories. Some say motion blur does work while others say it doesn't. I'm wondering if it's a matter of either adding to the command line or the system.cfg that is the difference.

It definitely works when you put it in the System.cfg. That's one of the first things I did when I installed it, played through the first three levels and it works fine. It's possible that they made an error when putting it in the system.cfg, no clue though. Only thing that doesn't work is r_glow, which didn't work in the leak either unless you typed it in the actual console in-game. Only I can't type it in the console in-game, they locked it..... grumble grumble.

It definitely works when you put it in the System.cfg. That's one of the first things I did when I installed it, played through the first three levels and it works fine. It's possible that they made an error when putting it in the system.cfg, no clue though. Only thing that doesn't work is r_glow, which didn't work in the leak either unless you typed it in the actual console in-game. Only I can't type it in the console in-game, they locked it..... grumble grumble.

Day 1 patch was supposed to unlock the console?

I meant that they locked certain commands from being used in the console. I realized that some people might misinterpret that phrase right after I posted it, my bad.

I put the settings in an autoexec.cfg file (in the same directory as System.cfg) and they seem to work there too. Some settings still don't work.

<20:21:11> [CONSOLE] Executing console command 'exec autoexec.cfg'
<20:21:11> Executing console batch file (try game,config,root): "autoexec.cfg" found in ./ ...
<20:21:11> con_restricted = 0 [RESTRICTEDMODE]
<20:21:11> log_IncludeTime = 1 []
<20:21:11> log_Verbosity = 3 [DUMPTODISK]
<20:21:11> sys_spec_full = 4 [] RealState=Custom
<20:21:11> g_skipIntro = 1 []
<20:21:11> r_MotionBlur = 0 []
<20:21:11> [Warning] Unknown command: r_DepthOfField
<20:21:11> [Warning] Unknown command: r_Flares
<20:21:11> r_HDRBrightLevel = 0 [DUMPTODISK]
<20:21:11> [Warning] Unknown command: r_Glow

Setting log_Verbosity = 3 will show more details in the logs.

I never had any motion blur at all xD Even if I run the game on extreme.. Something must be terribly wrong

It definitely works when you put it in the System.cfg. That's one of the first things I did when I installed it, played through the first three levels and it works fine. It's possible that they made an error when putting it in the system.cfg, no clue though. Only thing that doesn't work is r_glow, which didn't work in the leak either unless you typed it in the actual console in-game. Only I can't type it in the console in-game, they locked it..... grumble grumble.

How do you access the system.cfg to change the settings? I've been using console commands and every time i die i have to retype them in which svcks

check your folder..

check your folder..

It's the strangest thing but I can't find anything labeled "system.cfg" anywhere..

check your folder..

It's the strangest thing but I can't find anything labeled "system.cfg" anywhere..

Have you ever started the game?
its in the first folder (crysis 2)


if not create one.

Yup. Check the folder, should be "C:\Program Files\Electronic Arts\Crytek\Crysis 2" by default. To actually open the file for editing use notepad or notepad++

I found it, but whenever I add in the settings and exit and save it tells me access denied

edit: Nevermind I fixed that, but after typing these settings into the system.cfg I saw no results..

cl_fov=80
pl_movement.power_sprint_targetFov=80
r_DrawNearFoV=70

They may be locked out.

Well I guess we just have to wait for them to finish this game in patches. Hopefully they won't abandon us like they did with the first Crysis and quit patch support early. They really need to give us back our commands. Feels like we're being punished for the "you know what" getting out. This is not how you support a great modding community. But whatever like I said I guess we'll just have to wait and see.

Wow, I'm glad I stuck with my gut feeling and didn't break down under the pressure of temptation of buying this game. I'll be waiting and watching to see if there is any sign of improvement, but I'd say at this point loyal PC fans have been had. Instead of getting a superior experience from the PC version because of all the customization possible, we get a clone of the xbox version which is actually worse than the xbox version because it has minimal customization and therefore is more suited to run on the xbox than on the PC.

Basically, its like Crytek put a 4 cylinder engine in a 2 ton pickup truck. The result is that it will haul worse than a Honda civic with that same 4 cylinder engine because the weight of the truck is too much. On top of that, that same little Honda will probably go faster with a load behind it than the truck will with nothing behind it.

I feel like a deer in headlights playing this, so much blur, glow and flares that I can't see sh*t.