Monday, December 21, 2015

Far Cry 4

A fix by DarkStarSword and mike_ar69

Special thanks to Bo3b for the decompiler fixes and DHR for discovering the Max Payne 3 profile!

Download the updated fix: 3Dfix-Far Cry 4-2016-03-09.zip

If you have issues with the new version, the original one is still available (refer to it's README.txt for installation instructions): 3Dfix-Far Cry 4-2015-06-05.zip

Update 2016-03-09

  • Fixed the crosshair not working on the Steam version of the game.
  • Fixed the simulated fur glitch in HLSL (Thanks to bo3b for the work on the decompiler)
  • Fixed interior shadow mask clipping with MSAA enabled.
  • Updated to 3DMigoto that supports SBS & TAB output modes. To enable, set the output mode to checkerboard in the nvidia control panel (don't worry - checkerboard won't be used), uncomment the 'run = CustomShader3DVision2SBS' line in the d3dx.ini, then press F9 in game to cycle modes.

Update 2016-02-23

Removed the assembly shaders due to a falling out in the community. This means the NVIDIA Hairworks simulated fur glitch at depth == 1.0 has returned, but that is a very minor issue. Soft shadows are now fixed with 3DMigoto's arbitrary resource copying support so they continue to work flawlessly. Be sure to uninstall the existing fix with the provided uninstall.bat prior to updating to this version.

Update 2015-12-21

This is a major update to showcase new 3DMigoto features. For the original fix, Bo3b and I had already spent a good deal of engineering effort adding a new input infrastructure to 3DMigoto to add the aiming down sights convergence preset that was necessary to make the game playable, but there were numerous other wishlist items that were not possible to fix at the time, but not important enough to delay releasing the fix.

I've since been working behind the scenes adding new features to 3DMigoto to give our community the ability to fix many more advanced issues in DX11 games, and since this is the main game I use to demo 3D Vision in public I decided that it would be a good choice to showcase many of these new features.
  -DarkStarSword

  • Automatically adjust the crosshair and weapon sight depth to rest on the target, and for the first time ever the depth buffer from the opposite eye is used to improve the accuracy of the auto crosshair (new features: texture & constant buffer copying, reverse stereo blit)

  • Automatically adjust various floating icons in the HUD based on the depth buffer (new features: same as auto crosshair, access vertex buffers as structured buffers, screen size injection, texture filtering, texture injection)

  • Automatically adjust the camera HUD depth, and leave vignette full screen (similar to above, but also used texture hash tracking and intra-frame texture detection)

  • Disable aiming convergence preset while descending ropes (new features: conditional overrides, shader & texture detection)

  • Fixed one frame sync issue on shadows when anti-aliasing was disabled or set to SMAA (This was a game bug and is present in 2D as well, but shows the flexibility of just what we can achieve using the arbitrary resource copying feature of 3DMigoto)

  • Fixed artefacts on rocky surfaces when using NVIDIA HBAO+ (more info and screenshots here. New feature: constant buffer copying)

  • Removed need for 2560x1440 users to edit the d3dx.ini (new feature: texture hashes independent of resolution)

  • Aligned repair tool flame with repair tool, and aligned sparks with vehicle being repaired (new features: intra-frame texture detection, arbitrary resource copying)

  • Fixed reflected glow of sun & moon (new feature: render target size filtering)

  • Fixed NVIDIA Hairworks simulated fur glitch at depth == 1.0 (new features: ability to fix geometry shaders & use Flugan's assembler)

  • Fixed box shaped artefact on NVIDIA soft shadows (new feature: Flugan's assembler arbitrary resource copying)

  • Fixed interior shadow mask clipping on windows & doors (No new feature strictly required to fix it, but the new frame analysis features were crucial to identify the cause of this issue)

  • Stretched vignette on world map to full 3D screen (new features: texture filtering & texture hash tracking. Note: on my screen I get a slight moire effect in the crosstalk that can make it look 2D on the white background beyond the edge of the map, but it looks fine on a non-white background)

  • Fixed minor inverted emboss on patchy snow (Manually fixed. Bo3b has since improved 3DMigoto's handling of booleans in HLSL for these type of issues)

  • Fixed environmental reflections when texture quality >= high

  • Fixed reflections of several more objects

  • Improved accuracy of specular highlight fix

  • Re-enabled ripples and foam in river in prologue

  • Fixed several shaders used in some community maps (just some of the more common ones I saw in a few maps - I'm not going to fix every map)

Fixed in original release

  • Shadows
  • Halos
  • Water reflections
  • Environment reflections
  • Specular highlights
  • Interior building masks
  • Clipping on lights
  • Low convergence preset activated when aiming via right mouse or left trigger (you can edit the d3dx.ini file to adjust the convergence amount or key binding under [Key1] and [Key2]).
  • UI/HUD depth adjusted to fixed depth.
  • Weapon sight depth adjusted to fixed depth.
  • "Dirty lens" bloom depth adjusted
  • nVidia god rays ("ENHANCED" option in settings)
  • Regular god rays (while looking at sun through trees)
  • Underwater green fog volume
  • Underwater caustics
  • Halos around lights
  • Decals
  • Sun/moon glow
  • Fog

Installation

  1. Use driver 358.87 (Newer drivers may work as well, but this the recommended driver for this game as it is known to work well for a lot of people, including Windows 10 users. It is no longer necessary to change the game profile with these newer drivers).

  2. Unpack zip to Far Cry 4\bin directory

  3. If game switches to windowed mode after launch, press alt+enter to switch back to full screen

  4. Set ambient occlusion to HBAO+ or SSAO. HBAO+ looks significantly better than SSAO and is highly recommended, especially now I've fixed the artefacts it had on rocky surfaces. SSAO may not work on earlier versions of the game.

  5. Disable motion blur, as it causes rendering artefacts.

  6. If you are using SLI, set terrain to medium or lower to get good performance.

HUD Depth

Most of the HUD is now automatically adjusted, but there are a few tweaks available in the d3dx.ini in the [Constants] section:

  • x sets the depth of any HUD element that is not automatically adjusted

  • y sets a minimum depth for any automatically adjusted HUD element

  • z sets the depth of the minimap. Use -1 to automatically adjust it, but I found that could be distracting given the gun can wave around in front of it while running.

Known Issues

  • Shangri-La missions are reportedly broken with SLI for some users (need to confirm, but it seems these may now be working with the latest drivers). The only known workarounds are to turn off either 3D or SLI for these missions.

  • An outline of the current weapon may show offset to the right in certain rivers (most notably in the prologue) while using MSAA or TXAA. This is a game bug that occurs even in 2D without the fix installed. Most water does not suffer from this problem.

  • The text showing the distance to a waypoint is not lined up with the floating waypoint icon. This would be tricky to fix as the text is drawn earlier in the frame than the icon and there's no easy way to distinguish it from any other text that we don't want to adjust.

Notes

If you find any rendering issues be sure to mention where the broken effect was in the game, and what settings you are using - particularly anti-aliasing, shadows, water and vegetation.

145 comments:

  1. Thanks a lot! Finally can play it!!

    ReplyDelete
  2. Thank you very much! The wait was worth it!

    ReplyDelete
  3. Thank you so much! Played with beta fix and equals to 3d vision ready game. Actually better because of aiming convergence tweak!

    ReplyDelete
  4. Still haven't picked this up yet but now I will ASAP. Thank you!

    ReplyDelete
  5. Fantastic!! Thanks for your hard work, it is very much appreciated

    ReplyDelete
  6. As always...just saying thanks for the work you all put in, driven by your love for 3D gaming feels pretty inadequate. Without your efforts us 3D Vision users would be missing out on so much. Compatibility mode, and the fact Nvidia are cheeky enough to market it as if it's a good solution, is such a joke. Anytime you guys need a funding boost, run a donations campaign again...I for one will contribute again :)

    ReplyDelete
  7. You guys have done an outstanding job, thank you immensely, this game is beyond belief in 3D. The vacation to Nepal/Himalayas that I would never dare to take.
    Thank you from the bottom of my heart for keeping 3D vision alive!

    ReplyDelete
  8. Thanks !!!! Finally, i ll going to play far cry 4

    ReplyDelete
  9. nice job. it is better than 3d ready :)

    ReplyDelete
  10. I didn't had the time to say "A BIG THANK YOU"!!!!!
    While I haven't played the game that much (damn time constraint) I fired it up with and without the fix and all I can say is...WOW!!!
    Awesome job guys!!! No matter what everyone else thinks/believes.. It looks SPECTACULAR!!!!

    Again, A BIG THANK YOU!!!!!

    ReplyDelete
  11. Thanks, nvidia should be paying you guys for doing their job for them.

    ReplyDelete
  12. This looks *unbelievable* in 3D. I'm playing through to 100% - every single loot chest, location, poster, journal, etc - just because of what an experience it is to simply walk from point to point. Thank you guys!!

    ReplyDelete
  13. Thank you a lot! Let's make good use of GTX970.

    ReplyDelete
  14. the mod works great except there is a shadow halo around the gun....is there anyway to fix this?

    ReplyDelete
    Replies
    1. I'm not entirely sure what you mean by that, but it might be ambient occlusion - does it disappear if you turn AO off?

      Delete
    2. You are running in Compatibility Mode/fake-3D. Use Ctrl-Alt-F11 to switch to the real fix. You must have Advanced Settings enabled in the NVidia control panel.

      Delete
  15. With this patch when the game loads and I try to leave the house in the village i spawn in, the game freezes (on opening the door to the outside). Happens both in 3D and non-3D Vision. Once I uninstall the patch it works fine again. Im on gtx 780 sli in windows 7. I have tried different profiles in inspector but it keeps crashing on trying to go outside. Any recommendations for troubleshooting? Thanks heaps.

    ReplyDelete
    Replies
    1. Upgrade to nvidia driver version 347.52 if you are on older.

      Delete
    2. Yes, most likely answer is driver glitch. Might try doing a fully clean install with DDU. Also worth experimenting with SLI off to see if that changes it.

      Delete
  16. thanks guys. Will try when I get home!

    ReplyDelete
  17. Ok. So I have upgraded to Titan X SLI, which has given me some new challenges overall (fix games to be playable again in 3D) most of which I have been able to address by playing around with profiles except one:
    Far Cry 4 with the max payne 3 profile gives me about 20 fps (in titan x SLI(!!) ) in the area I am testing in with no ghosting. The Far Cry 4 profile on the other hand gives me around 50-70 fps in the same area but I have significant ghosting on the gun, trees and some distant objects.
    Basically the may payne 3 profile is unplayable lol, and the far cry 4 is JUST a little bit too much ghosting to be enjoyable.
    What the hell? Any idea's for troubleshooting?
    Thanks guys :)

    ReplyDelete
    Replies
    1. You can make the Far Cry 4 profile work by following these instructions:
      https://forums.geforce.com/default/topic/789514/3d-vision/far-cry-4-3d-screenshots-/post/4485684/#4485684

      Delete
    2. Thanks - I was looking how to do exactly that :)

      Delete
  18. Tried the mod today:
    - nvidia 3d ready monitor
    - Max payne 3 Profile loads
    - mod installed to the correct place
    - game configured with correct settings

    problem: 3d works but I have to select the minimum deep possible or I will get double image ( ghosting ). is this normal ?

    ReplyDelete
    Replies
    1. No, that's definitely not normal, you should be able to play on any depth you like - I play on 100% with no problems.

      Can you confirm that the version of the game is the latest (1.10.0)?
      Which driver do you have installed (though this should not matter AFAIK)?
      What version of Windows are you running?
      If your monitor is 2560x1440 (like the ROG Swift) be sure to follow the extra instructions to modify the d3dx.ini.

      Delete
  19. Game is 1.10.0
    driver is 352.86
    windows 7 x64
    Titan X GFX
    full hd monitor acer HR274H passive 3D nvidia 3D Vision Ready ( one of only two passive monitors supported by nvidia )

    Thanks for the mod and for taking care to answer me ! :)

    ReplyDelete
    Replies
    1. That should all work fine. There have been reports of stability issues with that driver, but the 3D should be working (I'm running it at the moment). Can you post a 3D screenshot of the issue so I can check if the fix has engaged at all or if something else is wrong. alt+f1 to take a 3D screenshot then upload to 3dvisionlive.com

      Delete
    2. In caverns I see [url=http://photos.3dvisionlive.com/neovad/image/556bffe9e7e564327c00003f/]this problem[/url]. It appears in any version of game.

      Delete
    3. One more issue http://photos.3dvisionlive.com/neovad/image/556c0583e7e564e3470000a8/

      Delete
    4. The first screenshot looks like a broken water shader - guess I must have missed one. Can you screenshot the map where that cavern is and let me know what graphics settings you are using (particularly vegetation, anti-aliasing and shadows which are all known to affect the water)?

      Second screenshot is a known problem: "Repair tool flame is misaligned, and can't be fixed without breaking other flames"

      Delete
  20. Cavern location - http://photos.3dvisionlive.com/neovad/image/556c706be7e564c7380000b5/ (sorry for the cyrillic font). All settings on MAXIMUM

    ReplyDelete
    Replies
    1. I've updated the fix for this issue - it was a single anti-aliased variant of the cavern water shader that I had missed. Let me know if you spot any other issues like this.

      Delete
  21. There is an issue with 3d vision rendering and stability with 352.86. I dont know about the new driver just released but the previous one was working fine for me.

    ReplyDelete
    Replies
    1. 352.86 is widely being reported as unstable across a wide range of games, causing crashes in GTA V, Witcher 3 and many other games, so you really shouldn't be running it. The latest driver out 353.06 seems a lot better, but conflicts with a lot of overlays causing CTDs. 350.12 seems to be the best of the recent drivers, but YMMV. Bo3b has been keeping track of the issues affecting 3D Vision users across all the drivers:
      https://forums.geforce.com/default/topic/777954/3d-vision/suggested-driver-to-use-/

      Delete
    2. 353.06 doesn't work with this game at all - as soon as it loads the 3D dies and it just displays in mono (actually a shifted perspective from one eye)

      Delete
    3. That's odd, 353.06 seems to work fine for me. Will do some more testing.

      Delete
  22. With the far cry 4 profile (and stereodx10flags at x400).

    ReplyDelete
  23. Update: The 353.06 driver seems to eliminate the need to adjust the stereodx10flags bit.

    ReplyDelete
  24. I've found out that setting up textures quality to middle disables wrong reflections from moon light at the all surfaces. It's rather strange ... I've always thought that it influences only on texture resolution but not on shaders executing

    ReplyDelete
    Replies
    1. That's interesting, but not entirely surprising - while creating the fix we already discovered that a number of settings affected seemingly unrelated effects, like vegetation quality affecting physical lighting effects. I'm actually planning to update the fix in the near future as some of the improvements we have been making to 3DMigoto recently should help me fix the hairworks glitch and the moon reflection.

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

      Delete
    3. So, this turned out to just be one of the combinations I missed when I made the fix. Early on it was not recommended to push textures above medium as it caused the engine to stutter, and so I missed that combination when I tested all the settings. I have an update to fix this on all texture quality settings, which I want to release along with a handful of other fixes, but I'm currently gated on a crashing bug and haven't had the time to track down the cause yet.

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

    ReplyDelete
  26. I'm having an issue where whenever I aim my gun, the shadows suddenly break and only render in one eye. There doesn't seem to be any fix for this besides closing the game out and restarting, and then it happens again as soon as I aim. Is this some setting that I have to lower that I might have too high, or maybe an issue with the latest nvidia drivers?

    ReplyDelete
    Replies
    1. Likely a driver issue - recent drivers have lots of problems with this game, including one eye issues and broken shadows. Try rolling back to 350.12 which is known to work and see if the problem still occurs (remember to change the profile again after switching drivers). The fact that it happens when you aim is interesting - the fix adjusts the convergence while aiming, which points the finger royally at the nvapi set convergence call.

      Delete
    2. Well I reverted to 350.12 and it seems to have corrected the issue. Guess I'll stick with these drivers for a while since I see them recommended for a lot of titles on this blog. Thanks for the quick reply.

      Delete
  27. I have a question about the NVidia Inspector profile for this game

    I read that the Max Payne 3 profile is better to use but if i add that to NVidia Inspector, it say's that the FarCry.exe is already assigned to a profile called "FarCry 4" so i want to know what profile is better to use. Maybe the profiles are updated, i don't know so i hope for an answer here :)
    Maybe they updated it or is the profile Max Paybe still better?
    I ask this so i can delete the FarCry 4 profile without any worries


    Let me know

    ReplyDelete
    Replies
    1. Well, i played with the Max Payne profile and set the settings to :

      Ambient occlusion to HBAO+
      Anti-Aliasing TXAA.

      But the 3D is awfull :S

      Shaders on some surfaces from sun is only seeable in one eye what makes the 3D very weird looking.... also the same happens with some shadows...

      The same happens for the Far Cry 4 Profile....
      So This is .. to be honest... not playable in 3D with 3D Vision at the moment....

      Delete
    2. I have played with all the settings in game and it seems that nothing helped to get rid of that...
      What i noticed is that there is shadow in the right eye and not in the left eye... When i turn off the 3D, the shadow dissapears in the right eye, so i guess the shadow must not be there but i can't get rid of it, but when i change the convergence, the shadow goes away but then on other places the shadow appears... So no matter what i set the convegence to, there is always a shadow looking thing on objects..... I was thinking about Ambient Occlusion but when i turn that off the shadow is still in the right eye.

      So maybe there is a layer forgotten or so.........???

      Delete
    3. Ok nevermind the shadow issue, i fixed that , so almost all looks awesome.... offcourse you mentioned the doors are somewhat brighter, but no problem, but what is a issue is that i have to set the convergence very very low and then that the mountains are offsetted, i mean the mountains in the far distance.... all in front is perfect..... but really the mountains gives headache so i try not to look so much to them whiche is a shame, they are so beautifull.... i hope i did something wrong again :) let me know......

      I forgotten some files to place in the bin folder of the game so that fixed the shadow thingy:)
      but what about the mountains in the far distance like 1 kilometer far,, they are offsetted 1 centimeter or so... that make me look weird:P

      thx

      Delete
    4. When this fix is working, the game is flawless. So, the problems you are seeing are related to the installation or maybe your driver.

      If you are using anything later than 350.12, the first installation instruction says to use 350.12. Later drivers break the game, and cause problems like you are describing.

      Delete
    5. I solved almost all of my problems.... I was forgotten to place some files of the fix in the /bin folder of the game
      but,
      I think this issue (the mountains far away that are offsetted) that still exists are not related to my VGA driver (GeForce 355.82 whql)
      I have NVidia Asus GTX 960 Strix DC2OC Edition 2GB

      Profile in the NVidia Inspector i have set back to Far Cry 4 which game me better results then Max Payne 3 profile so.....

      Settings i Have set:
      Ambient occlusion to HBAO+
      Anti-Aliasing TXAA.
      Motion Blur OFF
      and the rest of the settings like textures, geometry, High and Medium.
      1980x1020 (120 hz)

      Further indeed the game is smooth and all is good :) now it's playable exept those mountains but most of the time i don't see them so :)

      No problem.. thx anywaayzzzzz

      Delete
    6. lol sorry, 1920x1080

      Delete
    7. ok, it sounds like you mostly got this sorted, but for the record the Max Payne 3 profile is a must if using driver 350.12 or earlier. In more recent drivers nvidia changed the Far Cry 4 profile to include the necessary bits to make it work removing the need for the profile switch, but they simultaneously broke everything else making the game unplayable. I've now seen several reports including yours that 355.82 has finally improved things, which is a good sign - but I have not personally tested that and there might still be some issues. Until I personally confirm that all is well I still recommend using either 350.12 or 344.75 with the Max Payne 3 profile unless your graphics card is not supported on those versions.

      What's the issue with the mountains? If the driver+profile+fix is all installed correctly they should be flawless - can you upload a screenshot (Alt+F1 to take a 3D screenshot, upload to 3dvisionlive.com) so I can see what the problem is? It is possible that the driver has not calibrated the distance for infinity correctly for your setup and they are being displayed *beyond* infinity - What type and size monitor are you using? Is it a monitor, TV or projector? Are you using any depth hacks or inf overrides? Do you have a particularly narrow face (is the distance between your pupils less than about 6.5cm)? If you use a ruler and measure how far apart the left and right view of one of the mountains are are on the screen are they greater than the distance between your pupils? If you turn down the separation a little do they become more comfortable to look at?

      Delete
    8. Hmm, seems that when i press ALT-F! the in-game menu popsup, no screenshot is made......
      i suppose that this is going with NVidia, but i don't know if shadow play must be enabled, also i can not start the game with nvidia, i bought the game so, i have version 1.10.0 and can log in with uplay so..... but aside from that.... i can not make screenshot, i dont know what i am doing wrong here, i read NVidia article about in-game screenshot but all they tell is , press ALT-F1 and the image is saved as a JPS and is stored in C:\Users\[USERNAME]\Documents\NVStereoscopic3D.IMG...

      But there is no screenshot, and i get in-game menu, because F1 is menu in-game

      let me know thanks

      Delete
    9. I have a Asus 144 hertz monitor, 24 inch 3D vision Ready (Asus LCD Monitor VG248)
      I dont use hacks overrides or whatever, only this fix.
      And lol, no my eye space is okay.... no narrow face, other games play well, also this one, its minor but i guess its fixable.
      I meassured my eye space, and it is more then 6.5 cm..... so i guess im good with that :) pheeww

      And when i use convergence to lower it, the mountains stay offsetted, only lower the 3D depth will fix it but result in all becomes 2D again so...., i have made some screenshots, now i try to look how to post them here with a link or so.......

      Delete
    10. Ok, i guess this is the link
      http://photos.3dvisionlive.com/Progje/

      I can make some more if you want, with different 3D settings as you wish.....
      We all want best results offcourse:)

      As far as i know , best game i saw in 3D...

      Delete
    11. i quote: It is possible that the driver has not calibrated the distance for infinity correctly for your setup and they are being displayed *beyond* infinity

      That seems very logic.

      Delete
    12. What i did to fix the HUD a bit was to set the
      ; x sets HUD depth. 0 is screen depth, 1 is max, negative to pop out
      ; 0.955 is default
      x = 0.700

      I don't know if that is a correct setting, but seems that when i set the 3D depth very high and the convergence so that the closest object looks perfect, the HUD also looks perfect as also with the markers on the screen from missions etc.... all is left are the mountains.......

      Let me know if x = 0.700 for the HUD is a suitable value, i mean it was set on x = 0.995, which was offsetted for me......
      But was fine before i bought the game....
      The hud offset started after i bought the game today.

      Delete
    13. ok, there are some broken effects in those screenshots - the puffy clouds / fog have halos (I think this is probably the problem you mentioned with the mountains), and the the interior shadows on the buildings are misaligned and extrude through to the outside. These effects should all have be fixed and work fine on the latest version of the game using driver 344.75 and 355.12, so there must be something unique to your setup that cause them to still be broken. Possibly it's the driver or profile - I'll download 355.82 and see if the same thing happens. It might also be that you have used some combination of graphics settings that I missed - can you give me a list (or screenshot) of your graphics settings so I can check? Another possibility is the fix is not correctly installed, like missing files in ShaderFixes or permission issues? It could also be an SLI issue, but no one else has reported that issue on SLI.

      One of those screenshots of the mountains had a very high convergence making everything in the foreground impossible to see - I assume you did that on purpose for the screenshot and don't play the game like that? (the toyification effect on the trees does look awesome like that though ;-)

      As for the HUD, 0.7 is a quite reasonable value - that's one of those personal preference things. I tend to use 0.995 in first person games so that the crosshair lines up better with distant objects (and close objects tend to be large enough that I don't need the accuracy), but that can put the HUD behind objects which some people don't like. I've been meaning to see if I can adapt my auto crosshair depth code to work with this game, but I need to finish some supporting code in 3DMigoto first.

      Delete
    14. Well, 355.82 with the Far Cry 4 profile and fix installed seems to work perfectly on my system :)
      Had to turn compatibility mode off of course, but I didn't see any of the driver bugs that have plagued this game since 352.86 :)

      Delete
    15. I did post 1 photo that was indeed over-used convergence just to show that the mountains are correct when use too much convergence.

      compatibility (ctrl+alt+F11) seems not doing anything here..... i changed it also to ctrl+alt+F12 but same, nothing happens, i don't even know what to expect when i try to turn it on or off....

      I kinda knew the driver was okay, so whats with those issues i have you saw on the photos???

      I post a photo of the in-game settings aswell....

      As for the fix, i just unzipped it in the /bin folder of the game, used nvidia inspector to use Far Cry 4 profile and applied that in the inspector.
      When game starts, it shows Far Cry 4 profile for 3D.

      Delete
    16. I annotated your screenshots to show what is wrong:
      http://photos.3dvisionlive.com/DarkStarSword/image/55fb9a87e7e564ef13000212/
      http://photos.3dvisionlive.com/DarkStarSword/image/55fb9aa6e7e5649f6e00000d/

      The high convergence screenshot still has broken clouds as well. The only reason it looks better is that you have moved the broken effect closer to screen depth, reducing (but not eliminating) the misalignment:
      http://photos.3dvisionlive.com/DarkStarSword/image/55fb9acee7e5646d6100000a/

      For a comparison, here's what those scenes look like in my game. I set my separation to 70% on my 17" monitor to take these, which should be roughly equivalent to 100% on your 24" monitor if you display them in full screen:
      http://photos.3dvisionlive.com/DarkStarSword/image/55fb99fde7e564610300000b/
      http://photos.3dvisionlive.com/DarkStarSword/image/55fb9b40e7e564cd17000007/

      Looking at your screenshots it looks like infinity has been calibrated to about 4cm if those were displayed on a 24" screen, well under the 6.5cm inter pupil distance that the driver aims for (so, I'm guessing your separation must be set to around 60%), so that should be fine - nothing is being displayed beyond infinity, it's just broken.

      The screenshots you posted appear to be real 3D and not compatibility/fake 3D - if you enable the green overlay text it should tell you if it is on or off. It does seem strange that you haven't had to turn it off though, because it is enabled by default on 355.82. That suggests there might be something wrong with the driver profiles, so I'd recommend using DDU to cleanly uninstall that driver and reinstall it to eliminate that possibility.

      BTW you shouldn't need to use nvidia inspector with the 355.82 driver - nvidia updated the Far Cry 4 profile at my request after releasing this fix, it's just that they broke everything else at the same time so we've had to stick to old drivers until now. If you go back to an older driver you would need to use it of course.

      I'll go through your settings and see if there's some combination I may have missed. One question - are you using a single GPU, or SLI? I can only test a single GPU configuration - if there are issues with SLI on this driver I wouldn't see them.

      Delete
    17. I matched all my settings with yours and even tried uninstalling and reinstalling the fix from the blog to make sure I'm running the same thing as you, and ... it's still working fine. I'm really not sure why it's broken for you - there must be something weird going on specific to your system. What else can you tell me about your system? What version of Windows are you running? What graphics card are you using? Definitely try using DDU and cleanly reinstalling your driver because that is known to help some problems. Maybe use winrar to verify that the zip file you downloaded didn't get corrupted in transit, maybe try the driver I've continually recommended that hundreds of other people have used without issue.

      Delete
    18. I noticed you uploaded some new screenshots so I had a look:
      http://photos.3dvisionlive.com/Progje/image/55fb5c74e7e564eb3a00001c/

      The fact that the water is only broken in one eye tells me the issue is definitely in the driver profile - *this* is why it is necessary to switch the game to use the Max Payne 3 profile on 350.12 and earlier drivers. As to why you're seeing this on 355.82 with the Far Cry 4 profile (which should include the fix) - I'm not sure, but I'd bet that something went wrong when you used nvidia inspector and you ended up with the game in a blank profile instead of the Far Cry 4 profile (it might still be called "far cry 4" - the driver names new profiles after the executable). This would also explain why toggling compatibility mode didn't do anything - that option only exists if the game is in the Far Cry 4 profile.

      Reinstall 355.82 and don't touch the profile and it should work.

      Delete
    19. I dont have SLi, i have Asus GTX 960 DC2OC 2GB (OC Edition)
      So Single GPU, just 1 card in it :)

      So hmmm, i dont need the Nvidia Inspector at all.... So to fix that problem, reinstall 355.82 and clean it before with DDU..... i'll give that a try:) thanks

      Delete
    20. Oh sorry, i forgot to mention i am using Windows 7 (64 bit)

      Delete
    21. Ok here we go :)
      I used DDU to uninstall the NVidia driver without restart..... Then i downloaded the newest driver again.
      Installed it and do the 3D wizzard again....
      NOT used the NVidia Inspector. I just started the game and i saw that it was on Far Cry 4 Excelent and Compatibility Mode was ON so i turned that off and VOILLA!!!! there the menu was in 3D :) and now ingame all is perfect :) i guess even the door shaders :) i let you know and post screenies:) Thanks for your help :)

      Delete
    22. No worries, hope you enjoy the game :)

      Delete
    23. Yes i really enjoy the game.. thanks

      1 question about the editor though... i can't find an answer... Does the editor work in 3D ?
      I can imagine that it doesn't work because first it is in windowed mode, and second it hasn't a fix to do so... but who knows, i tried to turn on 3D always instead of only when 3D applications are enabled but didn't work..

      Should be awesome to make a map and try it in 3D in the edtor itself :)

      Delete
    24. I haven't tried the editor, but if it runs in a window it will be a deal breaker - 3D Vision just doesn't work in windowed mode with DX11 (DX9 can work with a profile tweak, but this game is DX11). The only possibility here would be to use a recent version of 3DMigoto (such as 2.1.0) to try to force exclusive full screen mode with set full_screen=1 in the d3dx.ini. Beware that recent versions of 3DMigoto may crash after around 10 minutes in this game on some systems, which I have yet to track down.

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

      Delete
    26. It seems that the waters in Shangri-La has the same problems i had with the waters outside Shangri-La.
      I posted a 3D picture here: http://photos.3dvisionlive.com/Progje/image/56033eace7e564124300025f

      Let me know thanks :)

      Delete
    27. NVidia driver is now 355.98 by the way.... i checked to be sure that it wasn't 355.82
      Maybe good to know what driver i was using..... i didn't update it , i guess he did that automatically.. i can remember 355.82 but okay :)

      Thanks

      Delete
    28. Can you confirm if that water is broken in only one eye (signifying a driver profile issue), or both eyes (signifying an unfixed shader) - I can't quite tell from that screenshot.

      Delete

    29. Yes, the it's on the right eye that i see the offsetted stones in the water, the left eye is good.

      Delete
  28. Why doesn't NVidia provide us with fixes for games???
    I mean, why do people pay 150 bucks for glasses if games can't use it and we must hope for someone that make a fix everytime?
    I think NVidia is responsable for this but that can be just me cuz i am a nice guy and i thank you a lot for making these fixes, some of them worked as far as i know but after a while, banggg, doesn't work anymore and my 3D glasses are useless......

    ReplyDelete
    Replies
    1. To be honest, the nvidia driver is simply not capable of automatically fixing anything but the simplest of rendering issues. Anything more complicated than that requires either the developers of the game and/or engine to fix them, or a modder from our community to step in and do it for them. You could argue that Nvidia should hire someone to do this full time (/me puts up my hand), but given that modding is generally a legal grey area at the best of times I don't think we can realistically expect this to happen. The most support we can [strike]expect[/strike] hope to get from them is fixing bugs in their driver, not adding new bugs with every driver release, and possibly working with the developers directly to support 3D Vision natively - unfortunately, given their track record none of these seem very likely :(

      Delete
    2. So basicly NVidia sell stuff which actually doesn't work (specially later on) and hope that people fix problems for them for nothing? hmmm makes me think.

      Delete
    3. To be fair, nvidia did used to push developers to support 3D Vision a lot more - the fact that this hasn't continued can be blamed just as much on the uninterested developers as it can on nvidia. And don't forget - this community has fixed almost 400 games so far, and none of that would have been possible without nvidia - we are using their technology (both hardware and software) after all. Don't get me wrong - I'd love it if they did more, but I really don't expect anything from them.

      Delete
  29. Is there a way to make a fix for The Hunter: Primal ???

    It does already works but when go out of the game, the settings of convergence is back to it's old settings....
    I don't really know what options are available when you make a fix for a particular game, but i know there is a fix for a game with a komma ( , ) and period (.) keys to store the settings, like Ghostbusters The Game has for example....

    And i will look also for eventually problems/issues the game have with 3D stereoscopic...

    It is the same engine as The Hunter from steam... Only with primal animals....

    Let me know thanks, should be awesome:)

    ReplyDelete
    Replies
    1. Hmmm, actually, game is pointless.... so i see no reason why fix the convergence to save it.... there is nothing to do in the game so nevermind i asked:) thanks anywayz

      Delete
  30. I have the game Soma and i use the 3D wrapper for the game, 3d looks awesome only there is 1 thing .....
    Do you have a categorie from the game here on the site? so we can place our experience with the 3D wrapper?
    I have a small issue that i got a bit seasick when moving the mouse around because looks like the 2 images (left and right eye) moves independent from eachother, makes people seasick......


    Let me know

    ReplyDelete
  31. Might I suggest you post on the SOMA thread on the geforce forum instead of the Far Cry 4 post? Likewise, requests for new fixes would be better off on the forums.

    ReplyDelete
  32. So this gamefix you never gonna put on this website? i must switch to different sites for fixes and/or more info? i guess thats the whole point of this site isn't it? anywayz thanks

    ReplyDelete
  33. My preference is all completed fixes should be posted on this blog, which will automatically add them in the game list. I have a manual list I maintain of fixes that were not posted on this blog (including Helifax' OpenGL fixes) that is merged into the game list, but as it's a manual list I have to update it manually and so it may not always be up to date (e.g. the SOMA fix was only released yesterday) or might be missing some titles (let me know if I've missed any), and not all browsers will refresh it properly even if I have updated it.

    I was suggesting you post elsewhere because this page you are commenting on right now is for the Far Cry 4 fix, but the last couple of comments have nothing to do with Far Cry 4, so this is not the right place for those comments. If the game does not have a page on this blog you can post on the geforce forums 3D Vision subforum instead, which is where we develop the fixes - it will also be seen by more people in the community, whereas comments on this blog will only be seen by people who have explicitly clicked "notify me" for whichever page you posted on.

    The Geforce Forums 3D Vision subforum is here:
    https://forums.geforce.com/default/board/49/3d-vision/

    and the SOMA thread is here:
    https://forums.geforce.com/default/topic/879631/3d-vision/soma-3d-vision-support-thread/

    ReplyDelete
  34. Hello anyone reading !
    Huge thanks to everyone involved in the making of this patch, as the Far Cry series is one of my favorite, and I couldn't imagine playing it without 3D Vision :-)
    I just upgraded my GPU (980Ti), DDUed and installed drivers 355.98.
    Then I installed Far Cry 4 and...
    Well, there is something very strange happening - never saw such a 3D 'bug' before : when I don't move, the game look perfect. But as soon as I move, I lose all depth. When I stop, depth returns. Not instantaneously, it takes about half a second where progressively front objects move back in place, distant objects are pushed away etc. As if left and right images were unsync while moving, and get back in sync when idle.
    If I decrease convergence a lot, the problem disappears but the game look all flat, as if I also lost all depth.
    I tried playing with graphic settings, but no chance.
    Anyone having the same problem ?
    Any idea what's happening ?

    Thanks !

    Laurent

    ReplyDelete
    Replies
    1. Are you on Win10 by any chance? Win10 is broken with any driver newer than 350.12

      Delete
    2. Oups, I forgot to mention my os : Seven pro x64. Every other game with patched ou native 3d vision works fine, so I'm really puzzled here...

      Delete
    3. ok, you might be hitting another driver bug that was introduced after 355.60 that causes stuttering in one eye in some games. I haven't checked if 355.60 works with this game or not - the drivers have been a buggy mess for months now. 350.12 definitely works if you can use it.

      Delete
    4. Yeah, probably :-/
      I'll try 350.12 if I can.
      thanks !

      Delete
    5. Ok, found the problem, and I feel so stupid ! I alway use my right mouse button to move, and that same button is changing convergence in d3dx.ini... forgot to look in that file this time... shame on me ! Things are perfect now... great :)

      Delete
  35. Teaser: 3DMigoto crash fixed, update coming soon...

    ReplyDelete
    Replies
    1. Nevermind... at least two more issues to solve first that affect Win8 and above

      Delete
  36. Replies
    1. Oops, sorry about that - I must have deleted the wrong file when I was cleaning up some outdated versions the other day. It should be working again now, but just FYI I have a substantial update for this fix coming out in the next few days (the current one works just fine, but the new one adds some new goodies like an automatic crosshair and fixes most of the remaining minor issues). When that's out I will bump this back to the first page of the blog.

      Delete
  37. You guys are incredible!! Thank you thank you!! Can't wait for the next release with new goodies. :D

    ReplyDelete
  38. woohoo! thanks so much for new version :D

    ReplyDelete
  39. This comment has been removed by the author.

    ReplyDelete
  40. i have gun shader Handling=skip in the d3dx.ini.disable gun model in normal view.
    how can i setup----hold a key to enable this shader with XB_LEFT_TRIGGER?
    i know this ( Key=XB_LEFT_TRIGGER Convergence=3.00 Type=hold)

    ReplyDelete
  41. Sounds like you have hit a decompiler bug in 3DMigoto - we would have to either manually fix the shader, use the assembly version, or fix the decompiler to handle that case. Are you hunting the vertex or pixel shader? You might be able to disable it via the other type if it doesn't affect too much else. The handling=skip method of disabling a shader currently has no means to tie it to an IniParam - we could possibly add that but in general I'm preferring to keep complex logic in the shaders rather than 3Dmigoto.

    ReplyDelete
  42. Thanks a million. Awesome...
    So much hope for Far Cry Primal :-p

    ReplyDelete
  43. Hi, it's working fine in proper 3d, but my crosshair is always at screen depth, I use a controller, SLI 970's... windows 7, driver 358.87.... everything else seems fine.

    ReplyDelete
    Replies
    1. Hmmm, might be a combination I missed - can you post your graphics settings?

      Delete
    2. 1900X1080 Every graphics setting on the maximum allowed/enhanced setting but motion blur and AA off. I tried lowering terrain to medium, and tried all presets from low to ultra settings.

      It's just the floating crosshairs found on scopes that are screen depth.

      Delete
    3. Huh, that's odd - those shaders are supposed to use a minimum depth that matches the weapon scope (and maximum from the auto crosshair code). I did check a bunch of weapons, but maybe I missed a shader - can you give me an example of a specific weapon and scope that has this problem?

      Can you also run a quick experiment and see if disabling SLI clears it up?

      Delete
    4. SLI off makes no difference. I have tried many gun and scope combinations. I had tried the F1 assault rifle with the red dot sight, and the MS16 rifle with the long range scope, also the F1 with the reflex sight also, and the recurve bow with the available sight. Anything with the floating reticule in the middle, all iron sights are fine of course.

      Delete
    5. "It's just the floating crosshairs found on scopes that are screen depth.".
      Happens when uninstall.bat was not carried out before installing the patch

      Delete
  44. OMG, DarkStarSword! OMG!!! Thank you SOOOO much!

    ReplyDelete
  45. Is this shader hacking or sorcery already?! Amazing work and improvements!

    ReplyDelete
  46. This fix only works on 3D Vision or on 3D TV Play?

    ReplyDelete
    Replies
    1. Works on both. There is no difference between them. Make sure your 3D is working properly before running any fix.

      Delete
  47. Is it normal for the fix (2015-12-21) to have a big impact on fps? I disabled 3d in control panel and tested this with and without the fix and I get about 1/3 less fps when the fix is enabled (~63 vs ~95 looking at the same spot in Banapur).

    With 3d enabled the numbers are ~41 with the fix and ~58 without it.

    I'm using Win 8.1, 359.06 drivers, i5-4670k and GTX 980Ti.

    ReplyDelete
    Replies
    1. Can you do a couple of experiments for me to narrow down where the performance hit is coming from? First, uninstall the new version of the fix and install the old version to see how it compares without all the new features. Then, uninstall again and switch back to the new fix and edit the d3dx.ini and change track_texture_updates to 0 to see how much of an impact that is having. Then, search for the lines "post ResourceZBuffer = stereo2mono o0" and comment them out and measure again. There's other things that may be having an impact as well, but those are probably the two most likely candidates.

      Delete
    2. Ok here's what I got (all numbers are with 3d enabled):

      No fix, as said earlier: 58
      Old fix: 57
      New fix: 41
      New fix, track_texture_updates = 0: 54
      New fix, track_texture_updates = 0, resourcezbuffer lines commented: 54
      New fix, track_texture_updates = 1, resourcezbuffer lines commented: 41

      So it seems that track_texture_updates = 0 helps a lot. Does it have some negative effects? This is pretty much the worst fps I get anywhere, so with that disabled I should have 60 fps 95% of the time.

      Btw. with or without the fix I have 1 core at 100% utilization. And that's even with the cpu running @ 4.7 Ghz.

      Delete
    3. Ok, thanks for that - I was pretty much expecting that to be the main culprit as it has to recalculate texture CRCs whenever the game changes them (which is often). track_texture_updates=0 will cause some of the UI adjustments to break from time to time, but it's inconsistent. The most important ones like the crosshair and floating HUD icons seem to be unaffected in my testing so you can probably play with that disabled ok, but it will cause issues for things like the camera HUD, some of the layers on the full screen map (vignette and clouds) and some things in the main menu from time to time.

      I have some ideas that may be able to reduce the performance hit, but they will take a while to implement.

      Delete
  48. I just finished playing FC4 with this fix. I started without it, not knowing about it. Then used this and WOW -- so awesome. Thank you guys, you rock!

    ReplyDelete
  49. Firstly, thanks for the release! I'm having problems though. I've downgraded my driver to the recommended 358.87. I unpacked all contents of zip into FC4\bin\ - try to run the game but it force closes on boot. My spec:

    Win 10 64bit
    i5 4670k
    gtx 980 ti
    rog swift

    Game works fine w/o the 3d patch. Any ideas please? Thanks

    ReplyDelete
    Replies
    1. Update: I got it working by disabling uplay in-game overlay and disabling shadowplay. Initially boots into compatibility mode, so i toggle 3d compat mode, but there is no 3d image [i can see 2 2d images clearly]. How do i solve please?

      Delete
    2. That's odd. What do you mean by 2 2d images - as in side by side? Can you provide a screenshot? You might try using DDU to do a clean reinstall of the driver, and also use uninstall.bat and reinstall the fix cleanly.

      Delete
    3. Thanks for your response. Not sure if I misread earlier about requiring nvidia inspector, but after trying to resolve I installed it anyway and that seems to fixed the problem. Game looks fantastic! Glad this is my first play through! Ever thought about approaching nvidia and pitching for a full time job?

      Delete
    4. BTW, have you experienced low/poor LOD with the game? Here's some examples of what I mean but I don't think mine is as bad as this http://www.overclock.net/t/1552861/bad-draw-distance-lod-pop-ins-with-gtx-970

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

    ReplyDelete
  51. Hello guys!
    First of all thank you very much for the job you do for the community, the fixes are amazing:-)
    My problem:
    I am running in some issues trying to play far cry 4 with the fix. Somehow all ui stuff (crosshair minimap text and so on) sticks on the screen plane (also tried different graphic settings).
    After some analyzing i found the issue: all shaders that using crosshair.hlsl fail to compile. I have replaced the #include command with the content of the file directly and everything is working now. Somehow the 3DMigoto can not compile #include command on my system :-( (My guess is, the 3DMigoto cant find the shader path. Maybe it is somehow hard coded in there)
    Some add. info:
    I play the game over steam on win7 x64 with gtx980 ti driver version 361.75 (Have not tried other versions yet)

    ReplyDelete
    Replies
    1. Interesting - my guess is that perhaps the Steam version is using a different working directory from the uPlay version. Can you do a quick experiment and see if it works with #include <bin/ShaderFixes/crosshair.hlsl> instead?

      Delete
  52. Hi,
    thanks for the quick response :-)
    Yes it works that way. Is there other stuff that requires a similar fix?

    ReplyDelete
    Replies
    1. Ok, thanks for testing - I'll need to write an include handler in 3DMigoto to solve this problem properly, until then you can use the modified paths.

      Delete
  53. I just updated the fix again - this fixes the crosshair in the Steam version of the game, re-fixes Hairworks, fixes an MSAA version of the interior mask clipping issue, and adds SBS and TAB output modes (must enable in the d3dx.ini).

    ReplyDelete
  54. So I seem to be running into a weird issue involving any game that needs Uplay. (I have disabled in-game overlay on both uplay and steam, the issue still remains) Any game that runs Uplay will not run nvidia 3d or will crash. all other games run 3d and 3d fixes fine, but if uplay is involved the 3d will run but all that shows is a 2d image (possibly the right eye; the transmitter light is running and I get the ctrl+alt+inst text in the bottom corner but no 3d image) this is with far cry 4, with splinter cell the game crashes when entering gameplay. Not sure why uplay has begun giving me this problem, far cry 4 was doing 3d fine weeks ago. any help would be greatly appreciated and again thanks for all the great work.

    ReplyDelete
    Replies
    1. Did you update drivers recently? I'm hearing reports that some of the recent drivers are giving people trouble, but I haven't looked at the details. I'm still on 361.91 which is working fine for FC4 and FCPrimal, and I've had a report that 362.00 is working as well, but anything more recent may be broken. Try using DDU to uninstall your current driver then switch to either of those to see if they help.

      Delete
    2. found the issue, turns out it was some weird thing where my monitors settings had reset from 120hz to 60hz causing uplay games to just flip out. everything is working fine again. thanks again for your work and your help.

      Delete
  55. Unfortunately when I try to start or load a game I get an insta-crash to desktop and Uplay client, with no error message and can not get this game to play in 3D. :(

    ReplyDelete
    Replies
    1. What OS are you running? And if it's Win7 do you have KB2670838 installed or not?

      Delete
  56. What am I doing wrong? The reticle in scopes is hopelessly off (misaligned) unless I set 3D depth to none, as well as the on screen crosshair - the net effect being I can either play it without any 3D effect, or be unable to aim.

    -Tried the recommended driver 358.87 as well as the newest one with the exact same result.
    -Unpacked zip to Far Cry 4\bin directory
    -Ambient occlusion is on HBAO+
    -Disabled motion blur
    -Using single GTX 980 on Win 8.1.

    When I started the game it came up with the compatibility mode message. I tried toggling into 3D Vision mode which only made the HUD elements on the bottom right disappear as far as I could tell. It works fine after uninstalling the fix, with the known issues addressed by the fix intact, of course... But playable.

    I'm new to 3D Vision (as in just got the kit this Sunday), so there could very well be something stupid I don't know to do...

    ReplyDelete
    Replies
    1. Should work, but there are lots of variables, including that the game might have updated and broken the fix.

      It sounds like you are probably still in Compatibility Mode, and you don't want that, the fix only works in Automatic mode. Use Ctrl-Alt-F11 to toggle mode to normal Automatic. You need the Advanced Options enabled for that to work.

      Aiming overrides should work for both right mouse and xbox left trigger. If you are using something else, it won't work unless you add an override in d3dx.ini.


      To debug this, try removing the fix altogether with Uninstall.bat, and run the game to see how it looks in 3D Vision Automatic mode, and make sure all the settings work and you have graphics setup.

      Then add in the fix. Look to see that it changes and fixes the game. If nothing changes, you'll know it was installed wrong/is not active. If it looks good and it's still something with aim override or HUD, we'll have to take a look.

      Delete
    2. Thanks for the extremely fast reply! I'm not at home now but I will be able to refer to this information later tonight.

      -Everything works fine in Compatibility Mode with the fix uninstalled.
      -I will enable advanced keys and do the Ctrl-Alt-F11 mode toggle. I thought I tried this though.
      -What is "Automatic mode"? Is that the same thing as 3D Vision mode?

      I think have got it with the aim mapping - I map aim to what Far Cry calls "mouse 4"... It's the "back" button on a mouse with the left-side forward/back buttons. I believe this is VK_XBUTTON1, or XBUTTON1 in d3dx.ini per http://www.codeproject.com/Articles/14016/Handling-Keyboard-and-Mouse-Application-Buttons-in.

      Delete
    3. You can see what mode it is in with the Nvidia green text, Ctrl-Alt-Ins. Compatibility Mode is OK, but is generally considered weak sauce compared to our fixes. For this game in particular, DarkStarSword has made it perfect, so the real fix is 10x better than CM. As a general idea, we mostly only use CM as a last resort, I don't know anyone who prefers it to a real fix.

      For the aiming, you'll need to edit the d3dx.ini and change the override key. I'm not sure what matches, maybe VK_BUTTON4. You'll need to experiment.

      BTW, I tested this just now, and the fix is working flawlessly.

      Delete
    4. All better now, and it looks AWESOME! Frame rate took a slight hit though. Set track_texture_updates=0 and seems to have helped a little. I'm reading around 45 FPS with all settings on ultra + HBAO+, simulated fur and godrays off. I guess I have my GTX 1080 justification now! >:)

      Do you guys have a recommended depth setting?

      BTW, the Virtual Key Code for the "back" button on the mouse is VK_XBUTTON1 and the "forward" button is VK_XBUTTON2. These are the buttons on the left side of pretty much any mouse fancier than the most basic models.

      Last, the fix works fine with the 368.69 driver.

      Thanks for all the help!

      Delete
  57. I got the newest drivers 372.54 but there are some shaders that are not correct.
    Can you confirm that this is due to the new driver?

    It's kinda weird that we have to switch drivers for each game these days.
    I installed Far Cry 4 yesterday again and used the new fix and have set it to HBAO+ as described.

    I see the green letters when i turn on 3D and also it is not in compatibility mode as that get rid of the seperated views so i guess it's due to the new drivers that i used for No Mans Sky.
    I also not use SLi as i only have 1 GPU.

    It worked before but now it doesn't.
    Hope you can help me on this
    Thanks

    ReplyDelete
  58. Thanks a lot for the awesome fix :)

    ReplyDelete
  59. driver 372.90,windows 10.monitor asus rogswift 3d ready.before instalation 3dfix for far cry 4 and more games work fine in 3d mode....upgrade the driver a latest version 373.06 and the 3d is very bad....incorect shaders,ghosting efect en games 3d ready,etc. reinstall games,drivers , 3dfix again ,etc. no solution...I disconnected the monitor( the power cord) and surprize!!!work again!all the games Fr Cry 4, assasins creed black flag,etc. and the games 3d ready(tomb rider) without ghosting efect again!!!It is the possible solution for people who have similar problems...it works for me...sorry for my english!

    ReplyDelete
    Replies
    1. He visto que mucha gente tiene problemas con la configuración del 3d después de instalar los fix...he tenido el mismo problema y en apariencia no había solución...shaders incorectos,efecto fantasma y otros artefactos...con el driver 372.90 después de instalar los fix los juegos en 3d han funcionado perfectamente...al actualizar el controlador a la versión 373.06 han aparecido los problemas arriba mencionados.asi que he reinstalado los juegos, los fix y he revertido el controlador a la versión 372.90.sin resultado....hasta los juegos 3d ready (tomb rider por exemplo) se veían mal...sobre todo con mucho efecto fantasma.Entonces he desconectado por unos segundos el monitor de la toma de corriente lo he vuelto a conectar y he reiniciado el pc.Es como todo ha vuelto la normalidad ... puede ser la solución .a mi me ha funcionado así cuando parecía que no hay manera de resolver el problema...

      Delete
  60. New drivers fix is completely busted.

    ReplyDelete
  61. Just retested the fix using Win7, Driver 368.22, GTX 970, and it's working well.

    ReplyDelete