ASUS ROG Strix GeForce GTX 1080 | Core I7-7700K | 16GB RAM | Win10 Pro x64
Asus ROG Swift PG278Q 3D Vision Monitor
Optoma UHD 40 3D Vision Projector
Paypal donations for 3D Fix Manager: duselpaul86@gmx.de
[quote="maurizioclaudio21"]@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?
[/quote]
My screenshot in the post above is with StereoFlagsDX10=0x0000C008. It's not very bad, but I would rather play with crashes. It crashes about twice per hour with StereoFlagsDX10=0x00004008, so it's still possible to progress. With StereoFlagsDX10=0x0000C008 I played for more than an hour with no crashes.
[quote="DHR"]@john105
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.[/quote]
I'm using Windows 7. Can you try the following way to reproduce the crash?
- Install any 41x driver.
- Set Lighting Quality to Hyper.
- Start a new game, skip the intro and exit.
- Now when you start the game, it will load the first checkpoint when Faith is released. All you need to do is look down and the game should crash. At least it does for me in 95% cases if I do it.
Several people in this thread also reported the same error, so I think it's a common issue.
maurizioclaudio21 said:@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?
My screenshot in the post above is with StereoFlagsDX10=0x0000C008. It's not very bad, but I would rather play with crashes. It crashes about twice per hour with StereoFlagsDX10=0x00004008, so it's still possible to progress. With StereoFlagsDX10=0x0000C008 I played for more than an hour with no crashes.
DHR said:@john105
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.
I'm using Windows 7. Can you try the following way to reproduce the crash?
- Install any 41x driver.
- Set Lighting Quality to Hyper.
- Start a new game, skip the intro and exit.
- Now when you start the game, it will load the first checkpoint when Faith is released. All you need to do is look down and the game should crash. At least it does for me in 95% cases if I do it.
Several people in this thread also reported the same error, so I think it's a common issue.
[quote="Pauldusler"]No crashes here with Win10 and DHR's fix[/quote]
I have Win 10 it is impossibile to play whit DHR fix
depends on the PC configuration?
i have i5 3.5GHz OC 4300 and GTX 1060 6gb
@john105 / maurizioclaudio21
Can you test removing the current fix and install the Frostbite3 Universal Fix?
Just upload: [url]https://s3.amazonaws.com/dhr/Universal_Fixes/Universal.Fixes-3Dmigoto.1.3.11.x64-3DFix.Frostbite3.Engine.zip[/url]
Is using 3Dmigoto 1.3.11, so this can improve things.
[quote="DHR"]@john105 / maurizioclaudio21
Can you test removing the current fix and install the Frostbite3 Universal Fix?
Just upload: [url]https://s3.amazonaws.com/dhr/Universal_Fixes/Universal.Fixes-3Dmigoto.1.3.11.x64-3DFix.Frostbite3.Engine.zip[/url]
Is using 3Dmigoto 1.3.11, so this can improve things.
[/quote]
Thanks DHR but the red writing appears "wanted impossible to update"
[quote="DHR"]@john105 / maurizioclaudio21
Can you test removing the current fix and install the Frostbite3 Universal Fix?
Just upload: [url]https://s3.amazonaws.com/dhr/Universal_Fixes/Universal.Fixes-3Dmigoto.1.3.11.x64-3DFix.Frostbite3.Engine.zip[/url]
Is using 3Dmigoto 1.3.11, so this can improve things.
[/quote]
Thanks, DHR. Even though it still crashes, I only get crashes in about 60% of cases vs 95% with the old fix when I follow the steps I described in [url]https://forums.geforce.com/default/topic/939389/3d-vision/mirrors-edge-catalyst-3d-vision/post/5904761/#5904761[/url].
I can't replicate the crash....i trying with the old fix...the universal fix...and no crash!
I'm using the 416.34 driver.
Be sure to disable Origin overlay.
In the original fix, in the d3dx.ini (line 1197)....can you comment this lines:
[code];Option 2: This option works for Mass Effect Andromeda
[TextureOverrideCubeMapReflections]
; Fixes broken environment mapped reflections
match_misc_flags = +texturecube
match_usage = default
match_bind_flags = +render_target
StereoMode = 2[/code]
[quote="DHR"]I can't replicate the crash....i trying with the old fix...the universal fix...and no crash!
I'm using the 416.34 driver.
Be sure to disable Origin overlay.
In the original fix, in the d3dx.ini (line 1197)....can you comment this lines:
[code];Option 2: This option works for Mass Effect Andromeda
[TextureOverrideCubeMapReflections]
; Fixes broken environment mapped reflections
match_misc_flags = +texturecube
match_usage = default
match_bind_flags = +render_target
StereoMode = 2[/code]
[/quote]
I even tried to use "nocd" to start it without running Origin at all but it didn't make any difference. Commenting the above lines in the original fix also doesn't help.
I guess my way of replicating the crash only works for my system and even on my system it only happens with some driver versions. Like if I use 399, it never crashes at that specific spot, but crashes randomly elsewhere anyway.
Have you ever seen black character skin in one eye as on my screenshot from [url]https://forums.geforce.com/default/topic/939389/3d-vision/mirrors-edge-catalyst-3d-vision/post/5899450/#5899450[/url] with 39x drivers? As I described in that post, I think that skin bug and crashes are related.
DHR said:I can't replicate the crash....i trying with the old fix...the universal fix...and no crash!
I'm using the 416.34 driver.
Be sure to disable Origin overlay.
In the original fix, in the d3dx.ini (line 1197)....can you comment this lines:
;Option 2: This option works for Mass Effect Andromeda
[TextureOverrideCubeMapReflections]
; Fixes broken environment mapped reflections
match_misc_flags = +texturecube
match_usage = default
match_bind_flags = +render_target
StereoMode = 2
I even tried to use "nocd" to start it without running Origin at all but it didn't make any difference. Commenting the above lines in the original fix also doesn't help.
I guess my way of replicating the crash only works for my system and even on my system it only happens with some driver versions. Like if I use 399, it never crashes at that specific spot, but crashes randomly elsewhere anyway.
@DHR I have a couple of questions if you don't mind.
1. If I want to use your Frostbite3 Universal Fix, because it seem to at least decrease the amount of crashes, how do I optimize it for Mirror's Edge? Is using d3dx.ini and ShaderFixes from the Mirror's Edge fix and the rest of the files from the Universal Fix enough?
2. You mentioned that using StereoFlagsDX10 = 0x0000C008 instead of 0x00004008 breaks CS Lights. Since I didn't have a single crash with StereoFlagsDX10 = 0x0000C008, I suspect that one of these Compute Shaders is causing the error. Would it be easy for me to somehow disable all of them, and if it helps to avoid the crash, try to enable one by one to find which one is responsible?
@DHR I have a couple of questions if you don't mind.
1. If I want to use your Frostbite3 Universal Fix, because it seem to at least decrease the amount of crashes, how do I optimize it for Mirror's Edge? Is using d3dx.ini and ShaderFixes from the Mirror's Edge fix and the rest of the files from the Universal Fix enough?
2. You mentioned that using StereoFlagsDX10 = 0x0000C008 instead of 0x00004008 breaks CS Lights. Since I didn't have a single crash with StereoFlagsDX10 = 0x0000C008, I suspect that one of these Compute Shaders is causing the error. Would it be easy for me to somehow disable all of them, and if it helps to avoid the crash, try to enable one by one to find which one is responsible?
No problem!
1. In the blog post i put 2 link...the OLD is the original fix and the "updated" is using 3Dmigoto 1.3.11 with Universal Fix (last version).
2. Both fixes are using Regex, so CS are fixed "on the fly"... i don't know how many shader are fixed. if you want to disable all, copy this file in the root folder (\Mirrors Edge Catalyst): [url]https://s3.amazonaws.com/dhr/Test/User.cfg[/url]
1. In the blog post i put 2 link...the OLD is the original fix and the "updated" is using 3Dmigoto 1.3.11 with Universal Fix (last version).
2. Both fixes are using Regex, so CS are fixed "on the fly"... i don't know how many shader are fixed. if you want to disable all, copy this file in the root folder (\Mirrors Edge Catalyst): https://s3.amazonaws.com/dhr/Test/User.cfg
[quote="DHR"]No problem!
1. In the blog post i put 2 link...the OLD is the original fix and the "updated" is using 3Dmigoto 1.3.11 with Universal Fix (last version).
2. Both fixes are using Regex, so CS are fixed "on the fly"... i don't know how many shader are fixed. if you want to disable all, copy this file in the root folder (\Mirrors Edge Catalyst): [url]https://s3.amazonaws.com/dhr/Test/User.cfg[/url][/quote]
1. Thanks! I hope it will reduce the amount of crashes.
2. Yes, I have 0 crashes with User.cfg with both old and new fixes. So how can I try to disable/enable individual CSs? I guess I need to use 3Dmigoto for it. Maybe you know some link that explains how to disable individual CSs?
1. In the blog post i put 2 link...the OLD is the original fix and the "updated" is using 3Dmigoto 1.3.11 with Universal Fix (last version).
2. Both fixes are using Regex, so CS are fixed "on the fly"... i don't know how many shader are fixed. if you want to disable all, copy this file in the root folder (\Mirrors Edge Catalyst): https://s3.amazonaws.com/dhr/Test/User.cfg
1. Thanks! I hope it will reduce the amount of crashes.
2. Yes, I have 0 crashes with User.cfg with both old and new fixes. So how can I try to disable/enable individual CSs? I guess I need to use 3Dmigoto for it. Maybe you know some link that explains how to disable individual CSs?
For testing purpose, can you edit the user.cfg and change this line to "1", like this:
[code]WorldRender.LightTileCsPathEnable 1[/code]
This will enabled the CS Lights, but that user.cfg have others tweaks that may help for the crashes.
When I change WorldRender.LightTileCsPathEnable to 1, I still get crashes, but it also somehow reduces the probability from 95% with the old fix. I have absolutely zero crashes with the original User.cfg that has WorldRender.LightTileCsPathEnable set to 0.
When I change WorldRender.LightTileCsPathEnable to 1, I still get crashes, but it also somehow reduces the probability from 95% with the old fix. I have absolutely zero crashes with the original User.cfg that has WorldRender.LightTileCsPathEnable set to 0.
If you are using any kind of OC (CPU or GPU) i recommend to disable.
To hunt CS you need to enabled CS Tile Lights...and that's the root of your crashes.
If this don't work...i'm out of ideas.
If you are using any kind of OC (CPU or GPU) i recommend to disable.
To hunt CS you need to enabled CS Tile Lights...and that's the root of your crashes.
I don't have any OC. Also all other games work fine.
I never used 3Dmigoto before. Maybe you have some link about how to hunt CS and enable CS Tile Lights or something similar to get started?
Thanks a lot for your help so far!
ASUS ROG Strix GeForce GTX 1080 | Core I7-7700K | 16GB RAM | Win10 Pro x64
Asus ROG Swift PG278Q 3D Vision Monitor
Optoma UHD 40 3D Vision Projector
Paypal donations for 3D Fix Manager: duselpaul86@gmx.de
My screenshot in the post above is with StereoFlagsDX10=0x0000C008. It's not very bad, but I would rather play with crashes. It crashes about twice per hour with StereoFlagsDX10=0x00004008, so it's still possible to progress. With StereoFlagsDX10=0x0000C008 I played for more than an hour with no crashes.
I'm using Windows 7. Can you try the following way to reproduce the crash?
- Install any 41x driver.
- Set Lighting Quality to Hyper.
- Start a new game, skip the intro and exit.
- Now when you start the game, it will load the first checkpoint when Faith is released. All you need to do is look down and the game should crash. At least it does for me in 95% cases if I do it.
Several people in this thread also reported the same error, so I think it's a common issue.
I have Win 10 it is impossibile to play whit DHR fix
depends on the PC configuration?
i have i5 3.5GHz OC 4300 and GTX 1060 6gb
Can you test removing the current fix and install the Frostbite3 Universal Fix?
Just upload: https://s3.amazonaws.com/dhr/Universal_Fixes/Universal.Fixes-3Dmigoto.1.3.11.x64-3DFix.Frostbite3.Engine.zip
Is using 3Dmigoto 1.3.11, so this can improve things.
MY WEB
Helix Mod - Making 3D Better
My 3D Screenshot Gallery
Like my fixes? you can donate to Paypal: dhr.donation@gmail.com
Thanks DHR but the red writing appears "wanted impossible to update"
Thanks, DHR. Even though it still crashes, I only get crashes in about 60% of cases vs 95% with the old fix when I follow the steps I described in https://forums.geforce.com/default/topic/939389/3d-vision/mirrors-edge-catalyst-3d-vision/post/5904761/#5904761.
I'm using the 416.34 driver.
Be sure to disable Origin overlay.
In the original fix, in the d3dx.ini (line 1197)....can you comment this lines:
MY WEB
Helix Mod - Making 3D Better
My 3D Screenshot Gallery
Like my fixes? you can donate to Paypal: dhr.donation@gmail.com
I even tried to use "nocd" to start it without running Origin at all but it didn't make any difference. Commenting the above lines in the original fix also doesn't help.
I guess my way of replicating the crash only works for my system and even on my system it only happens with some driver versions. Like if I use 399, it never crashes at that specific spot, but crashes randomly elsewhere anyway.
Have you ever seen black character skin in one eye as on my screenshot from https://forums.geforce.com/default/topic/939389/3d-vision/mirrors-edge-catalyst-3d-vision/post/5899450/#5899450 with 39x drivers? As I described in that post, I think that skin bug and crashes are related.
1. If I want to use your Frostbite3 Universal Fix, because it seem to at least decrease the amount of crashes, how do I optimize it for Mirror's Edge? Is using d3dx.ini and ShaderFixes from the Mirror's Edge fix and the rest of the files from the Universal Fix enough?
2. You mentioned that using StereoFlagsDX10 = 0x0000C008 instead of 0x00004008 breaks CS Lights. Since I didn't have a single crash with StereoFlagsDX10 = 0x0000C008, I suspect that one of these Compute Shaders is causing the error. Would it be easy for me to somehow disable all of them, and if it helps to avoid the crash, try to enable one by one to find which one is responsible?
1. In the blog post i put 2 link...the OLD is the original fix and the "updated" is using 3Dmigoto 1.3.11 with Universal Fix (last version).
2. Both fixes are using Regex, so CS are fixed "on the fly"... i don't know how many shader are fixed. if you want to disable all, copy this file in the root folder (\Mirrors Edge Catalyst): https://s3.amazonaws.com/dhr/Test/User.cfg
MY WEB
Helix Mod - Making 3D Better
My 3D Screenshot Gallery
Like my fixes? you can donate to Paypal: dhr.donation@gmail.com
1. Thanks! I hope it will reduce the amount of crashes.
2. Yes, I have 0 crashes with User.cfg with both old and new fixes. So how can I try to disable/enable individual CSs? I guess I need to use 3Dmigoto for it. Maybe you know some link that explains how to disable individual CSs?
This will enabled the CS Lights, but that user.cfg have others tweaks that may help for the crashes.
MY WEB
Helix Mod - Making 3D Better
My 3D Screenshot Gallery
Like my fixes? you can donate to Paypal: dhr.donation@gmail.com
To hunt CS you need to enabled CS Tile Lights...and that's the root of your crashes.
If this don't work...i'm out of ideas.
MY WEB
Helix Mod - Making 3D Better
My 3D Screenshot Gallery
Like my fixes? you can donate to Paypal: dhr.donation@gmail.com
I never used 3Dmigoto before. Maybe you have some link about how to hunt CS and enable CS Tile Lights or something similar to get started?
Thanks a lot for your help so far!