3Dmigoto now open-source...
  118 / 143    
[quote="DarkStarSword"][center][color="orange"][size="XL"]3Dmigoto 1.2.68[/size][/color][/center][center][color="green"][url]https://github.com/bo3b/3Dmigoto/releases[/url][/color][/center][/quote] Trying to plug this DLL into my existing FFXIV fix (currently on the .67 release) has broken lighting in the fix. Might not be a huge issue, ie. if a fix is made using this version from the ground up it might be fine, but thought I'd report it all the same. Image from .68 [img]https://forums.geforce.com/cmd/default/download-comment-attachment/74238/[/img] Image from .67 [img]https://forums.geforce.com/cmd/default/download-comment-attachment/74239/[/img] Didn't really bother to go past this character select screen to see if there were further issues, but if you'd like me to do so, or to provide anything else then let me know. Also since it didn't seem like any new features were added I didn't bother to check the new d3dx.ini file to see if any new additions were made and/or necessary, so if there were then maybe that's why.
DarkStarSword said:
3Dmigoto 1.2.68


Trying to plug this DLL into my existing FFXIV fix (currently on the .67 release) has broken lighting in the fix. Might not be a huge issue, ie. if a fix is made using this version from the ground up it might be fine, but thought I'd report it all the same.

Image from .68

Image

Image from .67

Image

Didn't really bother to go past this character select screen to see if there were further issues, but if you'd like me to do so, or to provide anything else then let me know.

Also since it didn't seem like any new features were added I didn't bother to check the new d3dx.ini file to see if any new additions were made and/or necessary, so if there were then maybe that's why.

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

Posted 12/22/2017 01:58 AM   
[quote="DJ-RK"]Trying to plug this DLL into my existing FFXIV fix (currently on the .67 release) has broken lighting in the fix.[/quote]Can you provide a debug log from running the game long enough to see this (even just to the menu would probably be ok) - at a guess I'd bet that there is a good chance that the changes to StereoParams hasn't worked for this game and now it isn't bound at all. [quote]Also since it didn't seem like any new features were added I didn't bother to check the new d3dx.ini file to see if any new additions were made and/or necessary, so if there were then maybe that's why.[/quote]No, no d3dx.ini changes in this release.
DJ-RK said:Trying to plug this DLL into my existing FFXIV fix (currently on the .67 release) has broken lighting in the fix.
Can you provide a debug log from running the game long enough to see this (even just to the menu would probably be ok) - at a guess I'd bet that there is a good chance that the changes to StereoParams hasn't worked for this game and now it isn't bound at all.

Also since it didn't seem like any new features were added I didn't bother to check the new d3dx.ini file to see if any new additions were made and/or necessary, so if there were then maybe that's why.
No, no d3dx.ini changes in this release.

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

Posted 12/22/2017 06:07 AM   
[quote="DarkStarSword"]at a guess I'd bet that there is a good chance that the changes to StereoParams hasn't worked for this game and now it isn't bound at all.[/quote] You're probably right (little surprise there). This time I noticed even the HUD/cursor isn't pushed into depth on the menu screen. Log attached.
DarkStarSword said:at a guess I'd bet that there is a good chance that the changes to StereoParams hasn't worked for this game and now it isn't bound at all.


You're probably right (little surprise there). This time I noticed even the HUD/cursor isn't pushed into depth on the menu screen.

Log attached.
Attachments

d3d11_log.7z.jpg

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

Posted 12/23/2017 02:47 AM   
I've pushed up something that should in theory fix the issue in FFXIV - the game was using a DirectX call that could unbind StereoParams that I had forgotten about. We'll probably wait until we have a fix for The Division as well for the next release, but I just tried it on my Win 7 laptop (it did end up downloading in time) and it seems to be working. Are you on Win 10 as your signature says? Not sure if Bo3b has had a chance to look at it, but I definitely won't be able to try it on Win 10 until I get home in the new year.
I've pushed up something that should in theory fix the issue in FFXIV - the game was using a DirectX call that could unbind StereoParams that I had forgotten about.

We'll probably wait until we have a fix for The Division as well for the next release, but I just tried it on my Win 7 laptop (it did end up downloading in time) and it seems to be working. Are you on Win 10 as your signature says? Not sure if Bo3b has had a chance to look at it, but I definitely won't be able to try it on Win 10 until I get home in the new year.

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

Posted 12/23/2017 11:03 AM   
The Division has no crash for me on Win7, Driver 388.59, 3Dmigoto 1.2.68. Edit: Get crash on Win10 AE, Driver 385.69. Doing some required Win10 update (different from Win7 install, same folder), and will look into it. Edit2: Also confirm same behavior. Crashes on 1.2.67/68, but runs on 1.2.66. Only on Win10 crash. Confirmed that it is change: https://github.com/bo3b/3Dmigoto/commit/eb5f5091c6069a62f758f49c30f81a8ead9711ef
The Division has no crash for me on Win7, Driver 388.59, 3Dmigoto 1.2.68.

Edit: Get crash on Win10 AE, Driver 385.69. Doing some required Win10 update (different from Win7 install, same folder), and will look into it.

Edit2: Also confirm same behavior. Crashes on 1.2.67/68, but runs on 1.2.66. Only on Win10 crash. Confirmed that it is change: https://github.com/bo3b/3Dmigoto/commit/eb5f5091c6069a62f758f49c30f81a8ead9711ef

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

Posted 12/23/2017 11:24 PM   
Yeah, I'm running Win 10 as my primary. I do have Win 7 on a separate drive that I can dual boot into, but haven't really touched that since having done a fresh reinstall (so it's pretty barebones right now). I could try installing UPlay on it and verify if it loads fine for me there. In any event, I'm in no rush for the update for FFXIV, so waiting for the next release is fine. Was mainly curious to see if it would gain even more of an performance increase over .67, which was a pretty good bump in itself. Was more concerned with reporting the issue before it potentially cropped up elsewhere.
Yeah, I'm running Win 10 as my primary. I do have Win 7 on a separate drive that I can dual boot into, but haven't really touched that since having done a fresh reinstall (so it's pretty barebones right now). I could try installing UPlay on it and verify if it loads fine for me there.

In any event, I'm in no rush for the update for FFXIV, so waiting for the next release is fine. Was mainly curious to see if it would gain even more of an performance increase over .67, which was a pretty good bump in itself. Was more concerned with reporting the issue before it potentially cropped up elsewhere.

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

Posted 12/23/2017 11:25 PM   
3Dmigoto top-of-tree includes a commit that fixes the crash in TheDivision. This looks to me to be a one-off problem just for this game, because they request IDXGISwapChain2 then 3, even after we've returned errors for device and factory. They are deciding some other way that they are on Win10, and take a different path. This commit just returns an error for this scenario, which makes them back off successfully and does not crash. It will be picked up in next build. Overlay is working and shader hunting is working.
3Dmigoto top-of-tree includes a commit that fixes the crash in TheDivision. This looks to me to be a one-off problem just for this game, because they request IDXGISwapChain2 then 3, even after we've returned errors for device and factory. They are deciding some other way that they are on Win10, and take a different path.

This commit just returns an error for this scenario, which makes them back off successfully and does not crash. It will be picked up in next build.


Overlay is working and shader hunting is working.

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

Posted 12/24/2017 04:48 AM   
[quote="bo3b"]3Dmigoto top-of-tree includes a commit that fixes the crash in TheDivision. This looks to me to be a one-off problem just for this game, because they request IDXGISwapChain2 then 3, even after we've returned errors for device and factory. They are deciding some other way that they are on Win10, and take a different path. This commit just returns an error for this scenario, which makes them back off successfully and does not crash. It will be picked up in next build. Overlay is working and shader hunting is working.[/quote] Could this fix work for "Star Wars Battlefront 2"? Dice updated the Frosbite3 engine and the last iteration seems to now work anymore with 3DMigoto...
bo3b said:3Dmigoto top-of-tree includes a commit that fixes the crash in TheDivision. This looks to me to be a one-off problem just for this game, because they request IDXGISwapChain2 then 3, even after we've returned errors for device and factory. They are deciding some other way that they are on Win10, and take a different path.

This commit just returns an error for this scenario, which makes them back off successfully and does not crash. It will be picked up in next build.


Overlay is working and shader hunting is working.


Could this fix work for "Star Wars Battlefront 2"? Dice updated the Frosbite3 engine and the last iteration seems to now work anymore with 3DMigoto...

1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc


My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com

(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)

Posted 12/24/2017 11:56 AM   
I have a problem with forum tool, this is a try to restore my capacity to post...
I have a problem with forum tool, this is a try to restore my capacity to post...
Attachments

d3d11.log.txt.zip.jps

Posted 12/24/2017 04:56 PM   
[quote="Helifax"][quote="bo3b"]3Dmigoto top-of-tree includes a commit that fixes the crash in TheDivision. This looks to me to be a one-off problem just for this game, because they request IDXGISwapChain2 then 3, even after we've returned errors for device and factory. They are deciding some other way that they are on Win10, and take a different path. This commit just returns an error for this scenario, which makes them back off successfully and does not crash. It will be picked up in next build. Overlay is working and shader hunting is working.[/quote]Could this fix work for "Star Wars Battlefront 2"? Dice updated the Frosbite3 engine and the last iteration seems to now work anymore with 3DMigoto...[/quote] Unlikely I think. Won't hurt to try, but the problem for TheDivision seems fairly odd. Working out the details, it did however point out a flaw in our current wrapping mechanism, which is a bit of a surprise to me, but probably not to DarkStarSword. The objects that are returned as part of DX11 are not true C++ objects, they use a vtable, but are COM based. The new detail that TheDivision showed is that even if an object has an identical in-memory pointer- the object is still somehow different, and our wrap replaces some of their routines with ours, leading to crashes. The way to solve that problem is to only wrap the desired subclassed object (IDXGISwapChain3 in this case), or to use hooks. I suspect that this will fix the problem with Dishonored2 and Batman Telltale. Have not looked at Frostbite3.
Helifax said:
bo3b said:3Dmigoto top-of-tree includes a commit that fixes the crash in TheDivision. This looks to me to be a one-off problem just for this game, because they request IDXGISwapChain2 then 3, even after we've returned errors for device and factory. They are deciding some other way that they are on Win10, and take a different path.

This commit just returns an error for this scenario, which makes them back off successfully and does not crash. It will be picked up in next build.


Overlay is working and shader hunting is working.
Could this fix work for "Star Wars Battlefront 2"? Dice updated the Frosbite3 engine and the last iteration seems to now work anymore with 3DMigoto...

Unlikely I think. Won't hurt to try, but the problem for TheDivision seems fairly odd.

Working out the details, it did however point out a flaw in our current wrapping mechanism, which is a bit of a surprise to me, but probably not to DarkStarSword. The objects that are returned as part of DX11 are not true C++ objects, they use a vtable, but are COM based. The new detail that TheDivision showed is that even if an object has an identical in-memory pointer- the object is still somehow different, and our wrap replaces some of their routines with ours, leading to crashes.

The way to solve that problem is to only wrap the desired subclassed object (IDXGISwapChain3 in this case), or to use hooks. I suspect that this will fix the problem with Dishonored2 and Batman Telltale. Have not looked at Frostbite3.

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

Posted 12/24/2017 11:38 PM   
[quote="bo3b"]I suspect that this will fix the problem with Dishonored2 and Batman Telltale.[/quote] Wow. Quite frankly, a part of me believes The Division is beyond fixable (but I'm still stubborn enough to give it one last kick at the can... maybe), so I nearly didn't bother to report the issue with fear of wasting your guys time and energy if I didn't believe anything good might come from it, but if this gave insight into those other problems and possibly helped you to track down the root cause of those long standing bugs then, well, I'm glad to do my duty! ;) (or, at least, what little I can do these days)
bo3b said:I suspect that this will fix the problem with Dishonored2 and Batman Telltale.


Wow. Quite frankly, a part of me believes The Division is beyond fixable (but I'm still stubborn enough to give it one last kick at the can... maybe), so I nearly didn't bother to report the issue with fear of wasting your guys time and energy if I didn't believe anything good might come from it, but if this gave insight into those other problems and possibly helped you to track down the root cause of those long standing bugs then, well, I'm glad to do my duty! ;) (or, at least, what little I can do these days)

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

Posted 12/25/2017 12:15 AM   
Hello, I am interested by the last 1.2.68 performance improvement because either DCS world or IL2 BoS suffers from significant fps impact when using 3Dmigoto. So I put the last 1.2.68 in my IL2BOs mod, but unfortunately, it looks like there is a problem with IL2Bos. It looks like ini_params is always equal to zero. I just overwritten d3d11.dll, d3Dcompiler_46.dll and nvapi64.dll, and that make the mod KO. I tried to change the registry used for ini_params but it didn't fix the problem. I tried to add a line "ps-t15 = IniParams" in a shader entry of d3dx.ini but it didn't change neither. It occured even in VR mode (that is using steamVR) or in 3Dvision mode
Hello,
I am interested by the last 1.2.68 performance improvement because either DCS world or IL2 BoS suffers from significant fps impact when using 3Dmigoto.
So I put the last 1.2.68 in my IL2BOs mod, but unfortunately, it looks like there is a problem with IL2Bos. It looks like ini_params is always equal to zero.
I just overwritten d3d11.dll, d3Dcompiler_46.dll and nvapi64.dll, and that make the mod KO.
I tried to change the registry used for ini_params but it didn't fix the problem.
I tried to add a line "ps-t15 = IniParams" in a shader entry of d3dx.ini but it didn't change neither.
It occured even in VR mode (that is using steamVR) or in 3Dvision mode

Posted 12/25/2017 11:46 AM   
I am interested by the last 1.2.68 performance improvement because either DCS world or IL2 BoS suffers from significant fps impact when using 3Dmigoto. So I put the last 1.2.68 in my IL2BOs mod, but unfortunately, there is a problem with IL2Bos. It looks like ini_params is always equal to zero. I just overwritten d3d11.dll, d3Dcompiler_46.dll and nvapi64.dll, and that make the current mod KO. I tried to change the registry used for ini_params but it didn't fix the problem. I tried to add a line "ps-t15 = IniParams" in a shader entry of d3dx.ini but it didn't change neither. It occured even in VR mode (that is using steamVR) or in 3Dvision mode. I joined the d3d11_log.txt for old dll and new ddl. I am running win 10.
I am interested by the last 1.2.68 performance improvement because either DCS world or IL2 BoS suffers from significant fps impact when using 3Dmigoto.
So I put the last 1.2.68 in my IL2BOs mod, but unfortunately, there is a problem with IL2Bos. It looks like ini_params is always equal to zero.
I just overwritten d3d11.dll, d3Dcompiler_46.dll and nvapi64.dll, and that make the current mod KO.
I tried to change the registry used for ini_params but it didn't fix the problem.
I tried to add a line "ps-t15 = IniParams" in a shader entry of d3dx.ini but it didn't change neither.
It occured even in VR mode (that is using steamVR) or in 3Dvision mode.
I joined the d3d11_log.txt for old dll and new ddl. I am running win 10.
Attachments

game.zip.jps

Posted 12/26/2017 02:17 PM   
Ill be intere[quote="DarkStarSword"]I've pushed up something that should in theory fix the issue in FFXIV - the game was using a DirectX call that could unbind StereoParams that I had forgotten about. We'll probably wait until we have a fix for The Division as well for the next release, but I just tried it on my Win 7 laptop (it did end up downloading in time) and it seems to be working. Are you on Win 10 as your signature says? Not sure if Bo3b has had a chance to look at it, but I definitely won't be able to try it on Win 10 until I get home in the new year.[/quote] Path of exile still seems to have this problem when the game will crash on startup with 3dmigoto in windows 10 but is completely fine in windows 7. None of the .ini options for IDXGISwapChain and such changes anything and according to Bo3b nonthing seems to jump out as a problem in the log. I have tested this on three different systems and they all have the problem in window's 10 so I am sure it's not an issue with my system. Sounds a bit similar. Maybe taking a look at POE might offer up some clues. It's a free download...
Ill be intere
DarkStarSword said:I've pushed up something that should in theory fix the issue in FFXIV - the game was using a DirectX call that could unbind StereoParams that I had forgotten about.

We'll probably wait until we have a fix for The Division as well for the next release, but I just tried it on my Win 7 laptop (it did end up downloading in time) and it seems to be working. Are you on Win 10 as your signature says? Not sure if Bo3b has had a chance to look at it, but I definitely won't be able to try it on Win 10 until I get home in the new year.


Path of exile still seems to have this problem when the game will crash on startup with 3dmigoto in windows 10 but is completely fine in windows 7. None of the .ini options for IDXGISwapChain and such changes anything and according to Bo3b nonthing seems to jump out as a problem in the log. I have tested this on three different systems and they all have the problem in window's 10 so I am sure it's not an issue with my system.

Sounds a bit similar. Maybe taking a look at POE might offer up some clues. It's a free download...

i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
ASUS Turbo 2080TI
Samsung SSD 840Pro
ASUS Z97-WS3D
Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)

Posted 12/26/2017 09:56 PM   
[quote="lefuneste1"]<snip> there is a problem with IL2Bos. It looks like ini_params is always equal to zero.[/quote] This may be the same problem DJ-RJ reported with FFXIV, which should be fixed in the next 3DMigoto release, but I'd need to see the log with debug=1 enabled to be more sure. [quote]I tried to add a line "ps-t15 = IniParams" in a shader entry of d3dx.ini but it didn't change neither.[/quote] Hmmm, that part hasn't changed recently so manually binding IniParams like that should have still worked. I take it you also changed IniParams in the shader to use t15 instead of t120?
lefuneste1 said:<snip>
there is a problem with IL2Bos. It looks like ini_params is always equal to zero.

This may be the same problem DJ-RJ reported with FFXIV, which should be fixed in the next 3DMigoto release, but I'd need to see the log with debug=1 enabled to be more sure.

I tried to add a line "ps-t15 = IniParams" in a shader entry of d3dx.ini but it didn't change neither.

Hmmm, that part hasn't changed recently so manually binding IniParams like that should have still worked. I take it you also changed IniParams in the shader to use t15 instead of t120?

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

Posted 12/27/2017 06:40 AM   
  118 / 143    
Scroll To Top