Vk3DVision - A Vulkan 3D Vision Driver

[Lysander]

Awesome! No problem!
Hopefully everything will work just fine! Please, if you could let me know, it would be awesome ^_^ :

Yes, that was it! I kinda wish I waited with Doom because with this fix I don't have the slight issues on the left/right screen edges and I got a new CPU since then so now everything runs super-smooth at constant 60fps in glorious 3D Maybe a replay, hmmm Will definitely be amazing with Doom:E once I get to it!

Detroit demo ran a bit slower and had a few shader issues but perhaps it's because it's the demo - I'll likely get to the game in the future. Does the full game have more AA options? It was very prominent in the demo.

Thank you so much, really exciting to have a whole new slate of games with 3D potential - I hope many more use the Vulkan API in the future

[Lysander]

oh, btw, this should be front page news on the Helixmod blogsite! We have a Doom:Eternal 3D fix!

[skyrimer]

1. Did you change the renderer to Vulkan in Graphics/Advanced?
2. The Crosshair value is in the ini file and you can adjusted from the game (F10, change the ini file, reload the ini file - use the shortcut and adjust it to your liking).
3. No problem here with that on any of my systems. Not sure why you see that.

1. Yeah, when I boot normally i get the red warning 3d message, I can then go to config advanced options and see vulkan set as renderer, get in game and warning still there, eyes reversed. Boot directly with vulkan exe, everything works fine. Both exes are set as administrator.
2. That did the trick, I set crosshair value to 0.25, now incresing the convergence didn't break it so i got fantastic 3d, this game looks phenomenal with 3d and ultra settings (other than the stuff mentioned on the readme)
3. It happens every time, as soon as I try to quit, black screen. Not much of an issue though.

I sent a few euros, had to be grateful for this fantastic fix.

[helifax]

1. Did you change the renderer to Vulkan in Graphics/Advanced?
2. The Crosshair value is in the ini file and you can adjusted from the game (F10, change the ini file, reload the ini file - use the shortcut and adjust it to your liking).
3. No problem here with that on any of my systems. Not sure why you see that.

1. Yeah, when I boot normally i get the red warning 3d message, I can then go to config advanced options and see vulkan set as renderer, get in game and warning still there, eyes reversed. Boot directly with vulkan exe, everything works fine. Both exes are set as administrator.
2. That did the trick, I set crosshair value to 0.25, now incresing the convergence didn't break it so i got fantastic 3d, this game looks phenomenal with 3d and ultra settings (other than the stuff mentioned on the readme)
3. It happens every time, as soon as I try to quit, black screen. Not much of an issue though.

I sent a few euros, had to be grateful for this fantastic fix.

The red message and the eyes flipped sounds like some sort of 3D Vision bug....

[Losti]

Hi,

THE BAD NEWS is that 3D Vision stopped working with the RTX 3080 Release Driver (even on older hardware like the RTX 2000 series). This means the VK3D Vision will not work with Nvidia 3D Vision Monitors & Glasses WITH anything newer than last known driver to work - 452.06 when using DirectX 11. This is because, I need the 3D Vision driver to display on a 3D Vision monitor + emitter + glasses... obviously
I believe there will be some investigation into trying to see if it can be made to work with the latest driver or if the support is still there, or what is the case. (I am not part of that and not looking into it... so, don't ask me )
A lot of things got broken in this driver, including CMU seems to not find the patterns to address CM.

THE GOOD NEWS is the I DON'T care about 3D Vision when Vk3DVision works in Side-by-side/Top-Under modes or Virtual Reality (via HelixVision) And Vk3DVision works perfectly fine on the RTX 3080 driver in these modes (mmostlly because is not something controlled by Nvidia ^_^)
Also, since DX9 still works with 3D Vision, potentially I could use a DX9 interface to interface with 3D Vision (there are some caveats here, but it's on the table), So, in case of Vk3DVision, Nvidia 3D Vision is not fully lost. My OGL3DVision wrapper works fine and it uses DirectX 9 to interface with 3D Vision.

I wanted to share in case people want to go and buy (if you can) a new RTX 3080 card and also want to use 3D Vision.

So, the bad news and the good news are up to you to interpret, I guess
I'll have more news in the following days hopefully! This week was pretty slow for me since I am also undergoing some home renovations and when I am not working I need to deal with those

Cheers,
Helifax

Heli, some simple question from here:

Does this mean, using HelixVision, also for NOT Vulkan games, and the SBS mode, means using a VR-headset, we do not have to care about the not working 3D-Vision with the latest driver??

[helifax]

Hi,

THE BAD NEWS is that 3D Vision stopped working with the RTX 3080 Release Driver (even on older hardware like the RTX 2000 series). This means the VK3D Vision will not work with Nvidia 3D Vision Monitors & Glasses WITH anything newer than last known driver to work - 452.06 when using DirectX 11. This is because, I need the 3D Vision driver to display on a 3D Vision monitor + emitter + glasses... obviously
I believe there will be some investigation into trying to see if it can be made to work with the latest driver or if the support is still there, or what is the case. (I am not part of that and not looking into it... so, don't ask me )
A lot of things got broken in this driver, including CMU seems to not find the patterns to address CM.

THE GOOD NEWS is the I DON'T care about 3D Vision when Vk3DVision works in Side-by-side/Top-Under modes or Virtual Reality (via HelixVision) And Vk3DVision works perfectly fine on the RTX 3080 driver in these modes (mmostlly because is not something controlled by Nvidia ^_^)
Also, since DX9 still works with 3D Vision, potentially I could use a DX9 interface to interface with 3D Vision (there are some caveats here, but it's on the table), So, in case of Vk3DVision, Nvidia 3D Vision is not fully lost. My OGL3DVision wrapper works fine and it uses DirectX 9 to interface with 3D Vision.

I wanted to share in case people want to go and buy (if you can) a new RTX 3080 card and also want to use 3D Vision.

So, the bad news and the good news are up to you to interpret, I guess
I'll have more news in the following days hopefully! This week was pretty slow for me since I am also undergoing some home renovations and when I am not working I need to deal with those

Cheers,
Helifax

Heli, some simple question from here:

Does this mean, using HelixVision, also for NOT Vulkan games, and the SBS mode, means using a VR-headset, we do not have to care about the not working 3D-Vision with the latest driver??

Yes, that is correct. For SBS and VR via HelixVision, VK3DVision works without the need for the Nvidia 3D Vision driver

[Losti]

NICE, so i have ordered a GTX 1080ti OC for low price today to use the new HP REVERB2 at the end of october so i:

1. have a VR image quality i can live with and acceptable motion tracking and comfort
2. do not have to care missing 3D vision support if this isnt solved here in the comunity
3. i can use HELIX VISION and get max imersion in 3D gaming

OK fixing 3D games with a VR headset would be stupid, but earlier drivers still work so i will build up a 3D-fxi windows setup ^^

THANK YOU for this information!

[helifax]

NICE, so i have ordered a GTX 1080ti OC for low price today to use the new HP REVERB2 at the end of october so i:

1. have a VR image quality i can live with and acceptable motion tracking and comfort
2. do not have to care missing 3D vision support if this isnt solved here in the comunity
3. i can use HELIX VISION and get max imersion in 3D gaming

OK fixing 3D games with a VR headset would be stupid, but earlier drivers still work so i will build up a 3D-fxi windows setup ^^

THANK YOU for this information!

Yeah! That's what I do I even got a bit used to do it in VR as well ) Not as easy obviously, because I keep pressing wrong keys on the keyboard, but doable )
No problem!

[Losti]

Yeah i need my laptop for 3D fixing, fixing shaders via network and just press f10 at my desktop pc. A bit difficult with a VR headset i am curiouse how the proverb G2 Image will look like. I cant wait but i have to wait because purchease a proverb g1 die only about a month is nonsens.

I am sure my will to play will be much higher with the new hardware than.

[Lysander]

Heli, some simple question from here:

Does this mean, using HelixVision, also for NOT Vulkan games, and the SBS mode, means using a VR-headset, we do not have to care about the not working 3D-Vision with the latest driver??

I think you guys misunderstood each other, sounds like Helifax is saying you don't need the 3D-Vision driver ONLY for Vulkan games (via Vk3DVision). Which makes sense, as it's a Vulkan wrapper.

[helifax]

Heli, some simple question from here:

Does this mean, using HelixVision, also for NOT Vulkan games, and the SBS mode, means using a VR-headset, we do not have to care about the not working 3D-Vision with the latest driver??

I think you guys misunderstood each other, sounds like Helifax is saying you don't need the 3D-Vision driver ONLY for Vulkan games (via Vk3DVision). Which makes sense, as it's a Vulkan wrapper.

Yes, that is correct!
Let me write it in a clearer way to avoid any confusion
Nvidia 3DVision driver is required for 3D VISION Monitors & glasses! (This should be obvious )
Nvidia 3DVision driver is NOT required for Monitors/TVs that Support Stereo in Side-by-Side or Top/Under format.
Nvidia 3DVision driver is NOT required for Virtual Reality using HelixVision.

For DX11 games using 3DMigoto, you still require the 3D Vision Driver, obviously And HelixVision still requires it

Cheers,
Helifax

[Losti]

Argh ok Thanks for clearify.

[floph]

Tomorrow we have yet another fast paced game, Doom style, just not in hell - Serious Sam 4, and it's Vulkan, according to media. What do you guys think ? Would it be a good candidate for a 3D fix through Vk3DVision ?

[masterotaku]

Tomorrow we have yet another fast paced game, Doom style, just not in hell - Serious Sam 4, and it's Vulkan, according to media. What do you guy think ? Would it be a good candidate for a 3D fix through Vk3DVision ?

https://www.guru3d.com/news-story/serio ... ments.html
"The game will also require 40GB of free hard-disk space, and will support DX11, DX12 and Vulkan."

It will be fun to compare performance between DX11 and Vulkan in 3D. I'll get and fix the game someday (if no one fixes it before), but I'm not in a rush. Probably on a good sale.

[helifax]

Tomorrow we have yet another fast paced game, Doom style, just not in hell - Serious Sam 4, and it's Vulkan, according to media. What do you guy think ? Would it be a good candidate for a 3D fix through Vk3DVision ?

https://www.guru3d.com/news-story/serio ... ments.html
"The game will also require 40GB of free hard-disk space, and will support DX11, DX12 and Vulkan."

It will be fun to compare performance between DX11 and Vulkan in 3D. I'll get and fix the game someday (if no one fixes it before), but I'm not in a rush. Probably on a good sale.

It's easy... Vulkan wins by a mile Vulkan always wins over DX 12 not to speak DX 11... (unless they really botched the renderer )

[for3donly]

just noticed the stats of this thread, 17K views and >650 posts, among the rare top most popular thread. i'm glad that's so.

[Chtiblue]

2. The Crosshair value is in the ini file and you can adjusted from the game (F10, change the ini file, reload the ini file - use the shortcut and adjust it to your liking).

2. That did the trick, I set crosshair value to 0.25, now incresing the convergence didn't break it so i got fantastic 3d, this game looks phenomenal with 3d and ultra settings (other than the stuff mentioned on the readme)

Where is the crosshair value in the ini file? I don't find it

[Lysander]

Where is the crosshair value in the ini file? I don't find it

I think it's this piece:

[Key5]
Key = 0x4B ; K key ; Crosshair at depth
Type = toggle
y = 0.65 <--------------------------------- THIS ----------------------------

(original key is set to middle-mouse button (which - OBVIOUSLY - should be reserved for grenades ), I reset mine to K)

[Chtiblue]

I don't understand, I don't have this Key on the Vk3DVision.ini in the Doom Eternal fix (last update from 20th September). I only have 3 Key presets in the vk3D.ini...
Anyway, thanks I'll copy this to the ini.

[Lysander]

oh! ops, I was talking about Doom 2016

[RAGEdemon]

Both Doom's are fixed too?

This is insane!

HELLifax, you're 3DVision's true [fallen] angel!

[Necropants]

Tested out doom eternal last night and felt compelled to thank and congratulate Helifax personally. But just chiming in here.
Maxed fps in 3Dvision on Ultra Nightmare. (just reflections on low.) 1440p needs Crosshair much further in depth, (i'm using 0.9) but I am absolutely blown away by the performance on my machine which is getting long in the tooth at this point despite 2080ti (game says 120fps)

Absolutely Incredible.

[BazzaLB]

Tested out doom eternal last night and felt compelled to thank and congratulate Helifax personally. But just chiming in here.
Maxed fps in 3Dvision on Ultra Nightmare. (just reflections on low.) 1440p needs Crosshair much further in depth, (i'm using 9.0) but I am absolutely blown away by the performance on my machine which is getting long in the tooth at this point.
(game says 120fps)

Absolutely Incredible.

Yes, I played Doom16 and the performance is stellar. I am admittedly using SBS 1920x1080 (960x1080 per eye) on a 3dTV without enabling 3DVision at all but it runs so smooth and none of the eye sync issues of the OGL wrapper. Its absolutely fantastic achievement.

[john105]

Thanks a lot for all your efforts, Helifax! I tried it with Detroit Become Human Demo, but unfortunately it didn't work for me. I followed all readme instructions. When I start DetroitBecomeHuman.exe (as admin of course) with Vk3DVision.exe running, the game process terminates after running for less than a second.

I attached the dumps and the log. The log says "Cannot update the existing profile" like Lysander also mentioned. Not sure why. If I delete the profile, the message changes to

22:19:55:996 [04764] | INFO | Created NVIDIA Profile: detroitbecomehuman.exe-Vk3DVision
22:19:56:048 [04764] | WARN | Could not generate profile for detroitbecomehuman.exe application! 3D Vision will be disabled...

but everything else is the same.

I have Core i9-9900KS, 32 GB RAM, GTX 1080Ti, Win 7, 452.06+BringBack3DV. Maybe Vk3DVision doesn't work on Windows 7? Unfortunately I don't have Doom to try.

[helifax]

Thanks a lot for all your efforts, Helifax! I tried it with Detroit Become Human Demo, but unfortunately it didn't work for me. I followed all readme instructions. When I start DetroitBecomeHuman.exe (as admin of course) with Vk3DVision.exe running, the game process terminates after running for less than a second.

I attached the dumps and the log. The log says "Cannot update the existing profile" like Lysander also mentioned. Not sure why. If I delete the profile, the message changes to

22:19:55:996 [04764] | INFO | Created NVIDIA Profile: detroitbecomehuman.exe-Vk3DVision
22:19:56:048 [04764] | WARN | Could not generate profile for detroitbecomehuman.exe application! 3D Vision will be disabled...

but everything else is the same.

I have Core i9-9900KS, 32 GB RAM, GTX 1080Ti, Win 7, 452.06+BringBack3DV. Maybe Vk3DVision doesn't work on Windows 7? Unfortunately I don't have Doom to try.

Yes.. Unfortunately Windows 7 is not supported (went EOL in January 2020). Only Windows 10 is supported at the moment. (I didn't even try it on Windows 7).
The warning about the Nvidia profile can be ignored. I will probably completely remove the Profile writer from Vk3DVision as it is not required anymore.

I have made a new version (1.0.2) for all the fixes where I addressed a small bug in the DescriptorSets Layout and updated all the fixes. This will probably not fix it under Windows 7, but I would appreciate it if you can try it again and send me the dmp file.
Perhaps there is something I can fix for Windows 7. (I don't have any PC capable of running Windows 7 anymore - due to missing drivers).
I have updated all the game fixes to use Vk3DVision 1.0.2.

Cheers,
Helifax

[john105]

I have made a new version (1.0.2) for all the fixes where I addressed a small bug in the DescriptorSets Layout and updated all the fixes. This will probably not fix it under Windows 7, but I would appreciate it if you can try it again and send me the dmp file.

Sure, I'll definitely test it and report back.

Perhaps there is something I can fix for Windows 7. (I don't have any PC capable of running Windows 7 anymore - due to missing drivers).

Actually I built a new PC recently. Installing Windows 7 and finding drivers was relatively easy (with some research), even though my CPU was released just in November 2019, only 2 months before the EOL. I tried 2 motherboards, one with the Z370 and another with the Z390 chipset, and both worked. I had to use a moded USB3 driver for Z390 though. But AMD might be a different story.

Anyway, asking you to install Windows 7 would be asking too much if you don't really need it. But I'll still test new versions of Vk3DVision just in case.

[helifax]

I have made a new version (1.0.2) for all the fixes where I addressed a small bug in the DescriptorSets Layout and updated all the fixes. This will probably not fix it under Windows 7, but I would appreciate it if you can try it again and send me the dmp file.

Sure, I'll definitely test it and report back.

Perhaps there is something I can fix for Windows 7. (I don't have any PC capable of running Windows 7 anymore - due to missing drivers).

Actually I built a new PC recently. Installing Windows 7 and finding drivers was relatively easy (with some research), even though my CPU was released just in November 2019, only 2 months before the EOL. I tried 2 motherboards, one with the Z370 and another with the Z390 chipset, and both worked. I had to use a moded USB3 driver for Z390 though. But AMD might be a different story.

Anyway, asking you to install Windows 7 would be asking too much if you don't really need it. But I'll still test new versions of Vk3DVision just in case.

I am using the Z390 and unfortunately all the USB moded drivers that I tried don't really work correctly. (I had lots of issues with the sleep mode of the PC or sleep mode of different USB devices) and it was more of a pain that I would have liked.
So, I removed Win7 from the list of OSes that I care about

[john105]

I am using the Z390 and unfortunately all the USB moded drivers that I tried don't really work correctly. (I had lots of issues with the sleep mode of the PC or sleep mode of different USB devices) and it was more of a pain that I would have liked.

This driver worked fine for me easyupload.io/l62rx6 I initially downloaded it from https://www.win-raid.com/t4883f52-Solut ... stems.html , but now that page says "Due to the reason of non resistance, all Intel related mod drivers will be removed from the shelf." whatever that means

I've tried Vk3DVision 1.0.2 with the same result. The dmp files are attached.

[john105]

double post

[helifax]

I am using the Z390 and unfortunately all the USB moded drivers that I tried don't really work correctly. (I had lots of issues with the sleep mode of the PC or sleep mode of different USB devices) and it was more of a pain that I would have liked.

This driver worked fine for me easyupload.io/l62rx6 I initially downloaded it from https://www.win-raid.com/t4883f52-Solut ... stems.html , but now that page says "Due to the reason of non resistance, all Intel related mod drivers will be removed from the shelf." whatever that means

I've tried Vk3DVision 1.0.2 with the same result. The dmp files are attached.

Thanks for the dump.

Yes, Windows 7 is not supported and unfortunately will never be.
The crash that you are experiencing is in this line:

Code: Select all

IDXGIFactory2 *dxgiFactory2 = nullptr;
        HRESULT hr = _dx_device[device]._factory1->QueryInterface(__uuidof(IDXGIFactory2), reinterpret_cast<void **>(&dxgiFactory2));
        if(dxgiFactory2)

There is no DXGIFactory2 support on Windows 7 as DXGI 1.1 is not fully implemented, let alone DXGI 1.2.
DirectX 11 on Windows 7 doesn't have the full capabilities set that I require.

So, Windows 10 only apparently.
Thank you for the report and testin!

Cheers,
Helifax

[john105]

Yes, Windows 7 is not supported and unfortunately will never be.
The crash that you are experiencing is in this line:

Code: Select all

IDXGIFactory2 *dxgiFactory2 = nullptr;
        HRESULT hr = _dx_device[device]._factory1->QueryInterface(__uuidof(IDXGIFactory2), reinterpret_cast<void **>(&dxgiFactory2));
        if(dxgiFactory2)

There is no DXGIFactory2 support on Windows 7 as DXGI 1.1 is not fully implemented, let alone DXGI 1.2.
DirectX 11 on Windows 7 doesn't have the full capabilities set that I require.

Thanks for looking into it! I found that Windows 7 should support it with Platform Update according to https://docs.microsoft.com/en-us/window ... gifactory2 Is it the correct link? I have KB2670838 installed, which my understanding is the Platform Update, but maybe there's an updated Platform Update I'll try to install other updates I'm missing in case it can make a difference.

[Kermitou]

Hi Helifax, and everybody,
I tried all the 3 new fixes, new version 1.02, with Doom Steam, Doom Ethernal on Bethesda platform and Detroit on Epic, but nothing worked. I followed all the instructions on the readme file, under windows 10 2004, Nvidia Driver 451.67, 3D vision Driver installed with "bringback3DV" tool, GTX 1070 and Asus VG278H screen. The resolution is the same on the window panel and the game, option set to borderless display. All the games start, in 2D and I see your little windows blog. But not 3DV ...Strange, because a lot of other games are working fine with the fixes avalable on Helimoxblog ?!? Thank you for your help

[Lysander]

Hi Helifax, and everybody,
I tried all the 3 new fixes, new version 1.02, with Doom Steam, Doom Ethernal on Bethesda platform and Detroit on Epic, but nothing worked. I followed all the instructions on the readme file, under windows 10 2004, Nvidia Driver 451.67, 3D vision Driver installed with "bringback3DV" tool, GTX 1070 and Asus VG278H screen. The resolution is the same on the window panel and the game, option set to borderless display. All the games start, in 2D and I see your little windows blog. But not 3DV ...Strange, because a lot of other games are working fine with the fixes avalable on Helimoxblog ?!? Thank you for your help

Did you read through this thread about the issues I've had? Maybe the same problem, the driver fix is not applied via 3DFM? Verify it, won't hurt.

[DJ-RK]

Well, unfortunately I've been having some significant issues since my first time running Doom: Eternal using Vk3DVision, and I've been doing my best to troubleshoot on my own but have been running into further problems, so I figured I should bring this to your attention and ask some questions to try to narrow down the issue.

Let me break down the issue and give a bit of a timeline:

- Successfully played D:E on Monday with absolutely no issues (other than running out of ammo and dying all the time on Nightmare difficulty ;p). Obviously followed the instructions (since it was working). This is on a PC running Win 10 v2004, Nvidia driver 451.48

- Tried loading D:E again to continue playing on Wednesday evening, and was prompted with the error in the attached screenshot. I made no major system changes at all between the two sessions, in fact, I barely used my computer at all on account of returning to work this week (and being too tired to do anything Tuesday evening).

- I considered the possibility that somehow that 3D was turned off, so I loaded up 3DFM and sure enough it showed both 3D AND the Win10 driver modification was turned off (which is odd because not only do I know for certain I did not turn either off at the time, I almost never turn off the Win10 hack at all. When I disable 3D I just use a .bat script I have on my desktop which only changes the registry to disable 3D, so I'm confident that I did not make those changes). When I tried to enable 3D in 3DFM, 3DFM would just crash.

- Since, at this point I could identify multiple potential sources of the cause of the issue I did everything logical to try to fix it: I unistalled 3DFM entirely, DDU'd, reinstalled the same driver, reinstalled 3DFM and all driver hacks. I also performed a check on my system for malware which came back clean (I do not run a commercial AV during regular PC usage, btw, as I don't mess with untrustworthy sources, so that's not a potential culprit)

- Now when I try loading up D:E, or even D:2016 (edit: and a few other games seem to be affected now too) I just get a silent crash during launch. If I try launching either game using the .exe files (without vkvision running), I get a windows error saying XINPUT1_3.dll cannot be found. Have done full reinstalls of both games. Other games launch fine, 3D works, 3DFM no longer crashes, etc.

Now, being a former IT support technician, I know not to immediately assume things, neither positive or negative (for example, even though I did a malware check, I know not to rule that out entirely), so don't take this question as a form of mistrust or suspicion, but since I've encountered 2 separate errors regarding missing system dlls I have to ask: does Vk3DVision access or modify the dlls in the Windows system folder, or anything of the sort that may be contributing to this issue I'm facing? I'm wondering if maybe it modifies the files (or access to them) while VkVision is in use, then restores them when done, and perhaps something happened to cause the last part to not occur, or something to that effect. I'll continue to troubleshoot on my own and try to resolve this issue (though if you have any suggestions I'd be more than happy to try them), but I had to ask since this is pretty much the only thing I've done on my PC and it (so far) seems to be the only thing affected.

Update: Found even more games saying even more .dll's were missing (eg. msvcp120.dll & msvcp140.dll). Perhaps my system did not properly shut down on Monday evening and corrupted some system files or something. Reinstalled the various VC++ redistributables and dx2010 packages to reacquire those files, and got D:2016 to load up just fine (without VkVision so far) so I think I'm good, but will leave the post intact to keep the error report in case it applies and/or helps anyone.

[Lysander]

2. The Crosshair value is in the ini file and you can adjusted from the game (F10, change the ini file, reload the ini file - use the shortcut and adjust it to your liking).

The ini file says the game needs to be restarted for changes to take place - how to "reload" it in-game?

[helifax]

Well, unfortunately I've been having some significant issues since my first time running Doom: Eternal using Vk3DVision, and I've been doing my best to troubleshoot on my own but have been running into further problems, so I figured I should bring this to your attention and ask some questions to try to narrow down the issue.

Let me break down the issue and give a bit of a timeline:

- Successfully played D:E on Monday with absolutely no issues (other than running out of ammo and dying all the time on Nightmare difficulty ;p). Obviously followed the instructions (since it was working). This is on a PC running Win 10 v2004, Nvidia driver 451.48

- Tried loading D:E again to continue playing on Wednesday evening, and was prompted with the error in the attached screenshot. I made no major system changes at all between the two sessions, in fact, I barely used my computer at all on account of returning to work this week (and being too tired to do anything Tuesday evening).

- I considered the possibility that somehow that 3D was turned off, so I loaded up 3DFM and sure enough it showed both 3D AND the Win10 driver modification was turned off (which is odd because not only do I know for certain I did not turn either off at the time, I almost never turn off the Win10 hack at all. When I disable 3D I just use a .bat script I have on my desktop which only changes the registry to disable 3D, so I'm confident that I did not make those changes). When I tried to enable 3D in 3DFM, 3DFM would just crash.

- Since, at this point I could identify multiple potential sources of the cause of the issue I did everything logical to try to fix it: I unistalled 3DFM entirely, DDU'd, reinstalled the same driver, reinstalled 3DFM and all driver hacks. I also performed a check on my system for malware which came back clean (I do not run a commercial AV during regular PC usage, btw, as I don't mess with untrustworthy sources, so that's not a potential culprit)

- Now when I try loading up D:E, or even D:2016 (edit: and a few other games seem to be affected now too) I just get a silent crash during launch. If I try launching either game using the .exe files (without vkvision running), I get a windows error saying XINPUT1_3.dll cannot be found. Have done full reinstalls of both games. Other games launch fine, 3D works, 3DFM no longer crashes, etc.

Now, being a former IT support technician, I know not to immediately assume things, neither positive or negative (for example, even though I did a malware check, I know not to rule that out entirely), so don't take this question as a form of mistrust or suspicion, but since I've encountered 2 separate errors regarding missing system dlls I have to ask: does Vk3DVision access or modify the dlls in the Windows system folder, or anything of the sort that may be contributing to this issue I'm facing? I'm wondering if maybe it modifies the files (or access to them) while VkVision is in use, then restores them when done, and perhaps something happened to cause the last part to not occur, or something to that effect. I'll continue to troubleshoot on my own and try to resolve this issue (though if you have any suggestions I'd be more than happy to try them), but I had to ask since this is pretty much the only thing I've done on my PC and it (so far) seems to be the only thing affected.

Update: Found even more games saying even more .dll's were missing (eg. msvcp120.dll & msvcp140.dll). Reinstalled the various VC++ redistributables and dx2010 packages to reacquire those files, and got D:2016 to load up just fine.

Something strange is going on there with your system.
Vk3DVision does not modify dlls or move dlls around or anything related to this.
Like Reshade/Steam/Renderdoc, etc, it uses the Vulkan Layering Mechanism.
The only memory injection that happens is in the game executable itself (and this is at runtime) and this is for frame sync - which comes as a dll itself.

It sounds something else is going on there... Not sure if this is helpful, but at least I hope it will point you in the right direction?!

[helifax]

2. The Crosshair value is in the ini file and you can adjusted from the game (F10, change the ini file, reload the ini file - use the shortcut and adjust it to your liking).

The ini file says the game needs to be restarted for changes to take place - how to "reload" it in-game?

It says "Some" changes will take effect after a restart only
For key shortcuts - what you are editing - they are on the fly
so, after you edit a key and save the ini file, just press the key and see the effects

[DJ-RK]

Something strange is going on there with your system.
Vk3DVision does not modify dlls or move dlls around or anything related to this.
Like Reshade/Steam/Renderdoc, etc, it uses the Vulkan Layering Mechanism.
The only memory injection that happens is in the game executable itself (and this is at runtime) and this is for frame sync - which comes as a dll itself.

It sounds something else is going on there... Not sure if this is helpful, but at least I hope it will point you in the right direction?!

NP. See my most recent edit to the previous post (we were both typing at the same time). Thanks for confirming that info, definitely something a bit screwy happened on my end then.

[Lysander]

Helifax (or someone) - can you post the original Vk3dVision.exe for Doom 2016, I got the 1.0.2 and am seeing something I thought wasn't there with the previous version so want to verify.

[helifax]

Helifax (or someone) - can you post the original Vk3dVision.exe for Doom 2016, I got the 1.0.2 and am seeing something I thought wasn't there with the previous version so want to verify.

1.0.2 is identical with 1.0.1 except for a crash fix when stereo injection is not enabled.
What exactly are you seeing that you think it's caused by 1.0.2?