Please provide a link to where it says it was deliberately chosen.

I think it was an unintended mistake to be corrected in a future patch.

Well, I did say "if".

And I'll let the developers speak for themselves. It's certainly not my place to publicly quote anyone that I've talked to about it.

I'm fairly positive that 2k, or whomever, will fix this issue before too long... but not \too quickly because as that 2k moderator stated, most of the dev staff are on vacation.

I\'ll still be picking up my pre-order up tomorrw and see how long i can hold for a patch (or an awesome fix from this community) before i break down adn play it, becaseu after polaying the demo adn seeing the videos it loks pretty damned good.. but on my 4:3 TV.. may as well since uiàèll see mroe of the game than using my ws monitor.
arg.

Heres an FOV hack for the demo:

http://dl.tocaedit.com/bioshockdFOV.zip


Reportedly not working on Vista 64bit...


I'll make one for the retail game when I get a hold of it.

Racer_S to the rescue!

Also to the PC ZONE guy : Some of us are above the 1337 gamer idiots found on Kotaku.

To the other guys who simply keep on arguing that what Bioshock does is what it is meant to do : Read up on all the FAQs. Understand what widescreen is and why it is better and why games need to do Hor+ to actually make use of it instead of coming to this thread and bashing the WSGers for complaining.

so i just seen an exe in there is this a replacement for the demo exe then?

Thanks for the fix! Is there any way you could make it compatible with Vista 64bit once you get hold of the retail version?

still no sure how to use the hack readme would nice ;p

Just wondering but... i'm guessing the way these FOV hacks you make work in a similar way to trainers? How do you come across the memory offsets to it in that case? You can't change it in the first place, so it's not like you can narrow it down with a memory scanner...

Here is what Racer_S's hack does ...



More to come later ...

Admin Edit: Adding link to download - http://dl.tocaedit.com/bioshockdFOV.zip and please Digg

In Vista it's quite hard to access other program's memory. Hmm.

vista works the same as xp in terms of memory access, i believe the reason it doesnt work on 64bit is due to different offsets.




the way i found the values was simply an educated guess.. but there is a pattern with all games, which I've learned from experience.

it took longer than usual but I've pinned it down.


also, i threw in a readme. sorry for the confusion.

for example ...

I'm not on Vista yet as I had no time to upgrade (going to by the end of next month), but wasn't it planed for Vista to restrict memory access a lot and use a sandbox model for running applications?


Btw, were you looking for a FOV variable manually? - I've been trying to for a minute, but it's quite full of 75.0000.. stuff

Do you have experience with Unreal 3 engine already so you know where approx they keep FOV?

That triple head of yours... what 3 monitors you use and in which way do you connect those?
Also, how much does it bother to have a monitor edge obstructing the view.