[Guide] Win 10 v1903+, gfx driver v430.39+ 3DV Fix

Post by **schwing** » Tue Oct 15, 2019 4:15 am

    3D Fix Manager and BringBack3DV are newer, automated ways to bring back 3D Vision on Windows 10. If you've installed Win 10 recently, then you likely need this fix to get started again. The below is the original fix if you ever want or need to do it manually.

---

    The original guide for doing this manually if you happen to need it:

    I'm happy to announce a fix for Windows 10 1903 3D Vision for 430.39+ gfx drivers! The fix below is the final version. Please keep this guide
on this forum, and all support requests in this thread, by PM, or the 3DV Discord. Thank you very much for your patience.

    Here are the fix steps, and choose option 1 or 2:

Read the guide before proceeding, then restart in Safe Mode.
Option 1: file replacement (easier method, but 442.19 is required)
- Download a 7z file containing two 442.19 DLL's for Standard or DCH, depending on what gfx driver you have installed, and an optional batch file
  (thanks, UnityBeing, for the suggestion).
- If the batch file doesn't work for you, then use a Take Ownership method from option 2 and do the following:
  - Go to C:\Windows\System32\DriverStore\FileRepository and find the nv_dispi... (or: nvmdi...) by sorting by Date Modified descending
    - If you can't find the folder, look for one that has the DLL's.
  - Right-click the folder and choose Take Ownership. In my testing, doing this on just the DLL's to replace was not sufficient.
  - Go into the folder, back up the DLL's you are replacing, and replace them with the downloaded ones.
    - If the folder was some other name and option 1 doesn't work, then revert using your backup files and try option 2.
Option 2: hex edit (manual method, probably any future driver)
- Choose a Take Ownership method below:
  - Install Take Ownership from the "one-click registry" option at the bottom, extract it with 7-Zip, and double-click the "Add" .reg file.
    - Confirm that the menu option appears when right-clicking a folder and a file. It doesn't work on a folder if you're inside it.
  - Or: JurandyRafael suggested NTFSAccess, which avoids adding to the right-click menu and is a more traditional method.
- Go to the same folder as in option 1. Back up the DLL you are hex editing, right-click it, then choose Take Ownership.
- Open a hex editor as admin (I use HxD), go to the same folder, and hex edit the DLL as below.
- Explaining the step below: open the DLL, copy the bytes on the left in the step below, and paste them in a Find window (CTRL+F). Choose the
      Hex-Values (or Bytes) option before pressing Find. You'll arrive at the first byte, which is 83. Pressing Find again should show some error or
      do nothing. Replace by copy-pasting (HxD: CTRL+B) the bytes on the right. To prevent typos, don't type them manually. Before you replace,
      make sure the cursor is on the left side of 83, and that the hex editor says "Overwrite" on the bottom (toggled with the INSERT key).
- For nvwgf2um.dll (32-bit games): replace 83 F8 07 0F 87 D3 01 00 00 FF 24 85 with B0 08 EB 0C
- For nvwgf2umx.dll (64-bit games): replace 83 F8 07 0F 8F 97 01 00 00 with B0 08 EB 05
- Save your changes (and ignore any access errors).

Final steps:
- Restart your computer.
- The 3D Vision driver can be installed before or after this guide with 3D Fix Manager or the Losti method.
  - You may have to restart the computer, but usually stereo works after the installation finishes.
  - If you have a DCH gfx driver, then follow this post to get DCH working. You may experience slow app startups while stereo is enabled. This
    doesn't happen for Standard gfx drivers.
  - If you get a "driver mismatch" error, then you installed a DCH graphics driver
Test modern-looking games (DirectX 10+) or generally ones you know don't work without the fix.
- Tomb Raider DX11 stereo works but DX12 stereo itself seems to be broken even in Win 10 1803.
To be safe, avoid launching games that have anti-cheat functionality, MMO's, or generally any game that has a ban feature.
- There is no way of knowing if the fix triggers one until it does, except to revert the fix using your backup files.
- At the minimum, we only expect feedback for games that have a 3Dmigoto fix applied anyway (typically offline single-player games).

Feedback suggestions:

Games you tried (especially UE4 games)
What went wrong (e.g. game startup broken, guide step undoable, etc.)
What works without the fix (people have been reporting this phenomenon, probably their display of choice is why)
Gfx driver version you tried (430.39 or later only)
Your specs (e.g. i3/i7 CPU, GPU, etc.)
Attachments/links (e.g. d3d11_log.txt after launching the game if d3dx.ini has calls = 1 and optionally debug = 1 under [Logging])

Post by **schwing** » Tue Oct 15, 2019 4:16 am

Most recent changes:

2020-05-02:
- Added 3D Fix Manager link and decided to call this guide's fix the final version. It has been well-tested by now and integrated into a couple programs.
2020-03-30:
- Robert256's automated solution is now the first method. This will make the 3DV installation a lot easier. I linked to his thread in case
  he changes the download link.
2020-02-11:
- Added a batch file to Option 1 to automate the file replacement process per UnityBeing's suggestion.
- Restructured the guide to rely on the batch file and fall back to other methods.
2019-11-14:
- Reduced the amount of bytes needed to replace with
- Added DCH support to the guide after posting a way to add DCH support in 3D Fix Manager's forum thread

Known issues (2019-11-02):

DX9 games aren't stereo in windowed mode
- I haven't seen this happen except for Resident Evil 4 HD
- One workaround is using DGVoodoo and making a DX11 fix.
Red overlay text appears when stereo is enabled
- I haven't seen this happen at all, but it seems to be an issue with the refresh rate not being high enough.
- My suggestion is to use Nvidia Profile Inspector, go to the global profile (it appears first upon launching), go to the 2 - Sync and Refresh
  section, and modify the Preferred Refreshrate setting. See which option works. You can check if the game is overriding this setting by
  going to the game's profile instead.
- Another idea is to try the refresh_rate setting in d3dx.ini of a 3Dmigoto fix.
- 2020-03-21: Display Driver Uninstaller has been reported to help. Try it before this guide in Safe Mode and see if it helps you.
DX12 stereo doesn't kick in from at least 1709 (at least for Shadow of the Tomb Raider)
- This requires a different solution than the DX11 fix
- 2019-11-22: I've figured out how to get the overlay to appear so far.
3D movie software doesn't work or has crosstalk
- Try using a different player or troubleshoot whether the player is the problem.

Post by **RAGEdemon** » Tue Oct 15, 2019 9:44 am

Wow schwing, thank you very much for this!

Post by **skyrimer** » Tue Oct 15, 2019 10:08 am

I'm on 1903 so I'll see if I can give this a try and report, amazing work scheming!

Post by **ToThePoint** » Tue Oct 15, 2019 10:15 am

Yes indeed, impressive stuff there schwing. As a current non Win10 user, it's still very reassuring to know that you've managed to get this method working for you, and hopefully others will be able to replicate your own success with v1903 over time.

Post by **Losti** » Wed Oct 16, 2019 7:26 am

Woow ill test this !thank you so far!

Post by **Shift-E** » Wed Oct 16, 2019 8:05 am

great find! any step to keep 3D Vision alive and working with the constantly changing windows 10 environment is a major plus. This should be useful for the VR folks who need the windows 10 updates.

thanks to everyone doing their part to keep 3D alive!

Post by **Losti** » Wed Oct 16, 2019 8:16 am

What are the things you replace in the Files with hex Editor?

Post by **DJ-RK** » Wed Oct 16, 2019 5:10 pm

Works for me on Win 10 1903 for Nv 436.48 without a hitch (did the manual hex edit method). 7700k, 1080Ti. So far have only tried running Borderlands 3 (UE4). Only issue is that attempting to disable fullscreen optimizations causes the Nvidia red text to display.

Post by **schwing** » Wed Oct 16, 2019 7:18 pm

Thanks guys for your support!

@Losti: in 1903 with or without the fix, the stereo driver stereoizes graphics properly up until the final draw call. It's after that point [in Present()] where graphics are sent to the display that the fix is meant for. The fix replaces a line of code that 1903 skips that in 1803 stereoizes the final image before it's sent to the display. As for the root cause, I don't know yet. I just wanted to know if this fix works for people of differing 3D hardware before moving further. Ideally the final version of the fix would be something better than hex editing such as setting some new 1903 registry value or otherwise something simpler.

@DJ-RK: in the meantime there's a workaround to remove the red text. I forget how. I tried to reproduce this in other games as I don't have that one. No dice.

Post by **Losti** » Wed Oct 16, 2019 10:38 pm

Woow .... Ok as soon as i can i will Tests this. Thank you very much. Ill use the hex Methode

Post by **WickedScav** » Thu Oct 17, 2019 3:54 pm

Tried your fix with Draugen (normally crashes as soon as 3DV is activated on 1903 with the latest drivers and Losti's script) using option 1, now the game works perfectly with 3DV and 1903. If I get time, I will try more games I know crash without your fix.

2080 RTX with 436.48
i7-5820K CPU @ 4.30GHz

Thanks a lot for the fix. Hopefully I can get rid of my dualboot system soon

Post by **DJ-RK** » Thu Oct 17, 2019 4:01 pm

Ok, so here's a new development. iCUE, the software responsible for my Corsair mouse, has been unresponsive lately. Just checked my event viewer log and found the following error:

Faulting application name: iCUE.exe, version: 3.20.80.0, time stamp: 0x5d7908f3
Faulting module name: nvwgf2um.dll, version: 26.21.14.3648, time stamp: 0x5d8d4672
Exception code: 0xc0000005
Fault offset: 0x00175c66
Faulting process id: 0xc6c
Faulting application start time: 0x01d585356f65a85b
Faulting application path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\iCUE.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_827405c7c65146ab\nvwgf2um.dll
Report Id: ebd23fa9-582f-4bca-ad8b-95d535223aa1
Faulting package full name:
Faulting package-relative application ID:

So that's pretty crappy, and definitely a dealbreaker for me. Not sure why my video driver would cause an issue with my mouse software, but dem's the breaks. Back to 425.31 for me for now.

Post by **schwing** » Thu Oct 17, 2019 4:04 pm

I happen to use that application but haven't had it crash nor do I see any errors in my Event Viewer. Although I use it for watercooling, not my mouse. Either way, I'll add it to my to-do list.

Edit: I improved the 32-bit hex editing case so that it doesn't matter what driver you're on. This may improve the iCue case, but I'll need to reproduce it first to know.

Edit 2: It looks like the spot iCue had trouble with is the exact part I fixed in the previous edit. The problem should no longer occur.

Edit 3: I tested Shadow of the Tomb Raider and DX11 stereo works if Direct Mode is re-enabled by setting 0x70ccb5f0 to 0 using Nvidia Profile Inspector and exclusive fullscreen mode is enabled. DX12 stereo doesn't work yet.

Post by **WickedScav** » Fri Oct 18, 2019 1:09 am

Tried now Draugen and Layers of Fear 2 (both UE4) which used to crash without your fix, they do work now without any problem. SofTR also still works with the fix, as it used to do, after deleting the specific flag in the drivers (DX11 only of course).

But, after applying your second fix manually using a hex editor, I can't get any of the 3 games to start anymore, they all crash upon starting. The 3d vision driver panel 3d test still runs normally. Maybe I messed up with hex editor, I don't know, but reverting back to your zip file (initial fix), everythings runs again normally.

Maybe if you prepare a new zip file with the updated fix, I could try that one again...

UPDATE: Damn, I really think I messed up with the hex edit, I think I used an "8" instead of a "B". I will try again and report back as soon as I can.

UPDATE 2: I noticed that you changed also the 64-bit hex, even though you said in your last post that only the 32-bit code was changed? In any way, there is a difference in the 64-bit version between your zip and the hex code: "B8 00 00 00" vs "B0 90 90 90"

UPDATE 3: I indeed messed up with the hex edit. now everything works again with your new fix, sorry

Post by **schwing** » Fri Oct 18, 2019 2:20 am

For that extra improvement, I didn't mention it because it's just to replace the 00's with 90's to make them easier to read. I don't expect them to fail because of that change. However, thanks for reminding me, I've updated the DLL link. It's the same as the hex edit (the DLL's I'm using on my PC right now). Also, I usually copy-paste the bytes to avoid typos.

Post by **Skawen** » Sat Oct 19, 2019 5:43 am

Thank You very much for this fix, now Layers of fear 2 is working & green overlay is back

Post by **CeeJayII** » Sat Oct 19, 2019 10:33 am

Thanks for your effort, awesome work. As you mentioned, anti-cheat games do seem to be triggered with this. I have to move the two original Driverstore files back in order to play games with anti-cheat enabled, whether 3D is activiated or not. Regardless, it looks like you're really onto something here. It's probably a pipe dream to think Nvidia will notice your work and re-implement 3D Vision based on it, but one can hope.

Post by **schwing** » Sat Oct 19, 2019 4:17 pm

Good to know. I had conflicting conclusions talking to different people about whether they would trigger. I'll keep the warning there then. I didn't want to muck up the guide with extra methods, but one thing I do to make replacement/reversion faster is use LockHunter to unlock the DLL's. This can be done outside of Safe Mode, and usually Steam and a couple programs I don't use show up. Close or terminate the processes you see; I've never seen a critical system program use them. The trigger is from file consistency, so you should have no problems after reverting.

One more thing: you can use Task Manager, go to Details, right-click the columns to add Platform, and that will tell you what bitness the anti-cheat-based game is running at. Then just revert the 32-bit or 64-bit DLL that matches that bitness. So if none of your 3DV games are 32-bit, then you don't need to replace the 32-bit DLL in the first place.

Post by **Lundamyrstrollet** » Tue Oct 22, 2019 1:58 pm

Great find Schwing! Will test it at the coming WE...Very important for us to go further with 3D Vision, cant believe you find a Way with 1903 , incredible!!!

Post by **Blacksmith60** » Wed Oct 23, 2019 6:36 am

Thanks alot Schwing, really impressive and important find here!

I'm still on Win 7, but you def. makes the unavoidable big decission easier

Post by **Losti** » Wed Oct 23, 2019 12:37 pm

Lundamyrstrollet wrote:Great find Schwing! Will test it at the coming WE...Very important for us to go further with 3D Vision, cant believe you find a Way with 1903 , incredible!!!

DITO !!!

Post by **Darkbluesky** » Sat Oct 26, 2019 9:52 am

I tested this. With 440.97 I have some problems, it seems to work but BF1 sometimes (not all time) during gaming gives a DX11 error and crashes:

BF4 just starting gives always a DX11 error and crashed to desktop before showing the loading screen:

and BF5 shows the red message (Attempt to use stereoscopic mode in a…) and crashes to desktop on the loading screen.

Other games, as Ghost of a Tale, CodWaW and CodWWII (CMU mode), SW:BF run just fine.

I think it could be something related to 440.97 because it worked with the previous driver and your fix. I have a i7 9700K, GTX1060 6Gb, 32Gb DDR4, Win10 1903. I add here the BF4 d3d11_log file. The error in BF1 comes only sometimes.

Post by **schwing** » Sat Oct 26, 2019 1:07 pm

Darkbluesky wrote:I think it could be something related to 440.97 because it worked with the previous driver and your fix.

That sounds like a profile or driver issue. You don't get any of these errors with stereo disabled in the control panel? For BF1 and BF4, they can't be from game updates, because the latest update notes are too old from my research. I don't have any of these games to test these errors for myself.

For BF4, or maybe all of them, try adding allow_platform_update=1 under the [System] section in d3dx.ini. Remove it if it doesn't work.

Post by **Darkbluesky** » Sun Oct 27, 2019 4:40 am

I don't get them if stereo is disabled in control panel.

I'll test what you say and see if something changes. Thanks

Nevertheless I have installed 440.97 with 3DFixManager 1.73 from the 425.31 (using DDU before) and then edited the files, now in the 3d setup wizard, in the second screen, I get a message telling me I have not installed the 3D drivers (although in the first screen, at the very bottom, says otherwise…), so I can't even activate 3d in cp.

I have also tested Losti approach with the 440.97 and the previous driver version, but I get same problems, sometimes some games (BField ones) start at maximum refresh rate (which is not a 3d supported one, so it crahses or don't work, just as I reported for BF5). I don't use Losti method, because when it installs the last/new driver it FORCES me to restart (no 'restart later' option) just after the previous one (425.31) is desinstalled. So I have to restart Losti thing but this time without any driver installed (no 425.31 etc), so I guess it does not do what it should.

Post by **schwing** » Sun Oct 27, 2019 6:04 am

I never got any errors in the 3DV wizard. I DDU, install a graphics driver (usually an offline installer exe), then either install the 3DV driver from 3DFM either before or after the guide above. I don't use the Losti method but I provided it since I know people use it and might want to see it here.

Post by **Darkbluesky** » Sun Oct 27, 2019 11:03 am

The problem with the wizard were due to the usb port used for the emitter. Now is directly in the mobo ports and it is ok.

The problems (crashing) with BF games were due to NZXT CAM last update (4.0.12). Beta 4.0.11 was ok, but the last one causes problems with nvidia driver installation and BF games, specially in 3D.

Now I have a problem with nvidia cp's Preferred Refresh Rate, in BFV is fixed too high and if I changed 'Highest possible' to '3D application' then ingame it changes back to Highest possible' and if I am in 3D the game crashes (too high refresh for 3D)

Changing the global settings Preferred Refresh Rate to '3D application' AND BFV's too, it seems to set BFV stuck at 144Hz which is ok for 3D. But I can't change neither the resolution to other than 1920x1080 neither. Just in case I have uninstalled geforce experience, but nothing changes. It is very annoying!

Post by **schwing** » Sun Oct 27, 2019 4:56 pm

Such monitoring or reshade software like RTSS or Reshade can cause game startup issues when updated. 3Dmigoto has to support whatever these apps do in order for graphics to get through the pipeline properly. They may even cause issues in certain games without 3DM. So when troubleshooting, it's worth turning these things off temporarily.

There's a refresh_rate setting in d3dx.ini you can try; I've never used it. Geforce Experience is not part of my testing, so I don't know if people will have issues with it when following this guide. I'm not sure if it's a popular option.

Post by **typhoon** » Tue Oct 29, 2019 6:05 pm

i love you!!

working with 436.02 here

tested only Planet Alpha (dx11 migoto)

will report issues with other games (2d too)

Post by **Pauldusler** » Thu Oct 31, 2019 1:26 pm

Hi Schwing,

tested your fix with 441.08 and it solved issues with the green text overlay in 3D Vision mode (win 10 v.1903). Also Darksiders 3 (Unreal Engine 4) is not crashing any more.
Very good job on that fix! Couldn't test so far if this also solves our issue with HelixVision not properly running on 1903 as it rather was installed by accident on my girl friend's PC ^^.
There is still one issue left: Both on my PC (1809, 440.97) and on my girl friend's PC (1903, 441.97) 3D does not work any more for DX 9 games in windowed mode. This also means that the Nvidia 3D Vision viewer doesn't work in windowed mode any more. Do you have the same issue?

What are your next steps? Did you already have some success in simplifying the procedure with a registry key?
In theory with C# / 3DFM it should be possible to restart PC in safe mode, take ownerships and replace some hex values in the file. But I think people are rather frightened of safe mode and those steps even if they are automated. We would need a simplier solution.

Cheers!

Post by **schwing** » Thu Oct 31, 2019 3:42 pm

That's great news that it's working for you guys and I completely agree. You don't actually need safe mode. This guide is meant to be a manual approach until a proper solution is found. The alternative I use is a program like LockHunter to remove any file locks first. For instance, for the 32-bit file, I only need to close Steam and iCue.

I've held back to work on other things and wait for feedback. It seems to be mainly the red resolution overlay text, which I haven't seen at all. I use a passive 3DTV, and I also tried a 3D monitor which shows the same results as my TV. The photo viewer works fine, but the one DX9 game that shows 2D windowed is Resident Evil 4 HD, for which the fix is helixmod. Mirror's Edge is also one, but that one works fine.

Post by **Darkbluesky** » Fri Nov 01, 2019 7:19 am

Pauldusler wrote: ...
There is still one issue left: Both on my PC (1809, 440.97) and on my girl friend's PC (1903, 441.97) 3D does not work any more for DX 9 games in windowed mode. This also means that the Nvidia 3D Vision viewer doesn't work in windowed mode any more. Do you have the same issue?
...

I find this also with the 441.97 (not the 440.97), I installed new driver then I let 3DFM install the stereoscopic driver, but I was thinking that maybe this is not the same as 3DFM does when installs all the driver (not only the S3D part), so I was waiting for new 3DFM version which allows 441 (and not only 440) driver to be installed (Losti method is no valid for me as explained in other post in this topic).

Aside of that I find also that the NVCP 3D test is no more working with this driver: it launches but in 2D...

Post by **typhoon** » Sat Nov 02, 2019 3:23 am

tested games (all working):

Singularity
Fe
Assassin's creed III
Metal Gear Solid V: Ground Zeroes
Planet Alpha

I confirm windowed mode not working anywhere
Probably for this reason PotPlayer 3d mode doesn't works anymore
Strangely (and fortunately!!) Stereoscopic Player is back working without crashing (it has been unusable for years on my rig, very unstable), using latest version and the license from nvidia player.
I have to say that i use also SVP (smooth video project) on players so it's not a "standard" configuration, works fine now with stereoscopic player.

sometimes 3d doesn't kick in and i have to change to windowed and back to fullscreen
some other times it doesn't go to 120hz and i get the red message, to avoid this i've enabled 3d "always on" (using https://github.com/Eincrou/Adv3DVisionConfig/releases ) and make sure i'm already at 120hz before launching the game
in the past i had to create a custom resolution that works only at 120hz in order to force the game to launch with the correct refresh rate, can't remember the games

No issue with others software and/or other 2d/multiplayer games yet.
i'll edit this post if i find something

i'm still on 436.02 and i'm not going to change it until i'm forced because of bugs or games not working properly
gfx: RTX2080
cpu: i7 7700k on ASUS maximus VIII Ranger
display: ASUS PG278Q

Post by **RAGEdemon** » Sat Nov 02, 2019 7:52 am

NVidia have now added Sharpening filters directly into the NV control Panel (and Reshade into GeForce Experience).

https://www.nvidia.com/en-us/geforce/ne ... dy-driver/

As an avid fan of attempting to sharpen every game played, with Reshade, this is good news for me personally.

Certainly, nVidia's old freestyle filters only work in one eye. I hope the newly integrated into Control Panel filters work in both eyes.

I aim to test it over the next few weeks. Has anyone had a try at the new integrated Sharpening filters + 3DV and found that both eyes work?

Post by **Darkbluesky** » Sun Nov 03, 2019 6:17 am

Ok, finally 3DFM (v 1.73, 1.74 won't update drivers if in 1903), asked me to update to 441.08 (until yesterday it was 440.8). So I have let it update (I was using 425.31) and bingo! Now it works with the hex editing explained here, EVEN in windowed mode and EVEN the NV CP 3D Test (which did not work neither).

So for me this is really good news. I think really that what 3DFM does when updating driver is something more than just install the last drivers and add 3dvision one, as this lead to broken windowed mode and other problems.

I have tested then what RAGE asked, sharpening filter. It works in 3D ! But I have only tested in BF1 and the bad news is that it crashes 4 out of 8 attemps to play the game in 3D (in 2D it never crashes) if sharpening is activated. I have NZXT CAM not running, and tested with and without RTSS too.

EDIT: Aside of BF1 it also works with BF4, BFV, Ghost of a Tale, CODWWII (CMU Mode), CODWaW, SWBF. Tested also with NZXT CAM and RTSS (detection level set to None, otherwise it crashes with NZXT CAM) and the crash in BF1 is the same, so I guess they have nothing to do.

EDIT2: I have tested the new ReShade filters in Freestyle (following Nvidia directions given in link above) and they work only in one eye. Dunno if using ReShade directly will work in both eyes or not, though.

Post by **RAGEdemon** » Sun Nov 03, 2019 3:23 pm

Darkbluesky, thank you very much for testing; and the good news!

To answer some of your questions:

1.
NZXT CAM, both old and new versions, are generally considered to be garbage, not even counting their immoral data collection antics. There was even recent benchmarking done by a credited publication on its negative affects on performance:

https://www.youtube.com/watch?v=NzAeAFudylI

I have switched to an open source version of CAM, which is tiny, having virtually no resource footprint:

Liquid Ctl:
https://github.com/jonasmalacofilho/liquidctl

Autostart with windows with a batch file (e.g. put into your startup folder). My batch file is as follows:

Code: Select all

cd [path to your install folder]
liquidctl set pump speed  36 60  37 70  38 90  39 100
liquidctl set fan speed  36 40  37 60  38 90  39 100

2.
ReShade installed separately indeed always works in both eyes. The problem there is that it usually conflicts with community 3D Vision Fixes as they tend to use the same .dll file meaning you can't [usually] have both running at the same time.

3. Generally to everyone:

If not investigated already and if your system can handle it, I would HIGHLY recommend playing games with:

* 4x DSR + 0% blur option

combined with

*ReShade (or now nVidia's) sharpening options maxed out.

For ReShade, my favourite filters are:

*LumaSharpen + AdaptiveSharpen @100% strength.

The added detail to games is absolutely amazing.

===========
Thanks everyone!

Post by **Darkbluesky** » Mon Nov 04, 2019 1:19 am

Thanks a lot RAGEdemon, I did not know about Liquid Ctl. Just for info, I was also concerned about their data collection, but in new version (still beta) they allow you to disable it and I have verified with TCP/IP monitor software: with previous versions there was a lot of connections back to NZXT, now there is not a single one if you disable the data collection option. Regarding performance, I guess is not the best one, yep, but still they have improved it somewhat.

Thanks a lot for your input and experience on ReShade and with sharpening, I'll test it! A pitty that they use same dll and that the Nvidia implementation does not work for 3D...

Regarding this hack in this topic, for me it seems I must install drivers through 3DFM otherwise it works but with problems.

Post by **schwing** » Mon Nov 04, 2019 2:33 am

I only use 3D Fix Manager for 3DV driver installation. The Losti method is there for people who prefer that one.

Post by **cyrilp** » Mon Nov 04, 2019 4:38 pm

i have done both option: copy your dll (with 441.08) / edit hex (with 441.08 & 441.12) but everytime i try to start the 3d setup wizard i'm told my driver is not compatible with 3D vision

Post by **schwing** » Mon Nov 04, 2019 6:03 pm

Maybe it's a DCH type of graphics driver you're using. You could ask here and see if Pauldusler knows about this error. Or try installing the 3DV driver before going through the guide. If you get the error then, that means the hex edit or replacement isn't the problem.