Widescreen Gaming Forum

EDIT: UTinput.ini Solution is in the third post:

Inspired by this thread until someone find a DECENT fix.

http://www.widescreengamingforum.com/forum/viewtopic.php?

I find FOV 90 on my widescreen monitor cramped, awkward and totally discomfortable on my eyes, and hence my concentration. I need a solution. There is the console command "FOV 100", but each time you spwan, the game resets FOV to 90. So, in an attempt to make a simple temporary solution I tried an ini tweak to improve the game, which should have had this implemented from DAY 1!

Results:

Well this has nearly got me beet. I could bind a NEW button to FOV 100, for example

Backspace:

[Engine.PlayerInput]
Bindings=(Name="Backspace",Command="FOV 100",Control=False,Shift=False,Alt=False)

This worked really well. However this is not optimal, as you remember to press the buttone ach time you spawn, which is not effecient and will see you get fragged cause you searching for buttons. So I tried to make "w" the button to command the FOV change, which means I have to put two commands on the "w" button, ie "MoreForward" and "FOV 100". This has proved impossible for me.

There are three sections in the UTinput.ini that have key binds.

[Engine.PlayerInput]
[Engine.DebugCameraInput]
[UTGame.UTPlayerInput]

I tried this in all three section :

Creating a Command Bind first:

Bindings=(Name="GBA_FOVLarge",Command="Fov 100",Control=False,Shift=False,Alt=False)

then under each of these:
[Engine.PlayerInput]
[Engine.DebugCameraInput]
[UTGame.UTPlayerInput]

Bindings=(Name="W",Command="GBA_Moveforward | GBA_FOVLarge",Control=False,Shift=False,Alt=False)

As well as:

Bindings=(Name="W",Command="GBA_Moveforward | FOV 100",Control=False,Shift=False,Alt=False)

and:

Bindings=(Name="W",Command="GBA_Moveforward + GBA_FOVLarge",Control=False,Shift=False,Alt=False)

and:

Bindings=(Name="W",Command="GBA_Moveforward" "GBA_FOVLarge",Control=False,Shift=False,Alt=False)

However none of these worked no matter where I put it in the Input file. "W" always kept working, so I ran an experiment. What if I UNBIND MoveForward from "W" key and make it like the Backspace FOV 100 bind?

So in under of the sections

[Engine.PlayerInput]
[Engine.DebugCameraInput]
[UTGame.UTPlayerInput]

Bindings=(Name="W",Command="FOV 100",Control=False,Shift=False,Alt=False)

Still, "w" only moved forward, no FOV change. This leads me to think that the game has another Input file somewhere.

I know that when I edited the ini file, and didn't make it READ ONLY then UT3 changes the "W" command back to its original. So I started editing the ini and then saving it and making it a READ ONLY file. Still no affect.

Anyone got any ideas?

When I messed with it I think I had to scrap all the duplicates or they'd override the one I changed, even with read-only, the 'cross-platform' entries make a major mess.

Thank to LazyCrakBear:

http://gearsforums.epicgames.com/showthread.php?p=25100550#post25100550

THe solution is so simple, I can't believe I missed it, I think I tried everything excpet adjusting the original bind.

BAAAA.

Anyway, replace this command with this new one:

Bindings=(Name="GBA_MoveForward",Command="Axis aBaseY Speed=1.0 | fov 100",Control=False,Shift=False,Alt=False)

So, when ever you spawn and as soon as you move forward, you get a temporary FOV solution.

Waughlaaa! Enjoy.

But every time you move forward it sets the FOV. I can make a temporarily fix by just pressing the F1 button to set the FOV if you want.

Edit: What about a timer that sets the FOV value every 1ms? Use F1 to enable it and F2 to disable it.

hmm, what if your using a weapon that can zoom-in and you move forward? It sets the FOV to 100 and the sniper becomes a short range weapon :D

Thank to LazyCrakBear:

http://gearsforums.epicgames.com/showthread.php?p=25100550#post25100550

THe solution is so simple, I can't believe I missed it, I think I tried everything excpet adjusting the original bind.

BAAAA.

Anyway, replace this command with this new one:

Bindings=(Name="GBA_MoveForward",Command="Axis aBaseY Speed=1.0 | fov 100",Control=False,Shift=False,Alt=False)

So, when ever you spawn and as soon as you move forward, you get a temporary FOV solution.

Waughlaaa! Enjoy.

Been using this workaround since the UT3 demo, and it's the best solution out of the box (other than patches/hacks) that I know of.

Problem is if zoomed in on sniper and you move forward the scope view/gun dissapears and you have to remember to unzoom (right click). Other than that it's better than nothing but still pretty ridiculous that it's not done properly by Epic in the first place. But that's Unreal Engine 3 for ya. ;)

Sniper rifle eh? I forgot about that and havn't run into it.

When I was ingame and I consoled the sniper, it didn't give me any grief, but I better retest it.

"I'm going in!"

EDIT: DAGNAMMIT!!!! Yes, you lose the scope. AAAARRRRR!

Ok, there has to be a better solution. However, I think that FOV 100 and no scope, is 100% better than FOV 90 and the odd scope site.

Squizzy, I like your thinking! Set FOV 100 evey millisecond. Well, if that doesn't slow the game down, or the performance, or interupt other commands I think that is a good, very good workaround, better than the bind fix even. Now, I wonder if something like that can be overridden whilst in zoom mode?

Guys, we are getting close here!!! I can feel it. CAN YOU FEEL IT?

CAN YOU FEEEEEEEEEEEEEEL ET!?

/breathe
/breathe

I know you can feel it.

But most important will be the final version. I'm sure they will fix it when it will be released. Do we have to worry about it that much for a demo? :)

But most important will be the final version. I'm sure they will fix it when it will be released. Do we have to worry about it that much for a demo? :)

Thing is they havn't fixed it for the final. HOwever I think you can take it too 120FOV in the final

But most important will be the final version. I'm sure they will fix it when it will be released. Do we have to worry about it that much for a demo? :)

I wish I could be as optimistic as you are squ1zzy, but for some reason I think they couldnt care less about proper WS/FOV... :cry:

...reason beeing that the UT3 engine is VERT- from all the games we've seen...

From someone who has played the final.

- Can you set the fov higher than 100?
yes to 120 but it´s same like the BETA, after every kill you have to set it new.

http://www.oceaniaut.com/vbb/showthread.php?t=26556

Sniper rifle eh? I forgot about that and havn't run into it.

When I was ingame and I consoled the sniper, it didn't give me any grief, but I better retest it.

"I'm going in!"

EDIT: DAGNAMMIT!!!! Yes, you lose the scope. AAAARRRRR!

Ok, there has to be a better solution. However, I think that FOV 100 and no scope, is 100% better than FOV 90 and the odd scope site.

Squizzy, I like your thinking! Set FOV 100 evey millisecond. Well, if that doesn't slow the game down, or the performance, or interupt other commands I think that is a good, very good workaround, better than the bind fix even. Now, I wonder if something like that can be overridden whilst in zoom mode?

Guys, we are getting close here!!! I can feel it. CAN YOU FEEL IT?

CAN YOU FEEEEEEEEEEEEEEL ET!?

/breathe
/breathe

I know you can feel it.

no we're not... i posted this so called solution almost a month ago... fact is epic needs to actually listen to the community rather than locking threads and banning people for complaining.... gears of war on PC was a disaster so i dont expect retail UT3 to be much better

Baracus2K, you need a hug. :D

Given Epic should have done it, but lets look for a solution in absense of developer care factor.

Anyone know a way to discrimiate the sniper FOV from the rest of the game?

Hmm, how bout putting that fov100 fix on the main fire button, then clicking sniper/alternate fire wouldn't have it active, and you'd mainly have correct fov since you're rarely not shooting (or at least I am).

Hmm, how bout putting that fov100 fix on the main fire button, then clicking sniper/alternate fire wouldn't have it active, and you'd mainly have correct fov since you're rarely not shooting (or at least I am).

I like where you going with this. I will have to put some thought into it over the next day, I bet there is some sort of combination that will allow it to work.

Baracus2K, you need a hug. :D

yea i do :oops:

Hmm, how bout putting that fov100 fix on the main fire button, then clicking sniper/alternate fire wouldn't have it active, and you'd mainly have correct fov since you're rarely not shooting (or at least I am).

but then you shoot wouldnt the fov get borked again and you have to go back into scoped mode?

hmm, true. guess I was thinking the 2nd button fired it as well.

Best solution is still probably that 100's of peeps mass in front of epic's HQ and demand proper FOV/Wide support, it's not impossible, UT2k4 and all previous had it!

Good news guys!

UT3 first patch (beta - download at your own risk)

http://www.unrealnorth.com/news.php?action=view&id=1470

Fixes masses of things INCLUDING adding a FOV adjuster in the advanced options menu. Thank god, my faith in epic is restored though can't work out why it was missing to begin with (or why aspect ratios weren't automatically taken into account).

So no more lost scope hopefully ;) (and yes it was vastly preferably to playing at 90degrees)

HUZZAH!

Can anyone confirm if the patch is a solid FOV fix? Or does it reset still?

HUZZAH!

Can anyone confirm if the patch is a solid FOV fix? Or does it reset still?

WEll someone on that link I posted (last page of comments) said their 100FOV finally sticks so I'd take it as confirmation, it would be pretty stupid for them to put the adjuster in and not have it stick now I supppose. ;)

I just hope it goes higher than 100 (it was misinformation that it did 120 in the retail because I was told by more sources that it only did 100) but either way, i'm keen to see what max FOV it has available and if this is ok for triple screens (not that i'm one of them, i'll be happy with anything over 100 on my single 16:10)


edit > found this thread on Beyondunreal 'patch issues' and one person said he couldn't move the slider, however it's still worth testing to see if 'fov XXX' sticks from the console as that's good enough until the patch is final (remember it is beta).

http://forums.beyondunreal.com/showthread.php?t=191985

I'm sure there will be lots of smaller issues for different people but that's why the patch isn't meant to be available to the general public yet. :)