List of current issues and solutions.

[JimmyJoeBlow]

Still in the process of compiling list for one playthrough. See post below.

I see plenty of bugs, crashes, and texture issues reported in these threads, but a lot of them are dated some time back and just being bumped for good reason I would think. However, I think it would be easier to get everything that is still not working in one thread. I am also aware that there are plenty of guides online to get things working to the best of their ability, but having everything in one spot instead of having to search all over is more convienient.

I randomly wanted to play and saw the remastered version in my library. I will also check out what's going on with it and will add things I come across as I go along. I do remember the original port having crashes and bugs here and there so I'm not really surprised.

On another note, the standard for games to just release for the quick money and try to patch later is awful because fixing some things may mess up others; that's coding. Shameless ports are dissapointing from any company.

Any others that see a problem feel free to report it on this page and if I can duplicate and/or have a screenshot I will add it. The game deserves better than it's current state.

[JimmyJoeBlow]

*IMPORTANT INFO REGARDING CRASHES* After a 3-4 hour session in the game without a single crash I may have been able to pinpoint the issue. Even when you disable vysnc in-game through the options, it is not completely turned off. Search for bioshock.ini and open the file using notepad. Towards the bottom (can just use ctrl+f) there is a line UseVSync=1. Replace the 1 with a 0 and this should completely disable VSync. If anybody does this and is still experiencing crashes then please report back on this thread where you were and what you were doing so I can go over the other changes I have made to the in-game files. I had made a handful before the session. Dating this for if/when new information is discovered that may bring change. 12/11

*BUGS*
- Mouse sensitivity shoots up when Atlas tells you to, "lower your weapon." looking at the first child (introducing big daddy). Sensitivity goes back to normal when weapons come back out.
- Turning off "Adaptive Training" in the options menu does not turn off all the help displays that regularly pop-up. (assuming it should)
- Weapons do not scale properly with FoV. Changing FoV does not alter the weapon size.

*VISUALS*
Will just be listing texture issues that I notice throughout the game and where.
- NPC Hair (mostly female), NPC melee weapons, underneath some staircases (Neptune's Bounty), darker NPC long coats seem to have a slight blue glow.

*CRASHES* (my playthrough)
- Hitting "M" to check for "What is this?" caused game to crash. (Medical Pavilion)
- After clicking "Zoom Out" on the map screen cursor became very large and then game crashed. (Medical Pavilion)
1- First Gene Bank, while looking at upgrades, made cursor very small and then made the cursor very large. Game crashed right after. (Neptune's Bounty).
- Alt+Tab back into the game and it crashed, easily could happen in many games. (Neptune's Bounty)

*TEMPORARY FIXES* (numbers correspond to issue)
1- If you have a controller then you can still access the Gene Bank. Plug it up and Enable Controller in the options menu under the controls section. You can now get in the Gene Bank with no fear of crashing. I use mouse+keyboard, so I just disable the controller after my initial use. However, if you are really concerned about crashes then sticking with the controller may be your best bet. (I believe only the first Gene Bank is bugged if anybody could confirm).

*THEORIES FOR DEV SOLUTIONS*
- It seems there is a chance for the mouse button to either grow large or small any time you are in a menu (not Esc menu), especially the *first Gene Bank, hovering over buttons and/or selecting them. After the cursor changes size the game immediately crashes everytime. An easy fix for those with controllers would be to just activate your controller before going to a Gene Bank. An easy solution for the devs to look into would be removing the option to change the cursor size. This is a minor option that has no affect on gameplay and therefore not necessary.

[CHAP]

Don't forget the weapons Fov taking up half the screen

[JimmyJoeBlow]

Originally posted by ♥♥♥♥♥ out 4 Harambe:

Don't forget the weapons Fov taking up half the screen

I do not think there is an issue here. All the weapons, so far, seem fine. Lookup some old gameplay videos of the original and you will see they are just as large. Just look where the gun tip ends and how far/close it is to the reticle to help you compare.

If you are having an issue that I am not then get me a screenshot so I can add it to my post.

[Tayzor Azul]

Originally posted by JimmyJoeBlow:

Originally posted by ♥♥♥♥♥ out 4 Harambe:

Don't forget the weapons Fov taking up half the screen

I do not think there is an issue here. All the weapons, so far, seem fine. Lookup some old gameplay videos of the original and you will see they are just as large. Just look where the gun tip ends and how far/close it is to the reticle to help you compare.

If you are having an issue that I am not then get me a screenshot so I can add it to my post.

The FOV for the weapons is broken thats why he mentioned it.

[la la laura]

The fix for the mouse speed glitch is that Bioshock/User.ini and their defaults have incorrect x and y acceleration values. Set them all to 2500. Bioshock and User.ini are found in the appdata folder, not the My Documents folder

Edit: This is because the INI file has mouse acceleration values for all kinds of situations, a seperate one for cutscenes and a seperate one for when your weapons are disabled, etc. and these appear to be incorrect even in the default files. I filed a support ticket about it.

[JimmyJoeBlow]

Thanks teddy's. The only thing I question is your values being 2500. I'm assuming that is what you left your default mouse speed at and why you are using that number. Once I hit a cutscene of that nature I will be able to confirm this and add it to the fixes.

Originally posted by Tayzor Azul:

The FOV for the weapons is broken thats why he mentioned it.

Ok, but in what way? When deciding if something isn't working properly it helps to have a brief explanation; just saying it's broken doesn't help me (or devs) with a fix. This is also something that can be fixed in the INI file, but before I post how to change it I would like to know exactly the problem. Are the weapons too big? Is the general FoV just too small? Also, the fix (as far as the number people would use) will be different depending on the size of your monitor if I'm not mistaken. So ultimately, if we can pinpoint the exact issue I will mention it in the fixes and then to take it a step farther I might even try finding good numbers for a handful of ratios.

[CHAP]

When you change the Fov the weapon model doesn't change meaning they can take up half the screen. before the patch it wasn't much of an issue, but now well....
Anyway heres a link to a you tube video where this guy explains most of the issues with this game.

https://www.youtube.com/watch?v=1PkM3N9yB7Y

I would love to see these issues get resolved as i haven't bothered to play the game since the PC release has been such a let down.

[JimmyJoeBlow]

Ok, I figured it was something of that nature. That really blows considering it is completely out of our hands.

[Mello]

My game keeps crashing in Neptune's Bounty after a quicksave for no reason at all...

[JimmyJoeBlow]

Are you doing anything in game by chance Mello? I believe the first Gene Bank just as you enter the area is bugged in itself and causes crashes. I actually just got done with about a 3 hour session and did not have a single crash and I believe it has to do with Vsync. Even if you have it disabled in the in-game options menu, it doesn't actually completely disable it. Must go into the bioshock.ini to disable. I had also changed a couple of ratio settings as well so if anybody goes and disables the vsync in the file and still has crashes, please let me know for more research.

I will be adding the information to my 2nd post on the thread and will remove or tweak what I mention

[Kekc]

I have a problem. Each time i launch the game it crashes when entering the rapture, and particularely after the scenematic, during the first autosave. Same thing happens when i save the progress manually, it crashes. I tried all the -nosound, -dx9, disable overlay and some other solutions, but nothing helps. I even tried to download pirate copies of the game to see wheter the problem is in the version, but once again, same story happens each time. I have a windows 10 notebook, gtx 960, 12 gb ram, long story short, the hardware is fine. I have the folder "BioShok" in My Documents, i gave the bioshock.exe all rights, it's not "read only", i ran it in ALL compatibility modes, i tried the thing with Stereo Mixer, i tried disabling Steam Overlay... nothing helps!!! Anyway it always crashes when I save the game. Is the anything else i can try???

[JimmyJoeBlow]

Sorry to hear that Kekc. Try taking a look at my second post and at the very top there is a fix that has currently allowed me to play crash free.

Windows 10 may also have issues with save files that I'm unaware of since I am running windows 7. If this is the case then I would recommend searching for the bioshock save files which should be in users\(your user name)\documents\bioshockhd. I would go ahead and delete any save files you see there. For whatever reason they may be corrupt and that way all the new saves are fresh. If you don't see the folder then make sure to allow hidden files to be seen.

Let me know if either of those help and if not I will be sure to add the issue to the list.

[Dragon_Tiki]

On my review i have list of bad and good changes

[Arkon Warlock]

theres also the point prometheus crash point in the iced in room where a suchong diary is in a trash bin. entering it causes a crash 100% of the time and i have looked it up and other have experienced this as well