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
[quote="DHR"]
@D-Man11
Totally off-topic....can you test Dragon Age Inquisition if works?
I copy-paste all the others effects fixed by mike and Helifax in to the Universal Fix, try [url="https://s3.amazonaws.com/dhr/Test/Dragon.Age.Inquisition.3Dfix.zip"]HERE[/url] and post your results in the Dragon Age thread.[/quote]
Hello, I tested DA:I, it works very well. A wonder :)
On the other hand, and for a little while, I can not take a photo with the ALT + F1 keys. I do not know why, if anyone has an idea?
@D-Man11
Totally off-topic....can you test Dragon Age Inquisition if works?
I copy-paste all the others effects fixed by mike and Helifax in to the Universal Fix, try HERE and post your results in the Dragon Age thread.
Hello, I tested DA:I, it works very well. A wonder :)
On the other hand, and for a little while, I can not take a photo with the ALT + F1 keys. I do not know why, if anyone has an idea?
ASUS VG248QE - 3D Vision 2 - GTX 1080 - i7 7700 - 16GB RAM - WIN 10
@norbert72
Very nice!! all lights are working OK then?
The version of 3Dmigoto is in a better shape than the one shipped in the fix, so not necessary all those tweaks and workaround...and the CS Lights are enabled.
About not be able to take photos, maybe you can try to re-install the driver using DDU.
@norbert72
Very nice!! all lights are working OK then?
The version of 3Dmigoto is in a better shape than the one shipped in the fix, so not necessary all those tweaks and workaround...and the CS Lights are enabled.
About not be able to take photos, maybe you can try to re-install the driver using DDU.
I answered on the topic of DA: I. It's perfect.
I just loaded a few backups. I have not tested more for the moment.
I use DDU at every update. Even if I reinstall the card driver, it does not change anything.
[quote] On the other hand, and for a little while, I can not take a photo with the ALT + F1 keys. I do not know why, if anyone has an idea? [/quote]There's a couple of games where the overlay didn't show up when taking a screenshot for whatever reason, but they were still saved for me.
[URL=http://imgbox.com/gisdKbFr][IMG]https://thumbs2.imgbox.com/0b/e5/gisdKbFr_t.jpg[/IMG][/URL]
I can no longer play, after 5 minutes this writing appears to me. help
with or without 3D fix
windows 10 build 1067 driver 388.13
Very strange....but if this happens with or without the fix, i can suggest to re-install drivers using DDU. And maybe try an older driver....for example in Hitman the game crash for me if i use some drivers version.
Very strange....but if this happens with or without the fix, i can suggest to re-install drivers using DDU. And maybe try an older driver....for example in Hitman the game crash for me if i use some drivers version.
^^^ That error message has been a bane for players of Need for Speed Payback. It happened to me several times as well. Unfortunately I can't tell you what fixes it exactly, although after a game patch along with reinstalling drivers, the problem eventually went away for me. There are some players reporting that the error still plagues them and cannot be eliminated on their system.
Ironically, it has been reported that the error seems to only affect EA published games..... put your tinfoil hats on, there may be dirty work afoot...
^^^ That error message has been a bane for players of Need for Speed Payback. It happened to me several times as well. Unfortunately I can't tell you what fixes it exactly, although after a game patch along with reinstalling drivers, the problem eventually went away for me. There are some players reporting that the error still plagues them and cannot be eliminated on their system.
Ironically, it has been reported that the error seems to only affect EA published games..... put your tinfoil hats on, there may be dirty work afoot...
|CPU: i7-2700k @ 4.5Ghz
|Cooler: Zalman 9900 Max
|MB: MSI Military Class II Z68 GD-80
|RAM: Corsair Vengence 16GB DDR3
|SSDs: Seagate 600 240GB; Crucial M4 128GB
|HDDs: Seagate Barracuda 1TB; Seagate Barracuda 500GB
|PS: OCZ ZX Series 1250watt
|Case: Antec 1200 V3
|Monitors: Asus 3D VG278HE; Asus 3D VG236H; Samsung 3D 51" Plasma;
|GPU:MSI 1080GTX "Duke"
|OS: Windows 10 Pro X64
I've also been getting a lot of 'DirectX function "..." DXGI_ERROR_DEVICE_REMOVED' errors like several other people in this thread.
[img]https://forums.geforce.com/cmd/default/download-comment-attachment/76275/[/img]
I can reliably reproduce it with the latest driver (416.34) using the very first checkpoint after the intro by just looking down. It's related to the fix somehow, because it started to happen after I applied it and stopped when I removed it (no matter if compatibility mode is on or off). Just running uninstall.bat doesn't help, but restoring the files from C:\ProgramData\NVIDIA Corporation\Drs does. These files are modified by the rundll32 process that executes once after applying the fix.
Since playing without 3D was not an option for me, I installed the fix again and started trying different versions of the driver to see if it makes any difference. I found that some old drivers (37x and 38x) crash even more, while 39x seemed to not produce this error at all. I thought that's it and started playing with 399.24. But soon I found another issue that I didn't have with 416.34 - character's skin was completely black in one eye as you can see on the screenshot below.
[img]https://forums.geforce.com/cmd/default/download-comment-attachment/76276/[/img]
This can be temporary fixed by toggling 3D off and on. I started experimenting with the game graphics settings to get rid of it and found that it goes away if I set Lighting quality to medium instead of hyper. Then I remembered that when it was crashing with 416.34 after looking down at the first checkpoint, it did it just before Faith's hand could become visible. That hand was also black in one eye with 399.24 and hyper lighting quality. I went back to 416.34 and it turned out that my thinking was correct. As medium lighting quality fixed the "black skin in one eye" bug with 399.24, it also fixed the DirectX Error with 416.34!
I could still reproduce the error with hyper lighting quality in almost 100% cases. Ultra and high lighting quality gave the same error in about 50% cases and I could never reproduce it on medium at that checkpoint. Unfortunately later I found that it didn't get rid of all crashes. I got two crashes during a couple of hours that I played. One was a similar DirectX Error and another was a more traditional Windows error dialog with faulting module nvwgf2umx.dll and exception code 0xc0000005.
Anyway, even with occasional crashes the game still looks gorgeous in 3D. Big thanks to DHR for the hard work!
I've also been getting a lot of 'DirectX function "..." DXGI_ERROR_DEVICE_REMOVED' errors like several other people in this thread.
I can reliably reproduce it with the latest driver (416.34) using the very first checkpoint after the intro by just looking down. It's related to the fix somehow, because it started to happen after I applied it and stopped when I removed it (no matter if compatibility mode is on or off). Just running uninstall.bat doesn't help, but restoring the files from C:\ProgramData\NVIDIA Corporation\Drs does. These files are modified by the rundll32 process that executes once after applying the fix.
Since playing without 3D was not an option for me, I installed the fix again and started trying different versions of the driver to see if it makes any difference. I found that some old drivers (37x and 38x) crash even more, while 39x seemed to not produce this error at all. I thought that's it and started playing with 399.24. But soon I found another issue that I didn't have with 416.34 - character's skin was completely black in one eye as you can see on the screenshot below.
This can be temporary fixed by toggling 3D off and on. I started experimenting with the game graphics settings to get rid of it and found that it goes away if I set Lighting quality to medium instead of hyper. Then I remembered that when it was crashing with 416.34 after looking down at the first checkpoint, it did it just before Faith's hand could become visible. That hand was also black in one eye with 399.24 and hyper lighting quality. I went back to 416.34 and it turned out that my thinking was correct. As medium lighting quality fixed the "black skin in one eye" bug with 399.24, it also fixed the DirectX Error with 416.34!
I could still reproduce the error with hyper lighting quality in almost 100% cases. Ultra and high lighting quality gave the same error in about 50% cases and I could never reproduce it on medium at that checkpoint. Unfortunately later I found that it didn't get rid of all crashes. I got two crashes during a couple of hours that I played. One was a similar DirectX Error and another was a more traditional Windows error dialog with faulting module nvwgf2umx.dll and exception code 0xc0000005.
Anyway, even with occasional crashes the game still looks gorgeous in 3D. Big thanks to DHR for the hard work!
@john105
Confirm that the game is better with the drivers 416.34?
decreased crash error dx?
I would like to finish it finally, but with other games the driver is bad
For nvidia forum driver 416.34
Also Witcher 3 is flickering with flash lights on screen, same as the video posted by another user on another thread. Also the game occasionally crash.
Thanks
Confirm that the game is better with the drivers 416.34?
decreased crash error dx?
I would like to finish it finally, but with other games the driver is bad
For nvidia forum driver 416.34
Also Witcher 3 is flickering with flash lights on screen, same as the video posted by another user on another thread. Also the game occasionally crash.
[quote="john105"]I've also been getting a lot of 'DirectX function "..." DXGI_ERROR_DEVICE_REMOVED' errors like several other people in this thread.
.......
I could still reproduce the error with hyper lighting quality in almost 100% cases. Ultra and high lighting quality gave the same error in about 50% cases and I could never reproduce it on medium at that checkpoint. Unfortunately later I found that it didn't get rid of all crashes. I got two crashes during a couple of hours that I played. One was a similar DirectX Error and another was a more traditional Windows error dialog with faulting module nvwgf2umx.dll and exception code 0xc0000005.
Anyway, even with occasional crashes the game still looks gorgeous in 3D. Big thanks to DHR for the hard work![/quote]
Out of interest, if your GPU overclocked at all? Have you tried underclocking to see if that aids stability?
I appreciate you've done a load of troubleshooting, but personally when I've seen this error it's been related to video card memory/core settings. Clearly it can 100% be down to software also (bad code/conflicts).
I've ran high overclocks in the past which were stable on some games and not others, even down to individual settings making a difference just due to the way they load different parts of the graphics subsystem.
john105 said:I've also been getting a lot of 'DirectX function "..." DXGI_ERROR_DEVICE_REMOVED' errors like several other people in this thread.
.......
I could still reproduce the error with hyper lighting quality in almost 100% cases. Ultra and high lighting quality gave the same error in about 50% cases and I could never reproduce it on medium at that checkpoint. Unfortunately later I found that it didn't get rid of all crashes. I got two crashes during a couple of hours that I played. One was a similar DirectX Error and another was a more traditional Windows error dialog with faulting module nvwgf2umx.dll and exception code 0xc0000005.
Anyway, even with occasional crashes the game still looks gorgeous in 3D. Big thanks to DHR for the hard work!
Out of interest, if your GPU overclocked at all? Have you tried underclocking to see if that aids stability?
I appreciate you've done a load of troubleshooting, but personally when I've seen this error it's been related to video card memory/core settings. Clearly it can 100% be down to software also (bad code/conflicts).
I've ran high overclocks in the past which were stable on some games and not others, even down to individual settings making a difference just due to the way they load different parts of the graphics subsystem.
GTX 1070 SLI, I7-6700k ~ 4.4Ghz, 3x BenQ XL2420T, BenQ TK800, LG 55EG960V (3D OLED), Samsung 850 EVO SSD, Crucial M4 SSD, 3D vision kit, Xpand x104 glasses, Corsair HX1000i, Win 10 pro 64/Win 7 64https://www.3dmark.com/fs/9529310
[quote="maurizioclaudio21"]@john105
Confirm that the game is better with the drivers 416.34?
decreased crash error dx?
I would like to finish it finally, but with other games the driver is bad
For nvidia forum driver 416.34
Also Witcher 3 is flickering with flash lights on screen, same as the video posted by another user on another thread. Also the game occasionally crash.
Thanks[/quote]
I don't think it's better with 416.34 compared to 399.24 for example. I'm just using it because it's the latest. The main thing that helped me was setting Lighting Quality to Medium in the game's settings.
I'm not sure about flickering because I haven't tried many games with this driver. I don't have Witcher 3 to try.
[quote="rustyk21"]Out of interest, if your GPU overclocked at all? Have you tried underclocking to see if that aids stability?
I appreciate you've done a load of troubleshooting, but personally when I've seen this error it's been related to video card memory/core settings. Clearly it can 100% be down to software also (bad code/conflicts).
I've ran high overclocks in the past which were stable on some games and not others, even down to individual settings making a difference just due to the way they load different parts of the graphics subsystem.[/quote]
Both my GPU and CPU are not overclocked. I didn't try to underclock because I never had issues with other games. The fact that I can reliably reproduce the error after loading the first checkpoint and looking down with Hyper Lighting Quality also tells me that it's software related.
Confirm that the game is better with the drivers 416.34?
decreased crash error dx?
I would like to finish it finally, but with other games the driver is bad
For nvidia forum driver 416.34
Also Witcher 3 is flickering with flash lights on screen, same as the video posted by another user on another thread. Also the game occasionally crash.
Thanks
I don't think it's better with 416.34 compared to 399.24 for example. I'm just using it because it's the latest. The main thing that helped me was setting Lighting Quality to Medium in the game's settings.
I'm not sure about flickering because I haven't tried many games with this driver. I don't have Witcher 3 to try.
rustyk21 said:Out of interest, if your GPU overclocked at all? Have you tried underclocking to see if that aids stability?
I appreciate you've done a load of troubleshooting, but personally when I've seen this error it's been related to video card memory/core settings. Clearly it can 100% be down to software also (bad code/conflicts).
I've ran high overclocks in the past which were stable on some games and not others, even down to individual settings making a difference just due to the way they load different parts of the graphics subsystem.
Both my GPU and CPU are not overclocked. I didn't try to underclock because I never had issues with other games. The fact that I can reliably reproduce the error after loading the first checkpoint and looking down with Hyper Lighting Quality also tells me that it's software related.
I did some more experiments with this game. As I mentioned before, I didn't get any crashes without the fix even in 3D with CM off. But once I installed the fix, simply uninstalling it didn't help, I also needed to restore C:\ProgramData\NVIDIA Corporation\Drs, which is the folder where the game profiles are stored.
I checked what profile settings the fix changes in Nvidia Profile Inspector and found that what causes the game to crash was the StereoFlagsDX10 parameter. So the game without the fix and with the default profile doesn't crash, and as soon as I change StereoFlagsDX10 to 0x00004008, it starts crashing. When the fix is installed, changing '4' in StereoFlagsDX10 to some other values also prevents the error. Changing '8' doesn't seem to make any difference. I tried values from 0 to F instead of 4, but all values where I don't get the crash also break something in 3D. I got the best result with StereoFlagsDX10 set to 0x0000C008. Zero crashes, but some things still look incorrect:
[img]https://forums.geforce.com/cmd/default/download-comment-attachment/76319/[/img]
I guess if the fix could be adapted to work with StereoFlagsDX10=0x0000C008 instead of 0x00004008, it would resolve the DirectX Error, but I'm not sure how easy it would be to do.
Another thing that helped to avoid the crash even with StereoFlagsDX10=0x00004008 was uncommenting the [TextureOverrideUAVNotRT] section in d3dx.ini, but it didn't look any better than with StereoFlagsDX10=0x0000C008.
I did some more experiments with this game. As I mentioned before, I didn't get any crashes without the fix even in 3D with CM off. But once I installed the fix, simply uninstalling it didn't help, I also needed to restore C:\ProgramData\NVIDIA Corporation\Drs, which is the folder where the game profiles are stored.
I checked what profile settings the fix changes in Nvidia Profile Inspector and found that what causes the game to crash was the StereoFlagsDX10 parameter. So the game without the fix and with the default profile doesn't crash, and as soon as I change StereoFlagsDX10 to 0x00004008, it starts crashing. When the fix is installed, changing '4' in StereoFlagsDX10 to some other values also prevents the error. Changing '8' doesn't seem to make any difference. I tried values from 0 to F instead of 4, but all values where I don't get the crash also break something in 3D. I got the best result with StereoFlagsDX10 set to 0x0000C008. Zero crashes, but some things still look incorrect:
I guess if the fix could be adapted to work with StereoFlagsDX10=0x0000C008 instead of 0x00004008, it would resolve the DirectX Error, but I'm not sure how easy it would be to do.
Another thing that helped to avoid the crash even with StereoFlagsDX10=0x00004008 was uncommenting the [TextureOverrideUAVNotRT] section in d3dx.ini, but it didn't look any better than with StereoFlagsDX10=0x0000C008.
@john105
Thanks for the tests you do
if you tell me that it's playable with that parameter StereoFlagsDX10=0x0000C008 it would be nice
can not you post some screensavers?
you don't have errors dx with that parameter?
@john105
Thanks for the tests you do
if you tell me that it's playable with that parameter StereoFlagsDX10=0x0000C008 it would be nice
can not you post some screensavers?
you don't have errors dx with that parameter?
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)
Hello, I tested DA:I, it works very well. A wonder :)
On the other hand, and for a little while, I can not take a photo with the ALT + F1 keys. I do not know why, if anyone has an idea?
ASUS VG248QE - 3D Vision 2 - GTX 1080 - i7 7700 - 16GB RAM - WIN 10
Very nice!! all lights are working OK then?
The version of 3Dmigoto is in a better shape than the one shipped in the fix, so not necessary all those tweaks and workaround...and the CS Lights are enabled.
About not be able to take photos, maybe you can try to re-install the driver using DDU.
MY WEB
Helix Mod - Making 3D Better
My 3D Screenshot Gallery
Like my fixes? you can donate to Paypal: dhr.donation@gmail.com
I just loaded a few backups. I have not tested more for the moment.
I use DDU at every update. Even if I reinstall the card driver, it does not change anything.
ASUS VG248QE - 3D Vision 2 - GTX 1080 - i7 7700 - 16GB RAM - WIN 10
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
I can no longer play, after 5 minutes this writing appears to me. help
with or without 3D fix
windows 10 build 1067 driver 388.13
MY WEB
Helix Mod - Making 3D Better
My 3D Screenshot Gallery
Like my fixes? you can donate to Paypal: dhr.donation@gmail.com
Ironically, it has been reported that the error seems to only affect EA published games..... put your tinfoil hats on, there may be dirty work afoot...
|CPU: i7-2700k @ 4.5Ghz
|Cooler: Zalman 9900 Max
|MB: MSI Military Class II Z68 GD-80
|RAM: Corsair Vengence 16GB DDR3
|SSDs: Seagate 600 240GB; Crucial M4 128GB
|HDDs: Seagate Barracuda 1TB; Seagate Barracuda 500GB
|PS: OCZ ZX Series 1250watt
|Case: Antec 1200 V3
|Monitors: Asus 3D VG278HE; Asus 3D VG236H; Samsung 3D 51" Plasma;
|GPU:MSI 1080GTX "Duke"
|OS: Windows 10 Pro X64
I can reliably reproduce it with the latest driver (416.34) using the very first checkpoint after the intro by just looking down. It's related to the fix somehow, because it started to happen after I applied it and stopped when I removed it (no matter if compatibility mode is on or off). Just running uninstall.bat doesn't help, but restoring the files from C:\ProgramData\NVIDIA Corporation\Drs does. These files are modified by the rundll32 process that executes once after applying the fix.
Since playing without 3D was not an option for me, I installed the fix again and started trying different versions of the driver to see if it makes any difference. I found that some old drivers (37x and 38x) crash even more, while 39x seemed to not produce this error at all. I thought that's it and started playing with 399.24. But soon I found another issue that I didn't have with 416.34 - character's skin was completely black in one eye as you can see on the screenshot below.
This can be temporary fixed by toggling 3D off and on. I started experimenting with the game graphics settings to get rid of it and found that it goes away if I set Lighting quality to medium instead of hyper. Then I remembered that when it was crashing with 416.34 after looking down at the first checkpoint, it did it just before Faith's hand could become visible. That hand was also black in one eye with 399.24 and hyper lighting quality. I went back to 416.34 and it turned out that my thinking was correct. As medium lighting quality fixed the "black skin in one eye" bug with 399.24, it also fixed the DirectX Error with 416.34!
I could still reproduce the error with hyper lighting quality in almost 100% cases. Ultra and high lighting quality gave the same error in about 50% cases and I could never reproduce it on medium at that checkpoint. Unfortunately later I found that it didn't get rid of all crashes. I got two crashes during a couple of hours that I played. One was a similar DirectX Error and another was a more traditional Windows error dialog with faulting module nvwgf2umx.dll and exception code 0xc0000005.
Anyway, even with occasional crashes the game still looks gorgeous in 3D. Big thanks to DHR for the hard work!
Confirm that the game is better with the drivers 416.34?
decreased crash error dx?
I would like to finish it finally, but with other games the driver is bad
For nvidia forum driver 416.34
Also Witcher 3 is flickering with flash lights on screen, same as the video posted by another user on another thread. Also the game occasionally crash.
Thanks
Out of interest, if your GPU overclocked at all? Have you tried underclocking to see if that aids stability?
I appreciate you've done a load of troubleshooting, but personally when I've seen this error it's been related to video card memory/core settings. Clearly it can 100% be down to software also (bad code/conflicts).
I've ran high overclocks in the past which were stable on some games and not others, even down to individual settings making a difference just due to the way they load different parts of the graphics subsystem.
GTX 1070 SLI, I7-6700k ~ 4.4Ghz, 3x BenQ XL2420T, BenQ TK800, LG 55EG960V (3D OLED), Samsung 850 EVO SSD, Crucial M4 SSD, 3D vision kit, Xpand x104 glasses, Corsair HX1000i, Win 10 pro 64/Win 7 64https://www.3dmark.com/fs/9529310
I don't think it's better with 416.34 compared to 399.24 for example. I'm just using it because it's the latest. The main thing that helped me was setting Lighting Quality to Medium in the game's settings.
I'm not sure about flickering because I haven't tried many games with this driver. I don't have Witcher 3 to try.
Both my GPU and CPU are not overclocked. I didn't try to underclock because I never had issues with other games. The fact that I can reliably reproduce the error after loading the first checkpoint and looking down with Hyper Lighting Quality also tells me that it's software related.
I checked what profile settings the fix changes in Nvidia Profile Inspector and found that what causes the game to crash was the StereoFlagsDX10 parameter. So the game without the fix and with the default profile doesn't crash, and as soon as I change StereoFlagsDX10 to 0x00004008, it starts crashing. When the fix is installed, changing '4' in StereoFlagsDX10 to some other values also prevents the error. Changing '8' doesn't seem to make any difference. I tried values from 0 to F instead of 4, but all values where I don't get the crash also break something in 3D. I got the best result with StereoFlagsDX10 set to 0x0000C008. Zero crashes, but some things still look incorrect:
I guess if the fix could be adapted to work with StereoFlagsDX10=0x0000C008 instead of 0x00004008, it would resolve the DirectX Error, but I'm not sure how easy it would be to do.
Another thing that helped to avoid the crash even with StereoFlagsDX10=0x00004008 was uncommenting the [TextureOverrideUAVNotRT] section in d3dx.ini, but it didn't look any better than with StereoFlagsDX10=0x0000C008.
Thanks for the tests you do
if you tell me that it's playable with that parameter StereoFlagsDX10=0x0000C008 it would be nice
can not you post some screensavers?
you don't have errors dx with that parameter?
The fix need the Stereoflag = 0x00004008, if not all CS Lights will be broken.
I don't have any crashes, so probably is related to win10.
MY WEB
Helix Mod - Making 3D Better
My 3D Screenshot Gallery
Like my fixes? you can donate to Paypal: dhr.donation@gmail.com