It feels just as horrible as Halo 2 when it was ported to PC, how do you change it?

I don't understand why do developers keep doing this, don't they play games like Half Life 2?

Create rageconfig file in rage base folder with this text in it "cvaradd g_fov 20". This makes fov 100 (default is measly 80) and the game gets 100 times better
I couldn't even play with fov 80 - my head was spinning and I couldn't see my beautiful weapons.

I've never ever had a problem with FOV in my games, whether that be Modern Warfare, Battlefield or now RAGE

rageconfig what? files have extensions...

http://donotargue.com/cfg-makers/rage/ the command line produced is g_fov "100" , not cvaradd g_fov 20

Also you should have put base under "" so one can know it is the name of the folder in rage base folder...

rageconfig.cfg
There's 2 ways to do it.
You can go into windows explorer, go to tools, select text, and then goto advanced and check the box "always show extension", ok it.
Then when you create a new .txt it will show the extension, then you can rename it to .cfg. In this case rageconfig.cfg.
done.

The other easier way is to copy a .cfg to your desktop, rename it to rageconfig.cfg, then clear it out and put the needed cvars in.
Place it back into the proper location.
done.

Edit:
Seems we posted at the same time.

I can't believe Rage turned out to be a bad console port, the textures at highest settings are horrible and no advanced settings within the game...
PC really is dying.

I don't know how your system is setup but this is what Rage looks like to me:
http://home.comcast.net/~mrrocket/etc/rage_shot.jpg

PC is not dieing, I don't know who told you that lol..

The only way I could get it to work was to type in the "in game console," :

cvaradd g_fov 25 = 105 view

or cvaradd g_fov 20 = 100 view

g_fov did not work, and adding to the .cfg did not work with up date driver atioglxx.dll

Hmm I just tried it with g_fov 110.
It works for me, however I have an Nvidia card so the console commands maybe different depending on video card.

nope works the same on my ATI

Ah well in that case, Sting must have just been typing it in wrong I guess.
Sting you should only need to type: g_fov
And then whatever field of view number after it.
For example: g_fov 105

It looks like that on my PC too, try to get a little closer to any surface...that's what I was talking about.

Oh, g_FOV 110-120 is best for me and when i played quake too.