[quote="GreatZar"]Can I set separation to 0 somehow (i.e. disable stereo effect without switching s3d off)? Or at least lower then 1? I think that was possible in dx9 wrapper.[/quote]The driver has a hardcoded minimum separation value of 1% without turning stereo off - this is true for both DX11 and DX9.
GreatZar said:Can I set separation to 0 somehow (i.e. disable stereo effect without switching s3d off)? Or at least lower then 1? I think that was possible in dx9 wrapper.
The driver has a hardcoded minimum separation value of 1% without turning stereo off - this is true for both DX11 and DX9.
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
I have a problem in Final Fantasy X, with an effect that is used for multiple effects. Basically, I need to apply the typical correction formula to a TEXCOORD, buuuuut.... it only has 2 dimensions.
//Gravity.
// ---- Created with 3Dmigoto v1.2.37 on Sun May 15 15:03:15 2016
[quote="DarkStarSword"]It's very likely due to the fact that 3DMigoto rejects any attempts of games to use feature levels it doesn't support to avoid crashes in some games (supporting every possible feature level gets very complicated very quickly). There's now a few games impacted by this though (CoH2 is affected, and Shadows of Mordor looks like it might be as well, but that uses an older version of 3DMigoto that isn't affected), so perhaps it is time to revisit this.[/quote]
Probably a good one for us to have an option to allow them through for cases where it's necessary.
For Call of Pripyat, that doesn't look like the problem to me, but maybe. The Log shows only two calls to fetch IDXGIFactory2, which are denied by 3Dmigoto. And the game backs off to IDXGIFactory successfully. Game is supported on Win7 with no evil update, so our path should work.
Also, CoP seems to have problems showing the DX11 options for other people as well. Doing a search I see numerous threads saying they don't have the options available.
@DJ-RK: Still, worth trying an older version of 3Dmigoto without this change to see if fixes it or not.
DarkStarSword said:It's very likely due to the fact that 3DMigoto rejects any attempts of games to use feature levels it doesn't support to avoid crashes in some games (supporting every possible feature level gets very complicated very quickly). There's now a few games impacted by this though (CoH2 is affected, and Shadows of Mordor looks like it might be as well, but that uses an older version of 3DMigoto that isn't affected), so perhaps it is time to revisit this.
Probably a good one for us to have an option to allow them through for cases where it's necessary.
For Call of Pripyat, that doesn't look like the problem to me, but maybe. The Log shows only two calls to fetch IDXGIFactory2, which are denied by 3Dmigoto. And the game backs off to IDXGIFactory successfully. Game is supported on Win7 with no evil update, so our path should work.
Also, CoP seems to have problems showing the DX11 options for other people as well. Doing a search I see numerous threads saying they don't have the options available.
@DJ-RK: Still, worth trying an older version of 3Dmigoto without this change to see if fixes it or not.
Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607 Latest 3Dmigoto Release Bo3b's School for ShaderHackers
Thanks DarkStarSword and bo3b. I got to trying some older versions last evening, and found that version 1.2.13 and lower in the 1.2.x series work (1.1.x series crash on load, though), and 1.2.14 onwards don't work in the fashion as described, so that's where whatever change happened occurred that breaks compatibility with that game.
For the most part 1.2.13 seems to be fine, except for a nasty issue that came up. Essentially, if I manage to load into the game quickly enough it would start in stereo 3D, but very shortly 3D would break and revert to a non-stereo image (although the HUD would still remain separated), and if left alone a bit longer like this, eventually the left eye would become frozen. I tried using frame analysis to locate a render target to set to stereomode=1 like DSS had helped me with another issue, found something that looked promising but didn't have any luck with that hash, but fortunately I've narrowed down the to a particular option in that game that can be set to avoid it on my end, however Blacksmith said that didn't work for him, but he's also running some additional mods which could be a factor and he's still doing some testing. Hopefully we can find a viable workaround, at least.
Thanks DarkStarSword and bo3b. I got to trying some older versions last evening, and found that version 1.2.13 and lower in the 1.2.x series work (1.1.x series crash on load, though), and 1.2.14 onwards don't work in the fashion as described, so that's where whatever change happened occurred that breaks compatibility with that game.
For the most part 1.2.13 seems to be fine, except for a nasty issue that came up. Essentially, if I manage to load into the game quickly enough it would start in stereo 3D, but very shortly 3D would break and revert to a non-stereo image (although the HUD would still remain separated), and if left alone a bit longer like this, eventually the left eye would become frozen. I tried using frame analysis to locate a render target to set to stereomode=1 like DSS had helped me with another issue, found something that looked promising but didn't have any luck with that hash, but fortunately I've narrowed down the to a particular option in that game that can be set to avoid it on my end, however Blacksmith said that didn't work for him, but he's also running some additional mods which could be a factor and he's still doing some testing. Hopefully we can find a viable workaround, at least.
3D Gaming Rig: CPU: i7 7700K @ 4.9Ghz | Mobo: Asus Maximus Hero VIII | RAM: Corsair Dominator 16GB | GPU: 2 x GTX 1080 Ti SLI | 3xSSDs for OS and Apps, 2 x HDD's for 11GB storage | PSU: Seasonic X-1250 M2| Case: Corsair C70 | Cooling: Corsair H115i Hydro cooler | Displays: Asus PG278QR, BenQ XL2420TX & BenQ HT1075 | OS: Windows 10 Pro + Windows 7 dual boot
DarkStarSword (I can't quote from my phone), the problem is the typical "double depth" haloing, although this time the texcoord doesn't have z and w axes.
I still have to wait almost 12 hours until I can try anything, but your 3rd suggestion doesn't work, for example. It affects the influence of convergence, but it isn't the needed value.
DarkStarSword (I can't quote from my phone), the problem is the typical "double depth" haloing, although this time the texcoord doesn't have z and w axes.
I still have to wait almost 12 hours until I can try anything, but your 3rd suggestion doesn't work, for example. It affects the influence of convergence, but it isn't the needed value.
[quote="DJ-RK"]Thanks DarkStarSword and bo3b. I got to trying some older versions last evening, and found that version 1.2.13 and lower in the 1.2.x series work (1.1.x series crash on load, though), and 1.2.14 onwards don't work in the fashion as described, so that's where whatever change happened occurred that breaks compatibility with that game.
For the most part 1.2.13 seems to be fine, except for a nasty issue that came up. Essentially, if I manage to load into the game quickly enough it would start in stereo 3D, but very shortly 3D would break and revert to a non-stereo image (although the HUD would still remain separated), and if left alone a bit longer like this, eventually the left eye would become frozen. I tried using frame analysis to locate a render target to set to stereomode=1 like DSS had helped me with another issue, found something that looked promising but didn't have any luck with that hash, but fortunately I've narrowed down the to a particular option in that game that can be set to avoid it on my end, however Blacksmith said that didn't work for him, but he's also running some additional mods which could be a factor and he's still doing some testing. Hopefully we can find a viable workaround, at least.[/quote]
Based on your debug there using older versions, it is likely that this game is unhappy about the return of E_NOINTERFACE. Looking at the change logs, that fix was added right around that time, probably in 1.2.14.
DJ-RK said:Thanks DarkStarSword and bo3b. I got to trying some older versions last evening, and found that version 1.2.13 and lower in the 1.2.x series work (1.1.x series crash on load, though), and 1.2.14 onwards don't work in the fashion as described, so that's where whatever change happened occurred that breaks compatibility with that game.
For the most part 1.2.13 seems to be fine, except for a nasty issue that came up. Essentially, if I manage to load into the game quickly enough it would start in stereo 3D, but very shortly 3D would break and revert to a non-stereo image (although the HUD would still remain separated), and if left alone a bit longer like this, eventually the left eye would become frozen. I tried using frame analysis to locate a render target to set to stereomode=1 like DSS had helped me with another issue, found something that looked promising but didn't have any luck with that hash, but fortunately I've narrowed down the to a particular option in that game that can be set to avoid it on my end, however Blacksmith said that didn't work for him, but he's also running some additional mods which could be a factor and he's still doing some testing. Hopefully we can find a viable workaround, at least.
Based on your debug there using older versions, it is likely that this game is unhappy about the return of E_NOINTERFACE. Looking at the change logs, that fix was added right around that time, probably in 1.2.14.
Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607 Latest 3Dmigoto Release Bo3b's School for ShaderHackers
[quote="bo3b"]Based on your debug there using older versions, it is likely that this game is unhappy about the return of E_NOINTERFACE. Looking at the change logs, that fix was added right around that time, probably in 1.2.14.[/quote]
Well, after further testing, I'm sad to say that going back to the previous version seems to be a bust. Nothing seems to overcome this issue with 2D breaking. Also, lighting shaders that were previously fixed seem to be breaking as well.
I'm not sure how feasible it would be, but if it's not too much touble, is there any possibility of a hotfixed version of 3DMigoto from a more recent build that removes or toggles that option? Doesn't have to be soon, or an official version, of course.
bo3b said:Based on your debug there using older versions, it is likely that this game is unhappy about the return of E_NOINTERFACE. Looking at the change logs, that fix was added right around that time, probably in 1.2.14.
Well, after further testing, I'm sad to say that going back to the previous version seems to be a bust. Nothing seems to overcome this issue with 2D breaking. Also, lighting shaders that were previously fixed seem to be breaking as well.
I'm not sure how feasible it would be, but if it's not too much touble, is there any possibility of a hotfixed version of 3DMigoto from a more recent build that removes or toggles that option? Doesn't have to be soon, or an official version, of course.
3D Gaming Rig: CPU: i7 7700K @ 4.9Ghz | Mobo: Asus Maximus Hero VIII | RAM: Corsair Dominator 16GB | GPU: 2 x GTX 1080 Ti SLI | 3xSSDs for OS and Apps, 2 x HDD's for 11GB storage | PSU: Seasonic X-1250 M2| Case: Corsair C70 | Cooling: Corsair H115i Hydro cooler | Displays: Asus PG278QR, BenQ XL2420TX & BenQ HT1075 | OS: Windows 10 Pro + Windows 7 dual boot
[quote="DJ-RK"][quote="bo3b"]Based on your debug there using older versions, it is likely that this game is unhappy about the return of E_NOINTERFACE. Looking at the change logs, that fix was added right around that time, probably in 1.2.14.[/quote]Well, after further testing, I'm sad to say that going back to the previous version seems to be a bust. Nothing seems to overcome this issue with 2D breaking. Also, lighting shaders that were previously fixed seem to be breaking as well.
I'm not sure how feasible it would be, but if it's not too much touble, is there any possibility of a hotfixed version of 3DMigoto from a more recent build that removes or toggles that option? Doesn't have to be soon, or an official version, of course.[/quote]
It's an easy change, I'll make a new version later today.
bo3b said:Based on your debug there using older versions, it is likely that this game is unhappy about the return of E_NOINTERFACE. Looking at the change logs, that fix was added right around that time, probably in 1.2.14.
Well, after further testing, I'm sad to say that going back to the previous version seems to be a bust. Nothing seems to overcome this issue with 2D breaking. Also, lighting shaders that were previously fixed seem to be breaking as well.
I'm not sure how feasible it would be, but if it's not too much touble, is there any possibility of a hotfixed version of 3DMigoto from a more recent build that removes or toggles that option? Doesn't have to be soon, or an official version, of course.
It's an easy change, I'll make a new version later today.
Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607 Latest 3Dmigoto Release Bo3b's School for ShaderHackers
3D Gaming Rig: CPU: i7 7700K @ 4.9Ghz | Mobo: Asus Maximus Hero VIII | RAM: Corsair Dominator 16GB | GPU: 2 x GTX 1080 Ti SLI | 3xSSDs for OS and Apps, 2 x HDD's for 11GB storage | PSU: Seasonic X-1250 M2| Case: Corsair C70 | Cooling: Corsair H115i Hydro cooler | Displays: Asus PG278QR, BenQ XL2420TX & BenQ HT1075 | OS: Windows 10 Pro + Windows 7 dual boot
Looking at the code, this doesn't seem to be a slam-dunk. We do have a Factory2 path, but the comments state that it crashes. I don't have CoP, so I can't directly test changes here, and so I can possibly make a build that just crashes for you.
[s]Let's try one more thing to clarify this before going that route. Can you try to uninstall the evil-update KB2670838? Then look at the game and see if it has the same missing options?
It seems to me that the game really needs to support that missing update case, but it might still drop back to fewer options. [/s]
Edit: Ah, I see you already noted this. Works fine under Win7 and fails under Win10. Awesome.
Looking at the code, this doesn't seem to be a slam-dunk. We do have a Factory2 path, but the comments state that it crashes. I don't have CoP, so I can't directly test changes here, and so I can possibly make a build that just crashes for you.
Let's try one more thing to clarify this before going that route. Can you try to uninstall the evil-update KB2670838? Then look at the game and see if it has the same missing options?
It seems to me that the game really needs to support that missing update case, but it might still drop back to fewer options.
Edit: Ah, I see you already noted this. Works fine under Win7 and fails under Win10. Awesome.
Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607 Latest 3Dmigoto Release Bo3b's School for ShaderHackers
FWIW I do have Call of Pripyat (when did I buy that?), so I can possibly work on this a little this weekend. Company of Heroes 2 might also be worth taking a look at since it has a similar problem and is on one of the shared accounts. Also, someone reported trying to use the latest 3DMigoto with Shadows of Morder has a similar error message, but I don't have that game to look at.
FWIW I do have Call of Pripyat (when did I buy that?), so I can possibly work on this a little this weekend. Company of Heroes 2 might also be worth taking a look at since it has a similar problem and is on one of the shared accounts. Also, someone reported trying to use the latest 3DMigoto with Shadows of Morder has a similar error message, but I don't have that game to look at.
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Experimental release here: https://github.com/bo3b/3Dmigoto/releases
1.2.38 has a new option to allow IDXGIFactory2 overrides through. I tested this on Just Cause 3, where I could see it calling for Factory2 and it worked without crashing, so... maybe.
Uncomment the line for ;allow_dxgi1_2=1 to allow these through.
@DarkStarSword: Worth trying on CoH2. For Shadows of Mordor, I see this error too for latest version, but it's not from IDXGIFactory2. Different spot of HackerDXGIAdapter::CheckInterfaceSupport. If I release that forced error it runs. Maybe makes sense to add to this override (but change variable name).
Be worth knowing how often this happens, and which ones, as our force dx11 has been a successful default.
1.2.38 has a new option to allow IDXGIFactory2 overrides through. I tested this on Just Cause 3, where I could see it calling for Factory2 and it worked without crashing, so... maybe.
Uncomment the line for ;allow_dxgi1_2=1 to allow these through.
@DarkStarSword: Worth trying on CoH2. For Shadows of Mordor, I see this error too for latest version, but it's not from IDXGIFactory2. Different spot of HackerDXGIAdapter::CheckInterfaceSupport. If I release that forced error it runs. Maybe makes sense to add to this override (but change variable name).
Be worth knowing how often this happens, and which ones, as our force dx11 has been a successful default.
Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607 Latest 3Dmigoto Release Bo3b's School for ShaderHackers
What a great coincidence, bo3b. Yesterday, the Untitled X mod (a mod for Final Fantasy X that uses dxgi dlls) developer and I were trying to make it work with 3Dmigoto.
Can't wait to try it at home and tell him if it works!
What a great coincidence, bo3b. Yesterday, the Untitled X mod (a mod for Final Fantasy X that uses dxgi dlls) developer and I were trying to make it work with 3Dmigoto.
Can't wait to try it at home and tell him if it works!
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD
Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword
"o2" is the output that needs the fix, but I don't have a depth value to use (the w of the other outputs doesn't work).
Here is the pixel shader:
Any ideas?
CPU: Intel Core i7 7700K @ 4.9GHz
Motherboard: Gigabyte Aorus GA-Z270X-Gaming 5
RAM: GSKILL Ripjaws Z 16GB 3866MHz CL18
GPU: MSI GeForce RTX 2080Ti Gaming X Trio
Monitor: Asus PG278QR
Speakers: Logitech Z506
Donations account: masterotakusuko@gmail.com
o0.x -= separation * (o0.w - convergence);
o0.x += separation * (o0.w - convergence);
o2.x += separation * (o0.w - convergence);
o2.x += separation * (o0.w - convergence) / o0.w;
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD
Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword
Probably a good one for us to have an option to allow them through for cases where it's necessary.
For Call of Pripyat, that doesn't look like the problem to me, but maybe. The Log shows only two calls to fetch IDXGIFactory2, which are denied by 3Dmigoto. And the game backs off to IDXGIFactory successfully. Game is supported on Win7 with no evil update, so our path should work.
Also, CoP seems to have problems showing the DX11 options for other people as well. Doing a search I see numerous threads saying they don't have the options available.
@DJ-RK: Still, worth trying an older version of 3Dmigoto without this change to see if fixes it or not.
Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers
For the most part 1.2.13 seems to be fine, except for a nasty issue that came up. Essentially, if I manage to load into the game quickly enough it would start in stereo 3D, but very shortly 3D would break and revert to a non-stereo image (although the HUD would still remain separated), and if left alone a bit longer like this, eventually the left eye would become frozen. I tried using frame analysis to locate a render target to set to stereomode=1 like DSS had helped me with another issue, found something that looked promising but didn't have any luck with that hash, but fortunately I've narrowed down the to a particular option in that game that can be set to avoid it on my end, however Blacksmith said that didn't work for him, but he's also running some additional mods which could be a factor and he's still doing some testing. Hopefully we can find a viable workaround, at least.
3D Gaming Rig: CPU: i7 7700K @ 4.9Ghz | Mobo: Asus Maximus Hero VIII | RAM: Corsair Dominator 16GB | GPU: 2 x GTX 1080 Ti SLI | 3xSSDs for OS and Apps, 2 x HDD's for 11GB storage | PSU: Seasonic X-1250 M2| Case: Corsair C70 | Cooling: Corsair H115i Hydro cooler | Displays: Asus PG278QR, BenQ XL2420TX & BenQ HT1075 | OS: Windows 10 Pro + Windows 7 dual boot
Like my fixes? Dontations can be made to: www.paypal.me/DShanz or rshannonca@gmail.com
Like electronic music? Check out: www.soundcloud.com/dj-ryan-king
I still have to wait almost 12 hours until I can try anything, but your 3rd suggestion doesn't work, for example. It affects the influence of convergence, but it isn't the needed value.
CPU: Intel Core i7 7700K @ 4.9GHz
Motherboard: Gigabyte Aorus GA-Z270X-Gaming 5
RAM: GSKILL Ripjaws Z 16GB 3866MHz CL18
GPU: MSI GeForce RTX 2080Ti Gaming X Trio
Monitor: Asus PG278QR
Speakers: Logitech Z506
Donations account: masterotakusuko@gmail.com
Based on your debug there using older versions, it is likely that this game is unhappy about the return of E_NOINTERFACE. Looking at the change logs, that fix was added right around that time, probably in 1.2.14.
Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers
After trying them, none fixed the problem. Thank you for the help, anyway :).
CPU: Intel Core i7 7700K @ 4.9GHz
Motherboard: Gigabyte Aorus GA-Z270X-Gaming 5
RAM: GSKILL Ripjaws Z 16GB 3866MHz CL18
GPU: MSI GeForce RTX 2080Ti Gaming X Trio
Monitor: Asus PG278QR
Speakers: Logitech Z506
Donations account: masterotakusuko@gmail.com
Well, after further testing, I'm sad to say that going back to the previous version seems to be a bust. Nothing seems to overcome this issue with 2D breaking. Also, lighting shaders that were previously fixed seem to be breaking as well.
I'm not sure how feasible it would be, but if it's not too much touble, is there any possibility of a hotfixed version of 3DMigoto from a more recent build that removes or toggles that option? Doesn't have to be soon, or an official version, of course.
3D Gaming Rig: CPU: i7 7700K @ 4.9Ghz | Mobo: Asus Maximus Hero VIII | RAM: Corsair Dominator 16GB | GPU: 2 x GTX 1080 Ti SLI | 3xSSDs for OS and Apps, 2 x HDD's for 11GB storage | PSU: Seasonic X-1250 M2| Case: Corsair C70 | Cooling: Corsair H115i Hydro cooler | Displays: Asus PG278QR, BenQ XL2420TX & BenQ HT1075 | OS: Windows 10 Pro + Windows 7 dual boot
Like my fixes? Dontations can be made to: www.paypal.me/DShanz or rshannonca@gmail.com
Like electronic music? Check out: www.soundcloud.com/dj-ryan-king
It's an easy change, I'll make a new version later today.
Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers
3D Gaming Rig: CPU: i7 7700K @ 4.9Ghz | Mobo: Asus Maximus Hero VIII | RAM: Corsair Dominator 16GB | GPU: 2 x GTX 1080 Ti SLI | 3xSSDs for OS and Apps, 2 x HDD's for 11GB storage | PSU: Seasonic X-1250 M2| Case: Corsair C70 | Cooling: Corsair H115i Hydro cooler | Displays: Asus PG278QR, BenQ XL2420TX & BenQ HT1075 | OS: Windows 10 Pro + Windows 7 dual boot
Like my fixes? Dontations can be made to: www.paypal.me/DShanz or rshannonca@gmail.com
Like electronic music? Check out: www.soundcloud.com/dj-ryan-king
Let's try one more thing to clarify this before going that route. Can you try to uninstall the evil-update KB2670838? Then look at the game and see if it has the same missing options?
It seems to me that the game really needs to support that missing update case, but it might still drop back to fewer options.
Edit: Ah, I see you already noted this. Works fine under Win7 and fails under Win10. Awesome.
Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD
Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword
1.2.38 has a new option to allow IDXGIFactory2 overrides through. I tested this on Just Cause 3, where I could see it calling for Factory2 and it worked without crashing, so... maybe.
Uncomment the line for ;allow_dxgi1_2=1 to allow these through.
@DarkStarSword: Worth trying on CoH2. For Shadows of Mordor, I see this error too for latest version, but it's not from IDXGIFactory2. Different spot of HackerDXGIAdapter::CheckInterfaceSupport. If I release that forced error it runs. Maybe makes sense to add to this override (but change variable name).
Be worth knowing how often this happens, and which ones, as our force dx11 has been a successful default.
Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers
Can't wait to try it at home and tell him if it works!
CPU: Intel Core i7 7700K @ 4.9GHz
Motherboard: Gigabyte Aorus GA-Z270X-Gaming 5
RAM: GSKILL Ripjaws Z 16GB 3866MHz CL18
GPU: MSI GeForce RTX 2080Ti Gaming X Trio
Monitor: Asus PG278QR
Speakers: Logitech Z506
Donations account: masterotakusuko@gmail.com