Meant to be Seen

Marin3D wrote: ↑Tue Sep 29, 2020 11:30 amor install the MSVC 2013 redistributables download from...

AlexTOPMAN wrote: ↑Wed Sep 30, 2020 2:05 pm

helifax wrote: ↑Tue Sep 29, 2020 1:50 amSo rendering 120FPS in 2D will give you 60 FPS in 3D...

The 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.

RAGEdemon wrote: ↑Sat Sep 26, 2020 1:51 pmI remember modifying inf/ini files to soft-mod my GTX into Quadro for professional applications...

Here are the instructions (sorry, that in Russian): https://forums.overclockers.ru/viewtopi ... #p17065337

TonyMontana wrote: ↑Wed Sep 30, 2020 11:08 am

helifax wrote: ↑Tue Sep 29, 2020 3:27 pm I am sure Bo3b can address this very quickly though as he knows exactly what to do and well.. to debug it -------- obviously you need Visual Studio installed anyway!

Thank 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

bo3bber wrote: ↑Thu Oct 01, 2020 1:05 am
New version is on server with the D version of the file. Works on my alternate machine, so hopefully works for you too. Same link.

Losti wrote: ↑Fri Oct 02, 2020 7:52 am Whats the use of the new driver if we redirect it to the old driver dll???

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

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.

harisukro wrote: ↑Fri Oct 02, 2020 11:58 am Did everyone tested the new hotfix 456.71 ? cause has a different branch [r456_61-6] vs old 456.55 - [r456_26-15]

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 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

Necropants wrote: ↑Mon Oct 05, 2020 6:53 am I thought Tridef is fake z-buffer 3D only?

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

bo3bber wrote: ↑Mon Sep 28, 2020 5:12 pm
5) iz3D somehow magically agrees to give us their code

That seems like a reasonable list, I tweaked.

Let there be magic...

iZ3D code...
Dear Vadim,

You won't remember me, however I was one of your first customers of the iZ3D monitor. It has always been one of my favourite 3D products and I was extremely saddened to hear that iZ3D was no longer going to be active.

It might surprise you to know that there is a dedicated Stereo3D community still active, both via forums and discord - we have fixed hundreds of games:

https://helixmod.blogspot.com/2013/10/g ... dated.html

We have developed our own tools to hack/wrap/inject into e.g. nVidia's old 3DVision driver to allow us to fix the broken effects in games, and are currently in the process of writing a Vulkan driver.

Unfortunately, the last bastion of 3D lovers - nVidia's 3DVision driver - has recently been discontinued.

As a community, we are quite desperate to keep 3D gaming alive - our developers have spend countless years coding towards making that happen, for example here:

https://github.com/bo3b/3Dmigoto/releases

Now, we are at an unfortunate impasse, as there is no place for us to turn to...

We would like to ask you if you know what happened to the iZ3D driver code?

We know that iZ3D has always been the best 3D driver, and we would love it if we could get our hands on it in some manner. We don't care if that way is open source, closed source, the code is messy / without any comments / incomplete etc - our talented and dedicated engineers will work it out.

If you don't mind me saying, the code likely has little value nowadays, however we could revive it into something quite special

I hope you might kindly consider this request; it would mean the world to a lot of people.

Kind regards,
-- Shahzad Ali
Cambridge.

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?

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.

ZePRiNCE wrote: ↑Thu Oct 08, 2020 1:27 pm - regarding iz3D, are we gonna "loose" all existing 3D fixes ?

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.

   
     
         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 

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/

Shahzad:
Got it - Amazing!
Our community developers will likely have questions. Would you mind terribly if they contacted you?
Perhaps you would kindly suggest a preferred communication method you might consider good for you?

iZ3D team:
I can try to answer some small questions. But unfortunately, I won't have much time in the near future. You can write to me here or on Github if you will develop there.

Shahzad:
Gentlemen, Thank you once again; we are forever in your debt. We shall be very careful to not burden you - I think our devs will prefer Github too.
I shall pass along the kind message

My nickname there <xxx>, you can just mention me in issues/discussions

Vadim:
Good 3D luck!!!