Also the game.cfg located here (C:\Users\Athena\Saved Games\Crysis2) regenerates every game, how do i fix that. The commands i apply work but restart every time.

Apply the r_drawnearfov=75 code to the target line of your shortcut and it should work 100% of the time.

I can only get some commands to work in game.cfg other commands i have to put in autoexe.cfg.

Weirdness?

Which is the offical place to put the commands, everyone is saying the game.cfg >.< Though when I set that to read only I couldn't log in.

Apply the r_drawnearfov=75 code to the target line of your shortcut and it should work 100% of the time.

which shortcut? I launch with the "crysis2launcher.exe" which launches the "crysis2.exe" but with the added benifit of auto updating. or does it matter?

Also i want to do this as a final option.

If I remember correctly from the demo, it is the Crysis2Launcher.exe which requires the target line.. However, I don't think it would hurt anything to put the target line in both shortcuts.

I used this target line method back in the demo to apply .cfg code before the developer console was functioning, and it worked very well.

If I remember correctly from the demo, it is the Crysis2Launcher.exe which requires the target line.. However, I don't think it would hurt anything to put the target line in both shortcuts.

I used this target line method back in the demo to apply .cfg code before the developer console was functioning, and it worked very well.

i dont think i am doing something right. i know i supposed to right click the .exe click properties, but were do i change the target line? i cant find were to edit? sorry if this sounds noobish. Aslo how would i implement it in? is it just like talon said?

sorry its been a while

There is a line of code in quotations that already directs the shortcut to the source .exe to open the program.

Outside of the quotation marks, leave one space and type in:

-r_DrawNearFov=75 with no quotations..

So the final result will look something like this:

"C:\ProgramFiles(x86)\EA\Crytek\Crysis 2\Crysis2Launcher.exe" -r_DrawNearFoV=75

Apply the edit, then you should be good to go!

okay thx do i need the "-" at the beginning of the command?

this is annoying me now. i cant edit any line in the properties, just the name of the .exe

nvm

PEBKAC on my part lol

how do i seperate the different commands, and my last question still remains, with needing the "-" at the beginning of the/each command.

There is a line of code in quotations that already directs the shortcut to the source .exe to open the program.

Outside of the quotation marks, leave one space and type in:

-r_DrawNearFov=75 with no quotations..

So the final result will look something like this:

"C:\ProgramFiles(x86)\EA\Crytek\Crysis 2\Crysis2Launcher.exe" -r_DrawNearFoV=75

Apply the edit, then you should be good to go!

Unfortunately I do not think this method works anymore. I tried doing what you said exactly and it didn't work. Have you tried it in the actual game yet and had any success?

nvm

PEBKAC on my part lol

how do i seperate the different commands, and my last question still remains, with needing the "-" at the beginning of the/each command.

Seperate the different commands with a space after each command.. So like:

"Blahblahblah.exe" -r_drawnearfov=75 -r_hdresnipbles=1 -c_koolaid=0

Yes, the dash is needed for every command you wish to use.

@ crynetsecurity: I cannot verify that this method functions with v1.9... The last time I tested it was v1.2 and it worked but a lot has changed since than with Crytek changing .cfg permissions and whatnot for security reasons.

nvm

PEBKAC on my part lol

how do i seperate the different commands, and my last question still remains, with needing the "-" at the beginning of the/each command.

Seperate the different commands with a space after each command.. So like:

"Blahblahblah.exe" -r_drawnearfov=75 -r_hdresnipbles=1 -c_koolaid=0

Yes, the dash is needed for every command you wish to use.


Thank you, i will give this a try and respon if it works.

no dice

Dammit!

It was worth a shot though.

well it all works (except "r_DrawNearFoV = 75") when i add it to the game.cfg. only problem is is it has to be reimplemented everytime. if i could get a way it would not reset and get a way for r_DrawNearFoV = 75 to work, i will be set.

well it all works (except "r_DrawNearFoV = 75") when i add it to the game.cfg. only problem is is it has to be reimplemented everytime. if i could get a way it would not reset and get a way for r_DrawNearFoV = 75 to work, i will be set.

I am going to search for a way to get r_drawnearfov to work, this will be my quest lol. There has GOT to be a way to get it to stick.

well it all works (except "r_DrawNearFoV = 75") when i add it to the game.cfg. only problem is is it has to be reimplemented everytime. if i could get a way it would not reset and get a way for r_DrawNearFoV = 75 to work, i will be set.

I am going to search for a way to get r_drawnearfov to work, this will be my quest lol. There has GOT to be a way to get it to stick.

lol thats what i have been doing for the last 3 hours lol. if you find it FOR THE LOVE OF GOD POST IT LOL. The world of Crysis 2 needs it!

Why would we need the command to increase the HUD camera FOV?
That is, to increase the FOV of the camera that 'sees' the weapons on your screen.
Thus increasing it would only show more of the weapon when you use the sights.

[/stuff]

Why would we need the command to increase the HUD camera FOV?
That is, to increase the FOV of the camera that 'sees' the weapons on your screen.
Thus increasing it would only show more of the weapon when you use the sights.

[/stuff]

I find it makes Alcatraz's arms and weapons look smaller and less clunky on screen, allowing me to see more of the world. The way they had it set up by default causes the arms and weapons to be way to close to the camera, which ends up feeling like it takes up 1/4 of my screen. It is most noticeable when holding a pistol, it honestly looks like Alcatraz is holding it an inch from his face.

Why would we need the command to increase the HUD camera FOV?
That is, to increase the FOV of the camera that 'sees' the weapons on your screen.
Thus increasing it would only show more of the weapon when you use the sights.

[/stuff]

Becasue the way it is now is unrealistic looking.

well it all works (except "r_DrawNearFoV = 75") when i add it to the game.cfg. only problem is is it has to be reimplemented everytime. if i could get a way it would not reset and get a way for r_DrawNearFoV = 75 to work, i will be set.
Remove the "Syspec = " line from game.cfg in your saved games folder, and set the file attributes of game.cfg to read-only.