DJ-RK wrote: ↑Fri Sep 25, 2020 2:14 pm
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.