Batman: Arkham Asylum demo TH support

Post by **GeneralAdmission** » 07 Aug 2009, 19:26

Demo has native support for triplehead resolutions. Main menu is Vert-, pre-rendered cutscenes all appear to be pillarboxed.

Slo-mo "finishing hits" use a zoomed-in camera that is also looks Vert-, but that doesn't detract from gameplay since those 1-2 seconds are not actually user-controlled.

thales100 also posted a 5040x1050 shot in the demo thread HERE.

Post by **Paddy the Wak** » 07 Aug 2009, 22:55

Hi guys ...
Here is a fix for the zoomed in camera for the finishing hits, interactions such as opening grates and the character dialogues ...

All it does is change the FOV to something better whenever you press the space bar ... which is the key for most interactions.
The space bar is also used for jumping and running but these changes don't seem to be a problem as the fov whenever you might want to jump or run will be at or about at these values anyway (i.e. not zoomed in).

Find the ... UserInput.ini
On XP it is here ... C:Documents and Settings*USERNAME*My DocumentsEidosBatman Arkham Asylum DemoBmGameConfig

Find this line ...
.Bindings=(Name="SpaceBar",Command="ContextSensitive | Run | CapeGlide | AcceptConversation | Evade | CancelBatarangCamera", Shift=false, Control=false, Alt=false, bIgnoreShift=false, bIgnoreCtrl=false, bIgnoreAlt=false):META:COM_RUN_GLIDE_USE,0,-1,-1,"bRunButton",false,false,CI_RunGlide,CI_Interact

For 5040x1050 change it to ...
.Bindings=(Name="SpaceBar",Command="ContextSensitive | Run | CapeGlide | AcceptConversation | Evade | fov 140 | CancelBatarangCamera", Shift=false, Control=false, Alt=false, bIgnoreShift=false, bIgnoreCtrl=false, bIgnoreAlt=false):META:COM_RUN_GLIDE_USE,0,-1,-1,"bRunButton",false,false,CI_RunGlide,CI_Interact

For 3840x1024 change it to ...
.Bindings=(Name="SpaceBar",Command="ContextSensitive | Run | CapeGlide | AcceptConversation | Evade | fov 130 | CancelBatarangCamera", Shift=false, Control=false, Alt=false, bIgnoreShift=false, bIgnoreCtrl=false, bIgnoreAlt=false):META:COM_RUN_GLIDE_USE,0,-1,-1,"bRunButton",false,false,CI_RunGlide,CI_Interact

These are settings I found to be good but you can change the FOV to whatever works for you.

(Sorry ... no time to do proper thumbnails with links) ...
Before ...

After ...

Before ...

After ...

Before ...

After ...

Before ...

After ...

and a finishing hit ...

Post by **skipclarke** » 08 Aug 2009, 00:01

Thanks for the info. Did the thumbnails.

Post by **GeneralAdmission** » 08 Aug 2009, 00:08

Great work, Paddy! And nice to see you drop in. :)

njracer · Post by **njracer** » 26 Aug 2009, 09:43

hey guys i just picked this up today for ps3, man this game if F'ING AMAZING!!!!very well done, they put a lot of blood sweat and tears in to this one. i'm definitely gonna pick it up for the pc to, ps3's graphics aren't all that. game play is phenomenal, story is phenomenal, voice acting is excellent, same people from the cartoon and they all nail it. fighting seems basic in the beginning but its very effective the way its executed. played the demo again for pc and with all the physics is awesome, although i'm gonna play using the michael keaton tim burton suit, i always loved the look of that one the best.

all around, i give this game a 10/10, i literally played it 10 hours straight, i'm a freaking zombie right now, need sleep :?

i recommend this game to everyone

Gitaroo · Post by **Gitaroo** » 17 Sep 2009, 07:56

how much should the fov be for 16:9? like 1360X768 or 1920X1080?

YouTube · Post by **ViciousXUSMC** » 05 Oct 2009, 06:52

Game is great, runs 5760x1200 right out of the box with almost no issues, Paddy's little fix above makes this game almost 100% surround ready.

Its a very good game, voice acting is so perfect. It captures that dark and strong feel of batman from the recent dark knight movies, graphics look great but dont take a lot of system power a la Crysis or GTA4.

A single 5870 card maxes out the game with no problems at full 5760x1200.

Seems like its a game you can make as little or as much out of it as you want.

Just b-line for your objectives and beat the game, or take the time to try and solve the hidden riddles and find the hidden items and stuff. I would definitely make this a must have game for PC owners.

ChainSOV · Post by **ChainSOV** » 05 Oct 2009, 10:46

for those of you playing with a xbox 360 pad or another gamepad of your choice, you need to change a different file bmInput.ini

just search for ContextSensitive and edit the lines like mentioned above

njracer · Post by **njracer** » 05 Oct 2009, 18:55

i didn't have to change anything to play with my xbox 360 controller. worked great right out of the box.

i will second, this game is a must have. one of the best games i've ever played.

ethr · Post by **ethr** » 11 Nov 2009, 21:17

I have a video up on youtube of my eyefinity set up running with physx doing a Batman AA benchmark run.

http://www.youtube.com/watch?v=nCFsQYQnygA

Cheers!

WaveZtream · Post by **WaveZtream** » 11 Nov 2009, 23:32

Oh do tell how you got it to work :)

ethr · Post by **ethr** » 12 Nov 2009, 00:07

Oh do tell how you got it to work :)

Driver hack info is here http://www.ngohq.com/graphic-cards/16223-nvidia-disables-physx-when-ati-card-is-present-28.html#post82812

I used the "lite" version

I had to boot to safe mode to patch driver.

Build a vga dummy plug video here http://www.youtube.com/watch?v=mtbfXg193do

I used shrink wrap. PhysX will not work unless there is a "monitor" hooked up to the card - hence the dummy plug. Or just hook up a spare monitor if you have the room etc.

Make sure you disable the nvidia card before you create your eyefinity grouping or things can get all messed up since eyefinity will break up all of the built in extended desktop stuff! Prolly not an issue if you have an actual monitor hooked up to the NVIDIA card. Then after the grouping is complete go back and enable the nvidia card.

Best of luck. I'll be posting some videos on all this on my youtube chan so please feel free to subscribe!

Trav

WaveZtream · Post by **WaveZtream** » 12 Nov 2009, 17:43

Thx for that mate will try it out as soon as the 5970 hits the market togheder with my 285 GTX :D

OneOfTwo · Post by **OneOfTwo** » 16 Nov 2009, 18:38

I'm having issues with the change of fov....after modifying that value the menus and cutscenes are still VERT- :(
I'm positive i changed exactly what this little guide explains, any hint?

OzHuski · Post by **OzHuski** » 23 Nov 2009, 14:56

Thx for that mate will try it out as soon as the 5970 hits the market togheder with my 285 GTX :D

Borrowed my mates old 9500GT this week and coupled it with my 4870X2 to see how it would work out with the PhysX hack in Win7.

Honestly, I expected the game to run better with PhysX off but it was the reverse.. Game was essentially unplayable at 5040x1050 with PhysX off, flicked the switch to Normal, and then to then High, and found the frame rate was actually going up. Ended up being pretty damn smooth and enjoyable with everything on max.

Hoping my mate will let me keep this card for a bit longer so I can buy the full version and play through :P If more games supported PhysX to this extent and DX11 Physics wasnt on the way id probably run out and grab myself a cheap GT250 right now.. Still might do it anyways :wink:

Post by **scavvenjahh** » 09 Dec 2009, 18:48

@OneOfTwo : the menus remain Vert-, but the cutscenes shouldn't. Which cutscenes are not Hor+ for you with the fix ?

All, did someone find a way to run the benchmark with a custom FOV ??

Post by **scavvenjahh** » 18 Dec 2009, 09:43

Couple FOV tricks I found...

1) Hor+ main menu
I haven't found a way to directly alter the FOV in the menus, but if you go check out some character's trophy, hit Space (or W !) to correct the FOV, then exit, the main menu'll be Hor+ until you quit it. 8)

2) Zoomed first-person view
You can't assign keys to zooming in/out in first-person view afaik. There's a couple secrets in the Botanical Gardens that I found to be abnormally hard to "shoot" because of this. If you keep getting a 'Subject too small' message but there's no way to get closer, try this edit :

.Bindings=(Name="Z",Command="ToggleCameraZoom | fov 60", Shift=false, Control=false, Alt=false, bIgnoreShift=false, bIgnoreCtrl=false, bIgnoreAlt=false):META:COM_ZOOM,0,-1,-1,"",false,true,CI_Zoom

Now you have Bat-binocs ! Hit Space and you'll still be in first-person view, only with the regular higher FOV. (When you go back to third-person view however, the FOV will always be unbearably narrow until you hit Space again.)

3) Custom FOV in the benchmark
To run the benchmark using a custom FOV simply apply Paddy's edit to a "neutral key" (i.e that will not interrupt the benchmark) like W.

.Bindings=(Name="W",Command="MoveForward | fov 142 |DebugMenuUpPressed | OnRelease DebugMenuUpReleased | Axis aRawLHJoyUp Speed=1.0", Shift=false, Control=false, Alt=false, bIgnoreShift=false, bIgnoreCtrl=false, bIgnoreAlt=false):META:COM_FORWARD,0,-1,-1,"",false,false,CI_Movement,CI_LeftStick,CI_LeftStickUp

Launch bench, hit W once during the loading screen and voilà !

4) Object culling
There seems to be a limit in the number of objects that can be displayed at once, which is hard to miss in multi-monitor modes: you get a wider FOV but not more objects on screen, so objects in front of you (center screen) appear out of nowhere as you get closer to them. The benchmark alone makes it all too obvious. I wonder if it'd be possible to edit this limit somehow :?

fluxetreflux · Post by **fluxetreflux** » 03 Mar 2010, 19:41

Thanks for this trick.

Did someone know what is the correct FOV for 5760x1080 ?

I'm using FOV 140. It's working. But maybe it will be better with another one...

Post by **scavvenjahh** » 09 Mar 2010, 16:09

I tend to use 142 for 48:10 in most games when I don't know the default FOV and/or AR, but it's kinda arbitrary. :oops:
The FOV values suggested by Paddy work great, so the default FOV must be 75 in 4:3, so you should use 144 in 48:9. (How do I know ? Here's how !)

Grimloon · Post by **Grimloon** » 12 Mar 2010, 21:47

I added a couple of extra keybinds to my config to switch FOV for bits where it was important:

.Bindings=(Name="B",Command="fov 90")
.Bindings=(Name="N",Command="fov 270")

Seems to work OK. I prefer 270 for the FOV at 48:10 as it's easier (for me at least) to manage mass melee. I know it's different nawadays but I still tend to assume that FOV=90° per monitor. So far it seems to work apart from the occasional fisheye effect in peripheral (please note the "so far" - I'm still new to this!)

Widescreen Gaming Forum