Friday, June 27, 2014

Bioshock Infinite [DX11] Helix

Bioshock Infinite [DX11]
By Helix

I am posting this for Helix because I had a few people ask about it and it's definitely worth checking out for those who missed it. This was posted around a year ago on Nvidia forums.

Fixed:
-Fixed some parts of the hud.
-Fixed random crashes.
-Fixed bug with different game resolutions.

Known issues:
-SSAO should be on NORMAL or below.
-Distant lights cutoff.
-[SLI ONLY] Reflections are broken during Chapel intro scenes.

Required Instructions:
-As soon as 3D enables press Ctrl-Alt-F11 [To disable fake 3D mode]
-Set SSAO to Normal.

Unpack this FILE to where BioShockInfinite.exe located

57 comments:

  1. The game is 3d vision rdy now

    ReplyDelete
  2. Already grabbed this the first time, but thanks a lot anyway

    ReplyDelete
  3. fake 3d is not 3d vision ready pal, thanx fo the fix Helix, the only thing missing is the correct gun sight convergence

    ReplyDelete
  4. Thank you for this fix.
    Does Ctrl-Alt-F11 have to be pressed every time, or just once? Can it be saved to the game's profile with Ctrl-F7?

    ReplyDelete
    Replies
    1. As far as I know every time. Game default loads nvidia's "fake 3d" mode.

      Delete
    2. what's exact time-point for to press Ctrl-Alt-F11 ???

      Delete
  5. Awesome, was waiting for this :D
    I have a request if you don't mind, there is a game called Max the Curse of Brotherhood, I don't know if that can be Mod for 3D Vision, but I think it will look amazing in 3D Vision

    ReplyDelete
  6. thks for the 3D pleasure.

    ReplyDelete
  7. The distant light cut-off problem can be fixed by decreasing the depth to a little bit under 50%. I'm getting a weird graphical glitch when using the shock jockey vigor in the game though.

    ReplyDelete
  8. How do I know If I disabled fake 3D mode or not?

    ReplyDelete
    Replies
    1. Ctrl-Alt-F11
      You can cycle and you should see a difference.

      Delete
    2. I don't see a difference...I think I did something wrong.

      Delete
  9. How to change ssao setting?

    ReplyDelete
    Replies
    1. options. On start menu. Its like
      Continue Save
      New Game
      Options.

      Delete
    2. It might be labeled Ambient Occlusion

      Delete
  10. Great work! But is it possible to get the HUD back to screen depth? Thanks.

    ReplyDelete
    Replies
    1. I took a quick look at the fix, and there is no easy way to move the HUD. Would require someone digging into the fix to add that, maybe via a hotkey. Doable, but someone needs to spend the time. Learn how you can make this change and share: http://wiki.bo3b.net

      Delete
    2. To change HUD depth ou have to edit the following files: 718B6728.txt, 71054161.txt and F3834447.txt in the \ShaderOverride\VertexShaders\ folder. Search for "mul r1.x, r1.x, l(0.2)" without "" and change the number @ the end. Higher values means HUD into depth, lowering means move HUD to screen depth. "mul r1.x, r1.x, l(0.0)" is screen depth. Id like the HUD into depth so i changed it to 0.6 but the value is up to ur choice.

      Delete
    3. This comment has been removed by the author.

      Delete
  11. why i cannot use a D3d9 injector with a d3d11.dll fix in any game , like Bioshock I. , or AC Rogue ?
    With BI, it crashx and with AC Rogue , the injector is not working .

    ReplyDelete
  12. why i cannot use a D3d9 injector with a d3d11.dll fix in any game , like Bioshock I. , or AC Rogue ?
    With BI, it crashs and with AC Rogue , the injector is not working .

    ReplyDelete
    Replies
    1. As noted on Rogue comments, I just tested Bioshock Infinite yesterday, and the game the fix are working fine over here with Steam version, and 350.12.

      Delete
    2. Can you maybe tell us which your SweetFX version and what the specific preset is? For me neither the 350 nor the new 353 play nice with my otherwise regular steam version of BI. For me either the 3D works or the SweetFX preset work, but not both at the same time.

      Delete
  13. Can I combine this fix with SweetFX settings by any chance? :3

    ReplyDelete
    Replies
    1. Yes.
      Sweetfx uses different files as far as dx11 games.

      Delete
    2. There is a conflict for some reason. The 3D fix on its own works flawlessly, but once I copy the SweetFX files into the Win32 folder as well, the game simply does not want to start up and a crash file is generated. It's stange since no files were overwritten when I copied both into the .exe folder. If I remove all SweetFX files it works as well as vice versa. Now strangely, when I remove all the helixfix files and only put the Sweetfx files in there and start the game with regular 3D Vision enabled, then toggling the SweetFX via hotkey also toggles the 3D on and off.

      Delete
    3. I disabled the steam overlay too, but alas no cigar

      Delete
    4. Strangely enough someone else seems to have the same problem above: "why i cannot use a D3d9 injector with a d3d11.dll fix in any game , like Bioshock I. , or AC Rogue ? With BI, it crashx and with AC Rogue , the injector is not working ."

      Could it have something to do with new nvidia drivers, or did you change something with the fix? I'm actually pretty damn sure I played BI with an older version of your 3Dfix (when it was still on some nvidia forum) combined with Sweetfx maybe two years ago.

      Delete
    5. Sweetfx CAN support DX11
      It uses a DXGI file.

      https://sfx.thelazy.net/games/game/130/
      ----------------
      People including myself used sweetfx + 3d fix bioshock infinite.+

      Delete
    6. Any idea at all, what the conflict might possibly be caused by, or things I could try out possibly to fix it? As I said, even without any of the Helix 3D fix files, and just the default Nvidia 3D enabled - the game jumps back and forth between 2D and 3D mode when I press the SweetFX hotkey to toggle the effects :\ This is NOT normal behavior in other games, where I can use both 3D and SweetFX together.

      So its always either 3D without SweetFX or 2D with the SweetFX. Once I put the Helix 3D fix files into the folder as wenn it doesn't start at all, but this strange behavior leads me to believe that the problem is not connected to the 3D fix itself. I actually did get a preset from https://sfx.thelazy.net/games/game/130/ and also tried SweetFX 1.3, 1.4 and 1.5 but all have the same "switch back to 2D" issue when I enable the effect.

      Delete
    7. That effect there is most likely to be because of latest drivers. If you can roll back to something more compatible I'd expect that to fix the 2D issue.

      Delete
    8. Kinda sucks to roll back, considering I also play Witcher 3 and GTA V... oh well I suppose then I have to do a BI marathon :)

      - Any idea from experience which driver version definitely works?

      - Is there perhaps a way to have multiple drivers installed at the same time that you can switch between - it would kind of suck to reinstall drivers back and forth...

      Delete
  14. Im not able to play this game with 3dtv play at 720p 60hz on my w1070 because the game forces it to use 720p 120hz .
    I've tried NVidia Inspector to force 60hz withou success.The desktop is already in 720p 60hz .
    Anybody has a solution to force the game in 60hz ?

    ReplyDelete
    Replies
    1. i've just saw the solution on this thread : https://forums.geforce.com/default/topic/573000/3d-vision/benq-w-1080st-3dtv-play-help/2/

      Delete
  15. Hi eqzitara thanks a ton for another amazing fix everything renders perfectly and looks great. I'm running into a strange issue though, it seems I'm getting a different contrast in each eye. the left eye is darker in color spectrum than than the right. Any idea, this may be monitor specific (ROG Swift - everything seems to be monitor specific with this one). I'll test it out on my old asus I gave to my mom when I get a chance but any thoughts in the mean time?

    ReplyDelete
  16. Might be helpful, if Ctrl-Alt-F11 does not work for you it's because you don't have advanced features enabled in the control panel. It is located under keyboard shortcuts in the stereoscopic 3d section.

    ReplyDelete
  17. great fix, seems to work well! From what I can tell, reflections in the chapel scene looked fine and I've got an SLI setup. Must be something related to newer drivers?... But, is there any way to alter the conversion when aiming down sights? This game would be virtually perfect if that could be applied somehow. Even better if it was done using the smooth transition as was done in Far Cry 4...

    ReplyDelete
    Replies
    1. Yes, the SLI bug was fixed in recent drivers, not sure which.

      You can play with the settings file and change the conversion. No way to add smooth transitions, this is HelixMod.

      Delete
    2. Thanks for the reply bo3b. The smooth transitions aren't really a big deal anyway... I looked in the dx11settings.ini file but there were no existing settings for mouse/button presets for me to toy with. I tried to dissect the .ini files of other DX11 HelixMod fixes and followed some of the tutorials on the site but couldn't get anything to work. Not sure if it's just not possible with this game or if it's just because I don't know enough about what I'm doing... probably the latter. Is there any advice you can give me to point me in the right direction? Thank you!

      Delete
    3. No its just not possible. This wrapper was built exclusively for bioshock infinite.

      Basically you choose two weapons and stick with them for all of Bioshock Infinite [cause upgrading].
      Just choose two weapons where convergence doesnt effect as much since your probably playing at a high setting

      Delete
    4. ah ok. Thank you for the info. Who knows how much time I would have put into it before figuring out it wasn't possible in the first place? :P

      Delete
  18. how can i start hunting shader in this fix? it's dx11 and helixmod debug d3d9.dll won't work,
    i seek to disable gun model in this game,where is d3d11.dll debug?
    play fpsgame with high setting( separation=10 convergence=10 )that was all I ever needed

    ReplyDelete
    Replies
    1. This is the only version of the DX11 HelixMod that Helix shipped. I don't think we ever got a debug version.

      You can probably use 3Dmigoto to hunt these shaders. But that will involve making the fix work in 3Dmigoto as well. You'll need to try to find the shaders that are overridden using 3Dmigoto Hash numbers as there is no direct conversion between the two. (different hash functions).

      Delete
    2. i try to use 3Dmigoto hunt these shaders,rotate through almost 70 pixelshaders and vertexshaders ,none of them are related to gunmodel,
      the same problem occurs in BF4 (3Dmigoto fix),Is this special game status ?
      i could find PS VS related to gunmodel in BF3 BFH FARCRY4........
      buy the way,tridef 3d almost turn all dx9 fps game with screendepth 2d gun and high convergence scene fused together,I think they did it on purpose.,but their technical support is dead..........

      Delete
    3. I took a look with 3Dmigoto, and it looks like it's working OK on this game. It should be possible to do what you want, but it's going to be hard.

      There are multiple VS and PS for each component, and you need to kill them all. In this case I identified 3 separate VS that affect the gun. Go to HERE to see the shaders and an example with the gun made invisible.

      I don't know if these shaders affect other items, might be better to do the same with PS. You'd also need to replicate the helix fix in the shaders with 3Dmigoto. Not impossible, there aren't that many, and you have the ASM as a guide.

      In any case, this works, you just need to disable multiple shaders.

      Delete
    4. As far as I know Unreal Engine doesnt distinguish shaders for guns between all other models/textures in game.
      It would be next to impossible. Like shader will control gun and a 1000+ walls, etc and each gun will be on 3/4 shaders.

      Delete
  19. The fix is not working with GTX1080 cards.

    ReplyDelete
    Replies
    1. Win10x64, v.368.95 drivers, Dual SLI.

      Delete
    2. Very unlikely to have anything to do with 1080 cards. SLI was also working with more recent drivers (fixing the SLI only problem of water for example.)

      "not working" doesn't provide enough information to make suggestions.

      Delete
    3. Dll running shows me a message, that needs a card supporting DX11 or 10, or this versions of DX are not installed (but they are).

      Delete
    4. Just tested it again, working well here with Steam version on Win 7, GTX 970, driver 368.81.

      The DX not installed problem is weird, we sometimes see that with 3Dmigoto fixes, but this is a HelixModx64 fix (the only x64 one actually).

      Might be a Win10 Anniversary update problem, we've seen other glitches related to that.

      Only thing I can suggest to try is to reinstall your driver, using DDU. On rare occasions it will get bad installs.

      Delete
    5. Where is the author`s info, that this fix is x64 only?
      I have only x32 game exe version installed (and i`m gonna check why it has no x64).
      Ok, i think you are targeted, where the problem is. Thank you. After solving it, i will write about results.
      Please, let`s add the information about fix is x64 only to the post (this message is for eqzitara).

      Delete
    6. Ah, sorry, I got that confused. HelixMod has multiple x64 fixes. This fix is for a x32 bit game though, as I think Bioshock Infinite only ever ran as x32.

      The part that is unique here is that this is the only DX11 fix for HelixMod. All others are DX9. So... unlikely to be what is going wrong in your case.

      Try running the game with the fix removed, but enable 3D. It will look terrible, but that will tell you whether it's a driver/OS problem versus a problem with HelixMod.

      Delete
  20. Anyone notice weird shimmering around your weapon in 3D? Tried adjusting convergence and depth settings, but the issue persists. Suggestions?

    ReplyDelete
    Replies
    1. Did you
      ~Disable compatibility mode with Ctrl+Alt+F11 (check the green text to confirm that it is disabled - you should only need to do this once).

      Delete