[quote="jhgator1777"]Lohan if you are using SLI , could you share a profile that makes it work please? Also for HDR I did not need to turn on HDR in windows, just turn it on in display setting in-game. and it auto detected for me anyways. It gives me weird effects though , which I am trying to get a screenshot of it, but it seems to happen only in motion.[/quote]
Sorry, I am not using SLI (just a single Titan X Pascal). Unfortunately HDR is greyed-out in my ingame-settings so no way for me to activate it currently.
[quote="masterotaku"]lohan: I haven't reached that part yet. I used all the time yesterday to fix shaders.[/quote]
I tried to deactivate 3D Vision for the Alligator-scene. This time even deactivating 3D Vision was not enough. I still got a freezing-crash. Interestingly when I uninstalled the WIP9-fix and then gave it another try I didn't get a crash. After the Alligator scene everything seems fine so far...
jhgator1777 said:Lohan if you are using SLI , could you share a profile that makes it work please? Also for HDR I did not need to turn on HDR in windows, just turn it on in display setting in-game. and it auto detected for me anyways. It gives me weird effects though , which I am trying to get a screenshot of it, but it seems to happen only in motion.
Sorry, I am not using SLI (just a single Titan X Pascal). Unfortunately HDR is greyed-out in my ingame-settings so no way for me to activate it currently.
masterotaku said:lohan: I haven't reached that part yet. I used all the time yesterday to fix shaders.
I tried to deactivate 3D Vision for the Alligator-scene. This time even deactivating 3D Vision was not enough. I still got a freezing-crash. Interestingly when I uninstalled the WIP9-fix and then gave it another try I didn't get a crash. After the Alligator scene everything seems fine so far...
For some reason when I installed the SLI profile, I cannot get fullscreen to work, 3d activates but I get a bordered screen and its offset to the right where i can see my dekstop in the background on the left. Tried ALT+Tab, not working, and settings are correct in-game, any suggestions? Also wondering why that SLI profile has GPU Count set to 4...
For some reason when I installed the SLI profile, I cannot get fullscreen to work, 3d activates but I get a bordered screen and its offset to the right where i can see my dekstop in the background on the left. Tried ALT+Tab, not working, and settings are correct in-game, any suggestions? Also wondering why that SLI profile has GPU Count set to 4...
[quote="jhgator1777"]Also wondering why that SLI profile has GPU Count set to 4...[/quote]
Because in SLI, you can have up to 4 GPUs. It doesn't matter. You can set it to 2 (if you have only 2). But if you have 4way-SLI and set it to 2, only 2 will be used. If you have 2 and set it to 4, guess what ^_^ Your only 2 GPUs will be used :)
jhgator1777 said:Also wondering why that SLI profile has GPU Count set to 4...
Because in SLI, you can have up to 4 GPUs. It doesn't matter. You can set it to 2 (if you have only 2). But if you have 4way-SLI and set it to 2, only 2 will be used. If you have 2 and set it to 4, guess what ^_^ Your only 2 GPUs will be used :)
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="lohan_0903"]I tried to deactivate 3D Vision for the Alligator-scene. This time even deactivating 3D Vision was not enough. I still got a freezing-crash.[/quote]
That's because the resource responsible is created, stereoized when it shouldn't be, and therefore broken during the loading screen before that scene. This creates a silent killer in which your game is destined to freeze, since quitting/advancing the game triggers its destruction and that's where the freeze happens. The different cases and silent breaks make these broken resources unpredictable.
If 3D is disabled via hotkey before the loading screen, then the resource won't be stereoized. You may need to advance far enough if it's working, but idk how far. So try that and see if it helps. Also if you see d3d11_log.txt, then uploading that will help debug the crashes happening. I forget if it needs verbose debugging enabled.
lohan_0903 said:I tried to deactivate 3D Vision for the Alligator-scene. This time even deactivating 3D Vision was not enough. I still got a freezing-crash.
That's because the resource responsible is created, stereoized when it shouldn't be, and therefore broken during the loading screen before that scene. This creates a silent killer in which your game is destined to freeze, since quitting/advancing the game triggers its destruction and that's where the freeze happens. The different cases and silent breaks make these broken resources unpredictable.
If 3D is disabled via hotkey before the loading screen, then the resource won't be stereoized. You may need to advance far enough if it's working, but idk how far. So try that and see if it helps. Also if you see d3d11_log.txt, then uploading that will help debug the crashes happening. I forget if it needs verbose debugging enabled.
---
Windows 10 x64 / 1x 980Ti GPU (no SLI, 418.81 driver) / 1920x1080
The alligator scene is fine, after disabling the two texture overrides I mentioned in previous posts (TextureOverride_Rain_112_10 and TextureOverride_Raina4). I closed the game after starting to control Ada.
Comment them or wait for today's update. I fixed clipping for some settings combinations (subsurface scattering + contact shadows), but with others the code is different.
The alligator scene is fine, after disabling the two texture overrides I mentioned in previous posts (TextureOverride_Rain_112_10 and TextureOverride_Raina4). I closed the game after starting to control Ada.
Comment them or wait for today's update. I fixed clipping for some settings combinations (subsurface scattering + contact shadows), but with others the code is different.
[quote="masterotaku"]lohan: I haven't reached that part yet. I used all the time yesterday to fix shaders.
Necropants: what if you disable SLI?[/quote]
As I posted in discord, unfortunately yes. =(
Maybe I will try that SLI profile djgrege posted
masterotaku said:lohan: I haven't reached that part yet. I used all the time yesterday to fix shaders.
Necropants: what if you disable SLI?
As I posted in discord, unfortunately yes. =(
Maybe I will try that SLI profile djgrege posted
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)
there was an update to the game today which added new play modes..
I uninstall the previous wip and install wip 9, and also changed the 2 line to Enable.
strangely, the game doesn't load anymore.. and quit to desktop after 3 seconds.
I uninstalled the fix and it loads again..
maybe its the update??
someone experience the same thing?
there was an update to the game today which added new play modes..
I uninstall the previous wip and install wip 9, and also changed the 2 line to Enable.
strangely, the game doesn't load anymore.. and quit to desktop after 3 seconds.
I uninstalled the fix and it loads again..
maybe its the update??
someone experience the same thing?
WIP 9 crash in my pc at start: Using Steam version, win 7, 1080ti, lastest nvidia drivers. i have tried in win 10 but is the same.
WIP 8: Only can see in one eye the first time i launched, now it seems to work
Im gonna DDU the drivers and try again WIP9
Some tip?
It's definitely the update that broke the fix! Just tested it for myself with the exact same result. The game "tries" to load (you get to see the usual black window) and then (when the game normally would switch to fullscreen) the black window just disappears. After uninstalling the fix the game runs fine.
So this is good news and bad news altogether. Good news because the added "Ghost Survivors" mode seems to be quite an interesting new game-mode (and it's free). Bad news because...well, it broke the fix!
It's definitely the update that broke the fix! Just tested it for myself with the exact same result. The game "tries" to load (you get to see the usual black window) and then (when the game normally would switch to fullscreen) the black window just disappears. After uninstalling the fix the game runs fine.
So this is good news and bad news altogether. Good news because the added "Ghost Survivors" mode seems to be quite an interesting new game-mode (and it's free). Bad news because...well, it broke the fix!
[quote="lohan_0903"]It's definitely the update that broke the fix! Just tested it for myself with the exact same result. The game "tries" to load (you get to see the usual black window) and then (when the game normally would switch to fullscreen) the black window just disappears. After uninstalling the fix the game runs fine.
So this is good news and bad news altogether. Good news because the added "Ghost Survivors" mode seems to be quite an interesting new game-mode (and it's free). Bad news because...well, it broke the fix![/quote]
Thz for the info Lohan_0903!
lohan_0903 said:It's definitely the update that broke the fix! Just tested it for myself with the exact same result. The game "tries" to load (you get to see the usual black window) and then (when the game normally would switch to fullscreen) the black window just disappears. After uninstalling the fix the game runs fine.
So this is good news and bad news altogether. Good news because the added "Ghost Survivors" mode seems to be quite an interesting new game-mode (and it's free). Bad news because...well, it broke the fix!
yep, confirmed ... and wtf, I wasn't in steam for a long time ... where is the "select version" functionallity for a customer friendly downgrade ??!!!
Found this https://steamcommunity.com/sharedfiles/filedetails/?id=1086279994
... is that really the only option to downgrade?
Hey Masterotaku, thanks for the explanation of what you were looking for in the log!
I commented out those two shaders, and played through Leon A to the end.
Unfortunately, I found there is a cutscene towards the end which was broken. I checked the log and did a few test runs, and confirmed that TextureOverride_Rain_112_16 (Hash=f9fc73d4) is the culprit. After I commented that guy out, it was smooth sailing to the credits.
I've started up Claire B, so if I run into any more crashes, I'll see if I can figure them out.
Hey Masterotaku, thanks for the explanation of what you were looking for in the log!
I commented out those two shaders, and played through Leon A to the end.
Unfortunately, I found there is a cutscene towards the end which was broken. I checked the log and did a few test runs, and confirmed that TextureOverride_Rain_112_16 (Hash=f9fc73d4) is the culprit. After I commented that guy out, it was smooth sailing to the credits.
I've started up Claire B, so if I run into any more crashes, I'll see if I can figure them out.
Thank you, ZombieDog7!! I have commented that one too for the next update.
Attention, everyone: the game update broke the mod Schwing made for 3Dmigoto, and that's what makes the game crash at boot. We have to go back to "UseVendorExtention=Disable" ("UseOptimizeShader=Enable" always worked) and using the official 3Dmigoto release.
Perhaps I shouldn't have uploaded an update with an experimental mod, but at least it gave us some insight into HDR compatiblity. So from now on, until 3Dmigoto supports vendor extensions officially, we're going back to normal 3Dmigoto and "UseVendorExtention=Disable" in "re2_config.ini".
Give me a few hours to upload a new update with the fixed clipping.
Thank you, ZombieDog7!! I have commented that one too for the next update.
Attention, everyone: the game update broke the mod Schwing made for 3Dmigoto, and that's what makes the game crash at boot. We have to go back to "UseVendorExtention=Disable" ("UseOptimizeShader=Enable" always worked) and using the official 3Dmigoto release.
Perhaps I shouldn't have uploaded an update with an experimental mod, but at least it gave us some insight into HDR compatiblity. So from now on, until 3Dmigoto supports vendor extensions officially, we're going back to normal 3Dmigoto and "UseVendorExtention=Disable" in "re2_config.ini".
Give me a few hours to upload a new update with the fixed clipping.
Sorry, I am not using SLI (just a single Titan X Pascal). Unfortunately HDR is greyed-out in my ingame-settings so no way for me to activate it currently.
I tried to deactivate 3D Vision for the Alligator-scene. This time even deactivating 3D Vision was not enough. I still got a freezing-crash. Interestingly when I uninstalled the WIP9-fix and then gave it another try I didn't get a crash. After the Alligator scene everything seems fine so far...
Because in SLI, you can have up to 4 GPUs. It doesn't matter. You can set it to 2 (if you have only 2). But if you have 4way-SLI and set it to 2, only 2 will be used. If you have 2 and set it to 4, guess what ^_^ Your only 2 GPUs will be used :)
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)
That's because the resource responsible is created, stereoized when it shouldn't be, and therefore broken during the loading screen before that scene. This creates a silent killer in which your game is destined to freeze, since quitting/advancing the game triggers its destruction and that's where the freeze happens. The different cases and silent breaks make these broken resources unpredictable.
If 3D is disabled via hotkey before the loading screen, then the resource won't be stereoized. You may need to advance far enough if it's working, but idk how far. So try that and see if it helps. Also if you see d3d11_log.txt, then uploading that will help debug the crashes happening. I forget if it needs verbose debugging enabled.
---
Windows 10 x64 / 1x 980Ti GPU (no SLI, 418.81 driver) / 1920x1080
Comment them or wait for today's update. I fixed clipping for some settings combinations (subsurface scattering + contact shadows), but with others the code is different.
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
As I posted in discord, unfortunately yes. =(
Maybe I will try that SLI profile djgrege posted
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)
I uninstall the previous wip and install wip 9, and also changed the 2 line to Enable.
strangely, the game doesn't load anymore.. and quit to desktop after 3 seconds.
I uninstalled the fix and it loads again..
maybe its the update??
someone experience the same thing?
WIP 8: Only can see in one eye the first time i launched, now it seems to work
Im gonna DDU the drivers and try again WIP9
Some tip?
So this is good news and bad news altogether. Good news because the added "Ghost Survivors" mode seems to be quite an interesting new game-mode (and it's free). Bad news because...well, it broke the fix!
Thz for the info Lohan_0903!
Found this https://steamcommunity.com/sharedfiles/filedetails/?id=1086279994
... is that really the only option to downgrade?
I commented out those two shaders, and played through Leon A to the end.
Unfortunately, I found there is a cutscene towards the end which was broken. I checked the log and did a few test runs, and confirmed that TextureOverride_Rain_112_16 (Hash=f9fc73d4) is the culprit. After I commented that guy out, it was smooth sailing to the credits.
I've started up Claire B, so if I run into any more crashes, I'll see if I can figure them out.
Attention, everyone: the game update broke the mod Schwing made for 3Dmigoto, and that's what makes the game crash at boot. We have to go back to "UseVendorExtention=Disable" ("UseOptimizeShader=Enable" always worked) and using the official 3Dmigoto release.
Perhaps I shouldn't have uploaded an update with an experimental mod, but at least it gave us some insight into HDR compatiblity. So from now on, until 3Dmigoto supports vendor extensions officially, we're going back to normal 3Dmigoto and "UseVendorExtention=Disable" in "re2_config.ini".
Give me a few hours to upload a new update with the fixed clipping.
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