What about https://www.computerbase.de/downloads/s ... -runtimes/ ?
![Wink ;)](./images/smilies/icon_e_wink.gif)
Why are we talking about SLI?! I never mentioned SLI. This one on GPU alone.AlexTOPMAN wrote: ↑Wed Sep 30, 2020 2:05 pmThe problem is - only few games can scale with 2x performance. Often, games have no support SLI at all. I mean, new 3Ds SLI can work in any case, because doubling data happens only at CPU to GPU transfer point. CPU+GPU natively balanced games (optimized by developers) have more chance to double fps in 3Ds SLI.
Here are the instructions (sorry, that in Russian): https://forums.overclockers.ru/viewtopi ... #p17065337
Sorry for that bad build, I don't typically ship debug builds.TonyMontana wrote: ↑Wed Sep 30, 2020 11:08 amThank you for explaining this. But even with VS2013 installed it still crashes, so I would be grateful for a recompiled version. In the meantime, I will do the testing with DX 10/11 games.
I have also found a resource I would like to share with you. It explains the process of DLL redirection and may be useful for our purposes:
https://www.exploit-db.com/docs/english ... ection.pdf
Thank you very much! I'd have wished not to say this again, but unfortunately the new build is still crashing for me on 2 different machines both properly set up as instructed. Also tried different versions of nvwgf2umx.dll. I should note that both are running AMD CPUs. Here is what the d3d11_log.txt reads:
Because, as we now have found out together, only the previous versions of nvwgf2umx.dll contain the stereo activation code required to activate NvSCPAPI.dll and NvSCPAPI64.dll.
your 3080 won't work with the old drivers that allow 3D Vision. And 3D Vision won't work with the new driver required by 3080.njbrodeur87 wrote: ↑Fri Oct 02, 2020 7:50 pm Just wanted to confirm from others in this thread that I understand this. Even if I have a separate windows partition with the latest 3dfix manager compatible driver on my current pc that works great with the 1080ti, if I upgrade to a 3080, even if I don't upgrade those said drivers I had, it still won't work? My plans were always to have a current os with updated drivers from nvidia, and then keep using the 3dfix manager compatible driver on my separate windows copy for just 3d and not update those drivers that were working and use a 3080 with it.
Ugh if the above doesn't work I may have to make a separate brand new pc for just 3d games only and spec with with a 2080 instead but hopefully I don't have to.
Thanks everyone
Super great experiments there, very helpful and great information.TonyMontana wrote: ↑Fri Oct 02, 2020 12:41 pmBecause, as we now have found out together, only the previous versions of nvwgf2umx.dll contain the stereo activation code required to activate NvSCPAPI.dll and NvSCPAPI64.dll.
So theoretically it should be possible to make the new driver have both versions of nvwgf2umx.dll at the same time - the new 456.38 one for regular, "non-stereo" calls - the second one from the previous driver 452 just for stereo calls.
Following this approach, I was able to make redirections on 456.38 from nvd3dum.dll --> NvSCPAPI.dll --> abcdefg.dll (previous, but renamed version of nvd3dum.dll) for testing purposes and it worked like a charm (using IDA Pro to manipulate calls coming from NvSCPAPI.dll).
When I then deleted the abcdefg.dll (while at the same time having the nvd3dum.dll still in the folder), the game still worked normally but without 3DV. Pasting the abcdefg.dll in again, stereo kicked back in. Deleting it again, stereo was off again. This proves it is possible to make redirections from NvSCPAPI.dll --> abcdefg.dll
This clearly only worked because on 456.38, nvd3dum.dll still contains the stereo activation code whereas nvwgf2umx.dll does not, as bo3bber already told us before.
But luckily, this is not true for nvapi64.dll (As far as we have found out yet).
So IMHO, stereo activation with DX11 will work, if (and thats a big if) we will be able to redirect the stereo activation calls (and only them) from the highest instance (this should be nvapi64.dll? ) to a previous nvwgf2umx.dll while at the same time leave the "non-stereo"-calls to go to the current nvwgf2umx.dll.
Is this route correct?:
usual, non-stereo calls: nvapi64.dll ? --> 456.38 nvwgf2umx.dll
stereo-calls only: nvapi64.dll ? --> 452.06 nvwgf2umx.dll --> NvSCPAPI64.dll --> 452.06 nvwgf2umx.dll (or is it the other way around, I am not sure yet)
Question: What file(s) make the call to NvSCPAPI.dll and NvSCPAPI64.dll other than nvd3dum(x).dll and nvwgf2um(x).dll?
I would like to point out that I am not an software engineer, but I will give my best to help you to solve this issue. If you have any documentation on the nvidia Stereo API available, I would be grateful if you could share it with me.
Also, if I am wrong with any of the above, please correct me. These are only theoretical assumptions based on the research I did so far.
Its useless to hope that any driver out there later 452.X will have the driver calls back in it ^^ Why should they do this? the branch later 452 will NOT HAVE IT ANYMORE in the DX11 driver file. Its useless to try hotfixes, beta drivers, wuattro or whatever is later than 452. But if you want to have a look, get the driver. Open the exe in winrar/7zip, extract the nvwgf2umx.dl_ in the Display.Driver folder to where ever you want, open windows command line (cmd.exe), move to the folder you have extracted the nvwgf2umx.dl_, type in expand nvwgf2umx.dl_ nvwgf2umx.dll, open nvwgf2umx.dll in a hex editor, search for the string "vision". If you cant find any thing that is called 3DVISION or 3D VISION, the stereo calls are not present.
Yeah, for now, at least until the experts figure out how to hack the drivers.njbrodeur87 wrote: ↑Fri Oct 02, 2020 10:18 pm Ugh dammit gonna have to build a new 3d build just for 3d games then in the near future as I have a 3080 coming to me in next couple weeks
Lizzard, when using TriDef with an Nvidia card, are you limited to 720p 60htz and 1080p 24Htz as well for those who are using 3DTV and a full 1080p 3D projector? My projector can only do 120htz on 1280 x 720p? I have TriDef version 7.4 on my PC, and with my previous AMD card I could do 1080p. I want to get used to using 3V vision before I start messing around with using tridef an my invidia card.Lizzard wrote: ↑Thu Oct 01, 2020 3:32 pm Please don't neglect these guys at DDD - Dynamic Digital Depth. I'm looking more seriously to find contact details. But I think it might be right underneath our noses. Neil seems to have contact with Chris Yewdall, CEO of Dynamic Digital Depth (former I suppose). I still use Tridef Ignition 6.7 on Windows 10 - 1903 with zero problems. At least the games that are listed still loads and works perfect in VR SBS. There are a few that have had updates since this was released, like StarCraft2 and Command & Conquer 3, that have trouble. Their fixes also adapted a "Universal" structure where some effects are broken like reflections. It also works independent of the 3d Vision driver. And in some cases it works better than Helix's wrapper or 3dMigoto. This code full of potential is just rusting out there somewhere.
Some of the most exciting news of its time:
https://www.youtube.com/watch?v=lSnLz_jIEqc
I know; when I found out, I spent my 3000 series money on a Titan RTX that someone was panic selling cheap. At this point my gaming P.C. is basically a dedicated 3D rig.njbrodeur87 wrote: ↑Fri Oct 02, 2020 10:18 pm Ugh dammit gonna have to build a new 3d build just for 3d games then in the near future as I have a 3080 coming to me in next couple weeks
Let there be magic...
With Tridef you could use up to 4K DSR with your nVidia GPU on a projector at 60Htz. You dont activate 3d vision and also no 3d vision fix. There is a small difference with 2k DSR and 4K DSR on a projector screen. 4k DSR on a native 1080p projector is a bit overkill. Only in Virtual Reality do you notice a plausible difference. I've been playing some games like this for a while now(VR) and it certainly softens the screendoor effect. But Im having serious sync issues. Dont know if there are too many hoops. DSR is a good alternative to Anti Aliasing without serious performance penalties. AA has a blurry effect on picture quality with a significant hit in performance when it gets to 1440p (2k) and higher.narhicfd wrote: ↑Sat Oct 03, 2020 5:00 pm Lizzard, when using TriDef with an Nvidia card, are you limited to 720p 60htz and 1080p 24Htz as well for those who are using 3DTV and a full 1080p 3D projector? My projector can only do 120htz on 1280 x 720p? I have TriDef version 7.4 on my PC, and with my previous AMD card I could do 1080p. I want to get used to using 3V vision before I start messing around with using tridef an my invidia card.
Also, for what reason would using prefer using TriDef over 3D vision?
Brilliant! This sounds really promising. I am absolutely available to host it open-source, closed source, however they would like to see it. If they have no preference, adding it to either my github or DarkStarSword's would be amazing.RAGEdemon wrote: ↑Tue Oct 06, 2020 4:49 pm Gentlemen, Vadim has kindly set up a group chat with 3 of the iZ3D team and asked them to provide the iZ3D driver source code. I am sure we will have many questions also.
I have asked DSS to join the group, and sent a message to Helifax, however I do not have fast contact for bo3b. Bo3b, as much as it might pain you, would you kindly sign up to the ol' Facebook and friend
===============
11:20 PM
Vadim created the group.
Hi, guys! You may remember Shahzad - one of iZ3D most active customer. They have a community working on 3D gaming, but looks like nVidia dropped their 3D driver support. So, iZ3D driver is their only chance. Is there a way to share the source code with them? Or I can try to do it if you will give me an instructions.
Of course we will lose all DX11 3D fixes. 6 years will be more or less wiped on RTX 3080 and all future graphics cards. The required shader hacks will be totally different on the iz3d driver if we will get the driver at all / make the driver work properly.
Thank you for your response! Using a 3Dmigoto to inject the dlls sounds really good, have you tried this yet?bo3bber wrote: ↑Fri Oct 02, 2020 10:30 pm
The fact that you can call through to a different driver version is extremely helpful to know.
That fundamental idea of rerouting only the stereo calls is good I think, and your test there suggests it might work. We know the stereo code hasn't changed at all in years, and was still working. The only real question is whether they somehow broke how the stereo calls would interface with the driver itself.
I'm fairly certain I can build a 3Dmigoto that will reroute these calls to a different driver. I've already done a pre-loader for the Schwing hack to make it work on a per-game basis by force loading the hacked nvwgf2umx.dll into a given game. It's not much of stretch to reroute those stereo calls into a different, older, version of that file.
Code: Select all
calls calls calls
nvapi.dll --> nvd3dum.dll --> nvwgf2um.dll --> NvSCPAPI.dll --> enables 3DV
|
|
here the chain brakes in 456, therefore NvSCPAPI.dll will not be called
I don't know what this event means to us, but I hope it is what we were all hoping for to some degree...Hi, this what I found <link>
But I removed madCodeHook library (http://madshi.net/) from it, because we can't distribute their source code. You can rewrite part of code that use it to something like EasyHook https://easyhook.github.io/