[quote="ddr0390"]Couldn't sleep anyway ;) I did DDU the driver but the result is the same.
When SOTTR starts 3D Vision turns on for a second. Then the game detects that StereoDefaultOn is 0 and 3D Vision gets disabled after the first flickering and stereoscopic automatically switches to "off". Even Nvidia 3DVision Photo Viewer has switched to 2D after the flickering. When I run SOTTR with stereoscopic "off", switch back to desktop and then start Photo Viewer I can't see the jps image but only a black area and 3D Vision can't be enabled. SOTTR is a real 3D Vision killer on my system :( Maybe because it's Win 7, non-SLI and only one monitor. Have to wait for a patch...
@zig11727: Thanks for the advice. I never used Tridef, so the default render is 3D Vision. As mentioned above StereoDefaultOn 0 just causes SOTTR to disable stereoscopic and 3DVision on my system. Only with StereoDefaultOn 1 I happened to run SOTTR in 3D Vision by chance but I can't reproduce it.[/quote]
Right!
Try this:
- Set it to zero.
- Start Photo Viewer. It should start. If is in 2D, press CTRL+T to activate 3D Vision.
- Start the game. If you get to the main menu and is 2D try to CTRL+T and see it 3D Vision activates and sticks!
I am a bit at a loss here on why it behaves different on your system, but since it's a timing issue, I expect something takes a different amount of time there... hence this might not work:(
ddr0390 said:Couldn't sleep anyway ;) I did DDU the driver but the result is the same.
When SOTTR starts 3D Vision turns on for a second. Then the game detects that StereoDefaultOn is 0 and 3D Vision gets disabled after the first flickering and stereoscopic automatically switches to "off". Even Nvidia 3DVision Photo Viewer has switched to 2D after the flickering. When I run SOTTR with stereoscopic "off", switch back to desktop and then start Photo Viewer I can't see the jps image but only a black area and 3D Vision can't be enabled. SOTTR is a real 3D Vision killer on my system :( Maybe because it's Win 7, non-SLI and only one monitor. Have to wait for a patch...
@zig11727: Thanks for the advice. I never used Tridef, so the default render is 3D Vision. As mentioned above StereoDefaultOn 0 just causes SOTTR to disable stereoscopic and 3DVision on my system. Only with StereoDefaultOn 1 I happened to run SOTTR in 3D Vision by chance but I can't reproduce it.
Right!
Try this:
- Set it to zero.
- Start Photo Viewer. It should start. If is in 2D, press CTRL+T to activate 3D Vision.
- Start the game. If you get to the main menu and is 2D try to CTRL+T and see it 3D Vision activates and sticks!
I am a bit at a loss here on why it behaves different on your system, but since it's a timing issue, I expect something takes a different amount of time there... hence this might not work:(
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
Thank You for Your advice :)
Unfortunately it still doesn't work. After using CRTL+T (or in game settings) there is an initial flickering that enables 3D Vision but then it gets disabled again (also for Photo Viewer) and there are no more trials to enable it (no permanent flickering as with StereoDefaultOn 1). Also tried 3D Vision Discovery as switching to anaglyph mode should be faster than enabling the IR emitter and synchronizing the glasses. But the same result.
Obviously I have bad luck with the timing on my PC. Maybe Yours is faster so the switching on/off finally sticks to "on" whereas on my slower PC it has enough time to switch to "off" again and stick there.
Thank You for Your advice :)
Unfortunately it still doesn't work. After using CRTL+T (or in game settings) there is an initial flickering that enables 3D Vision but then it gets disabled again (also for Photo Viewer) and there are no more trials to enable it (no permanent flickering as with StereoDefaultOn 1). Also tried 3D Vision Discovery as switching to anaglyph mode should be faster than enabling the IR emitter and synchronizing the glasses. But the same result.
Obviously I have bad luck with the timing on my PC. Maybe Yours is faster so the switching on/off finally sticks to "on" whereas on my slower PC it has enough time to switch to "off" again and stick there.
My original display name is 3d4dd - for some reason Nvidia changed it..?!
I'm having pretty much the same issue as you ddr0390.
Mine also works by chance once in a while. Right now, this is the procedure I'm following to get it working.
1. Start the game with Exclusive Full Screen OFF and Stereoscopic OFF.
2. Toggle both the above settings to ON within the game. If this works fine, you're good to go, else continue to step 3.
3. If the enable/disable loop begins, ALT + TAB out of the game or CTRL + ALT + DEL to open task manager.
4. Wait for a few seconds till the game reverts back to previous settings.
5. Go back to into the game and start over from step 2 till you get lucky.
I really hope this gets fixed soon either by Nvidia or SOTTR devs.
The game also crashes often in DX11 in the Peruvian Jungle and The Hidden City regions every now and then.
Hope that gets addressed as well. Anyone else having crashes in these regions?
My system specs:
Hardware:
CPU: Core i7 8700K @ stock
Mobo: Asus Z370-E Gaming
RAM: 32 GB (4x8GB) G.Skill 3200MHz CL16
GPU: 2 x GTX 1080 (MSI Gaming X) @ stock
Software:
OS: Windows 10 Pro 64-bit Build 17134
Nvidia Driver version: 399.24
I'm having pretty much the same issue as you ddr0390.
Mine also works by chance once in a while. Right now, this is the procedure I'm following to get it working.
1. Start the game with Exclusive Full Screen OFF and Stereoscopic OFF.
2. Toggle both the above settings to ON within the game. If this works fine, you're good to go, else continue to step 3.
3. If the enable/disable loop begins, ALT + TAB out of the game or CTRL + ALT + DEL to open task manager.
4. Wait for a few seconds till the game reverts back to previous settings.
5. Go back to into the game and start over from step 2 till you get lucky.
I really hope this gets fixed soon either by Nvidia or SOTTR devs.
The game also crashes often in DX11 in the Peruvian Jungle and The Hidden City regions every now and then.
Hope that gets addressed as well. Anyone else having crashes in these regions?
My system specs:
Hardware:
CPU: Core i7 8700K @ stock
Mobo: Asus Z370-E Gaming
RAM: 32 GB (4x8GB) G.Skill 3200MHz CL16
GPU: 2 x GTX 1080 (MSI Gaming X) @ stock
Software:
OS: Windows 10 Pro 64-bit Build 17134
Nvidia Driver version: 399.24
i7 8700K, Asus Z370-E Gaming, 32 GB RAM, MSI RTX 2080 Ti Gaming X Trio.
I can confirm those crashes:) For me is mostly in the Hidden City, sometimes after 10 minutes or so.
Do you use the SLI bits posted in the profile or is this with a default profile?
I can confirm those crashes:) For me is mostly in the Hidden City, sometimes after 10 minutes or so.
Do you use the SLI bits posted in the profile or is this with a default profile?
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="invisiblearrow"]I'm having pretty much the same issue as you ddr0390.
Mine also works by chance once in a while. Right now, this is the procedure I'm following to get it working.
1. Start the game with Exclusive Full Screen OFF and Stereoscopic OFF.
2. Toggle both the above settings to ON within the game. If this works fine, you're good to go, else continue to step 3.
3. If the enable/disable loop begins, ALT + TAB out of the game or CTRL + ALT + DEL to open task manager.
4. Wait for a few seconds till the game reverts back to previous settings.
5. Go back to into the game and start over from step 2 till you get lucky.
[/quote]
Me too, same issue of ddr0390.
With this method of "invisiblearrow" sometimes im lucky and the game work in 3dvision.
The problem for me is the Sli, if i disable Sli the method of Helifax work fine everytime, and the game start directly in 3dvision.. and in 3d this game is increeedibleee!!!
Another strange things are the FPS, with the game maxed i have 30/50 fps in sli and 30/50 with 1 1080ti at 1440p, i tried helifax profile, sli bit of Rise of tomb raider but nothing, same fps... with msi afterburner i see Sli scaling good..
invisiblearrow said:I'm having pretty much the same issue as you ddr0390.
Mine also works by chance once in a while. Right now, this is the procedure I'm following to get it working.
1. Start the game with Exclusive Full Screen OFF and Stereoscopic OFF.
2. Toggle both the above settings to ON within the game. If this works fine, you're good to go, else continue to step 3.
3. If the enable/disable loop begins, ALT + TAB out of the game or CTRL + ALT + DEL to open task manager.
4. Wait for a few seconds till the game reverts back to previous settings.
5. Go back to into the game and start over from step 2 till you get lucky.
Me too, same issue of ddr0390.
With this method of "invisiblearrow" sometimes im lucky and the game work in 3dvision.
The problem for me is the Sli, if i disable Sli the method of Helifax work fine everytime, and the game start directly in 3dvision.. and in 3d this game is increeedibleee!!!
Another strange things are the FPS, with the game maxed i have 30/50 fps in sli and 30/50 with 1 1080ti at 1440p, i tried helifax profile, sli bit of Rise of tomb raider but nothing, same fps... with msi afterburner i see Sli scaling good..
@invisiblearrow:
Yes, this is the way I managed to get 3D Vision running by chance. But I don't want try it any more as I fear that it might harm the hardware. I still hope that Nixxes will take a look at this bug and doesn't regard the workaround that helps some/many lucky guys as the final solution.
BTW I tried something else regarding this possible timing issue. For many actual games I'm overclocking my CPU (and sometimes GPU). But I decided to try the workaround with the default settings for my hardware. And indeed it happened more often that there was only one flickering, 3D Vision running and stereoscopic on - but the game only displayed the image for one eye! I wasn't just 2D as changing the depth settings moved the image to the left/right. Changing stereoscopic, frequency or resolution didn't have any effect. It asked for confirmation but didn't change anything. So also in this case the detection of the hardware status didn't work. Using the lowest graphic settings and minimum resolution didn't help.
But maybe it helps others to disable any overclocking settings...
@invisiblearrow:
Yes, this is the way I managed to get 3D Vision running by chance. But I don't want try it any more as I fear that it might harm the hardware. I still hope that Nixxes will take a look at this bug and doesn't regard the workaround that helps some/many lucky guys as the final solution.
BTW I tried something else regarding this possible timing issue. For many actual games I'm overclocking my CPU (and sometimes GPU). But I decided to try the workaround with the default settings for my hardware. And indeed it happened more often that there was only one flickering, 3D Vision running and stereoscopic on - but the game only displayed the image for one eye! I wasn't just 2D as changing the depth settings moved the image to the left/right. Changing stereoscopic, frequency or resolution didn't have any effect. It asked for confirmation but didn't change anything. So also in this case the detection of the hardware status didn't work. Using the lowest graphic settings and minimum resolution didn't help.
But maybe it helps others to disable any overclocking settings...
My original display name is 3d4dd - for some reason Nvidia changed it..?!
[quote="Helifax"]I can confirm those crashes:) For me is mostly in the Hidden City, sometimes after 10 minutes or so.
Do you use the SLI bits posted in the profile or is this with a default profile?[/quote]
I used the SLI bits posted in the link you mentioned. Default profile didn't utilize the 2nd GPU at all.
The scaling is pretty good in most regions (managed to get 60 FPS) except in heavily populated regions, where the usage on both GPUs drops into 50%-60% range and the FPS drops to 30s. Perhaps it's one of the problems with using SLI when the GPUs are on x8/x8 PCIe lanes since I'm on a Z370 board.
BTW guys, I have an update on the 3D vision on/off loop problem.
I decided to run Rise of the Tomb Raider to compare it with Shadow of the Tomb Raider.
And guess what, I got the same problem with Rise of the Tomb Raider. I know for a fact that ROTTR was working perfectly fine before, so I guessed it must be a driver issue.
So, I rolled back to driver version 385.69 which I knew worked well with ROTTR.
Now, both ROTTR and SOTTR work well without the 3D vision on/off problem at startup.
ddr0390, give this a try and see if it fixes things on your setup as well.
On another note, Witcher 3 has a weird hairworks bug with most of the recent drivers as mentioned here:
https://forums.geforce.com/default/topic/1058926/geforce-drivers/hairworks-bug-in-last-month-drivers/1/
Looks like 385.69 was the last good driver for everyone on SLI and/or 3D Vision setups.
Helifax said:I can confirm those crashes:) For me is mostly in the Hidden City, sometimes after 10 minutes or so.
Do you use the SLI bits posted in the profile or is this with a default profile?
I used the SLI bits posted in the link you mentioned. Default profile didn't utilize the 2nd GPU at all.
The scaling is pretty good in most regions (managed to get 60 FPS) except in heavily populated regions, where the usage on both GPUs drops into 50%-60% range and the FPS drops to 30s. Perhaps it's one of the problems with using SLI when the GPUs are on x8/x8 PCIe lanes since I'm on a Z370 board.
BTW guys, I have an update on the 3D vision on/off loop problem.
I decided to run Rise of the Tomb Raider to compare it with Shadow of the Tomb Raider.
And guess what, I got the same problem with Rise of the Tomb Raider. I know for a fact that ROTTR was working perfectly fine before, so I guessed it must be a driver issue.
So, I rolled back to driver version 385.69 which I knew worked well with ROTTR.
Now, both ROTTR and SOTTR work well without the 3D vision on/off problem at startup.
ddr0390, give this a try and see if it fixes things on your setup as well.
[quote="invisiblearrow"][quote="Helifax"]I can confirm those crashes:) For me is mostly in the Hidden City, sometimes after 10 minutes or so.
Do you use the SLI bits posted in the profile or is this with a default profile?[/quote]
I used the SLI bits posted in the link you mentioned. Default profile didn't utilize the 2nd GPU at all.
The scaling is pretty good in most regions (managed to get 60 FPS) except in heavily populated regions, where the usage on both GPUs drops into 50%-60% range and the FPS drops to 30s. Perhaps it's one of the problems with using SLI when the GPUs are on x8/x8 PCIe lanes since I'm on a Z370 board.
BTW guys, I have an update on the 3D vision on/off loop problem.
I decided to run Rise of the Tomb Raider to compare it with Shadow of the Tomb Raider.
And guess what, I got the same problem with Rise of the Tomb Raider. I know for a fact that ROTTR was working perfectly fine before, so I guessed it must be a driver issue.
So, I rolled back to driver version 385.69 which I knew worked well with ROTTR.
Now, both ROTTR and SOTTR work well without the 3D vision on/off problem at startup.
ddr0390, give this a try and see if it fixes things on your setup as well.
On another note, Witcher 3 has a weird hairworks bug with most of the recent drivers as mentioned here:
https://forums.geforce.com/default/topic/1058926/geforce-drivers/hairworks-bug-in-last-month-drivers/1/
Looks like 385.69 was the last good driver for everyone on SLI and/or 3D Vision setups.[/quote]
Many interesting things there! Many thanks for sharing this!
On my Laptop (single 880M - single Monitor) I get the SOTTR 3D Vision bug. My provided workaround seems to work only at 1920x1080 but not at any other resolution :-s
I will give those drivers a go! Many thanks again!
Helifax said:I can confirm those crashes:) For me is mostly in the Hidden City, sometimes after 10 minutes or so.
Do you use the SLI bits posted in the profile or is this with a default profile?
I used the SLI bits posted in the link you mentioned. Default profile didn't utilize the 2nd GPU at all.
The scaling is pretty good in most regions (managed to get 60 FPS) except in heavily populated regions, where the usage on both GPUs drops into 50%-60% range and the FPS drops to 30s. Perhaps it's one of the problems with using SLI when the GPUs are on x8/x8 PCIe lanes since I'm on a Z370 board.
BTW guys, I have an update on the 3D vision on/off loop problem.
I decided to run Rise of the Tomb Raider to compare it with Shadow of the Tomb Raider.
And guess what, I got the same problem with Rise of the Tomb Raider. I know for a fact that ROTTR was working perfectly fine before, so I guessed it must be a driver issue.
So, I rolled back to driver version 385.69 which I knew worked well with ROTTR.
Now, both ROTTR and SOTTR work well without the 3D vision on/off problem at startup.
ddr0390, give this a try and see if it fixes things on your setup as well.
Looks like 385.69 was the last good driver for everyone on SLI and/or 3D Vision setups.
Many interesting things there! Many thanks for sharing this!
On my Laptop (single 880M - single Monitor) I get the SOTTR 3D Vision bug. My provided workaround seems to work only at 1920x1080 but not at any other resolution :-s
I will give those drivers a go! Many thanks again!
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="ddr0390"]
Anyone tried to run the game with a Nvidia driver that was actual when ROTTR got the 3D patch and use the ROTTR profile for SOTTR? Maybe something changed in the drivers so the handling of enabling/disabling 3D Vision by a game doesn't work the way it was for ROTTR. Does ROTTR still work correctly with the actual driver (I don't have ROTTR installed ATM)? Just an idea, can't try it now by myself, have to go to bed...[/quote]
[quote="Blacksmith56"]ROTTR is still working allmost perfect, with recent drivers :)[/quote]
For this reason I didn't try other driver versions.
As I had driver 382.53 still extracted on my system I tried SOTTR with this version. Unfortunately the flickering occured as always. Tried the imported .nib for SOTTR and also added SOTTR to the ROTTR profile but it made no difference.
ddr0390 said:
Anyone tried to run the game with a Nvidia driver that was actual when ROTTR got the 3D patch and use the ROTTR profile for SOTTR? Maybe something changed in the drivers so the handling of enabling/disabling 3D Vision by a game doesn't work the way it was for ROTTR. Does ROTTR still work correctly with the actual driver (I don't have ROTTR installed ATM)? Just an idea, can't try it now by myself, have to go to bed...
Blacksmith56 said:ROTTR is still working allmost perfect, with recent drivers :)
For this reason I didn't try other driver versions.
As I had driver 382.53 still extracted on my system I tried SOTTR with this version. Unfortunately the flickering occured as always. Tried the imported .nib for SOTTR and also added SOTTR to the ROTTR profile but it made no difference.
My original display name is 3d4dd - for some reason Nvidia changed it..?!
[quote="ddr0390"][quote="ddr0390"]
Anyone tried to run the game with a Nvidia driver that was actual when ROTTR got the 3D patch and use the ROTTR profile for SOTTR? Maybe something changed in the drivers so the handling of enabling/disabling 3D Vision by a game doesn't work the way it was for ROTTR. Does ROTTR still work correctly with the actual driver (I don't have ROTTR installed ATM)? Just an idea, can't try it now by myself, have to go to bed...[/quote]
[quote="Blacksmith56"]ROTTR is still working allmost perfect, with recent drivers :)[/quote]
For this reason I didn't try other driver versions.
As I had driver 382.53 still extracted on my system I tried SOTTR with this version. Unfortunately the flickering occured as always. Tried the imported .nib for SOTTR and also added SOTTR to the ROTTR profile but it made no difference.[/quote]
Hmm, this is a pretty strange problem indeed. I might have just gotten lucky somehow with my driver rollback.
I can however confirm that the new driver (399.24) broke ROTTR 3D Vision as well. Had the same flickering problem as SOTTR. One other thing I did notice with driver 399.24 with ROTTR is that the splash screen (where the brand logos appear) took 3-5 seconds to come up even with 3D vision turned off. On 385.69, this screen loads up almost instantaneously with 3D Vision on or off. SOTTR also takes longer to load up initially with 399.24, but even with the older driver, it isn't instantaneous as ROTTR. I have a feeling that the delay in startup here might be causing the problem as others have suggested in some of the previous replies.
I'm wondering if loading up another non-resource intensive 3D app (like Trine 1 or 3D vision photo viewer) in the background first will help. I guess you've already tried that, but just mentioning it again.
ddr0390 said:
Anyone tried to run the game with a Nvidia driver that was actual when ROTTR got the 3D patch and use the ROTTR profile for SOTTR? Maybe something changed in the drivers so the handling of enabling/disabling 3D Vision by a game doesn't work the way it was for ROTTR. Does ROTTR still work correctly with the actual driver (I don't have ROTTR installed ATM)? Just an idea, can't try it now by myself, have to go to bed...
Blacksmith56 said:ROTTR is still working allmost perfect, with recent drivers :)
For this reason I didn't try other driver versions.
As I had driver 382.53 still extracted on my system I tried SOTTR with this version. Unfortunately the flickering occured as always. Tried the imported .nib for SOTTR and also added SOTTR to the ROTTR profile but it made no difference.
Hmm, this is a pretty strange problem indeed. I might have just gotten lucky somehow with my driver rollback.
I can however confirm that the new driver (399.24) broke ROTTR 3D Vision as well. Had the same flickering problem as SOTTR. One other thing I did notice with driver 399.24 with ROTTR is that the splash screen (where the brand logos appear) took 3-5 seconds to come up even with 3D vision turned off. On 385.69, this screen loads up almost instantaneously with 3D Vision on or off. SOTTR also takes longer to load up initially with 399.24, but even with the older driver, it isn't instantaneous as ROTTR. I have a feeling that the delay in startup here might be causing the problem as others have suggested in some of the previous replies.
I'm wondering if loading up another non-resource intensive 3D app (like Trine 1 or 3D vision photo viewer) in the background first will help. I guess you've already tried that, but just mentioning it again.
i7 8700K, Asus Z370-E Gaming, 32 GB RAM, MSI RTX 2080 Ti Gaming X Trio.
It's really strange. I had Rise working properly on 399.07, but rolled back to 384.76 to see if I would have better luck with Shadow. Neither Rise or Shadow would engage 3DV properly in 384.76 and Rise started crashing any time that it was activated, both in-game and in the launcher.
So, I went back to 399.07 - same problems as have been reported with Shadow - and Rise now crashes (black screen) in 3DV any time it is activated (crashes to black right after the intial loading/logo screen.)
It's really strange. I had Rise working properly on 399.07, but rolled back to 384.76 to see if I would have better luck with Shadow. Neither Rise or Shadow would engage 3DV properly in 384.76 and Rise started crashing any time that it was activated, both in-game and in the launcher.
So, I went back to 399.07 - same problems as have been reported with Shadow - and Rise now crashes (black screen) in 3DV any time it is activated (crashes to black right after the intial loading/logo screen.)
Although I was pretty satisfied with the visuals in side-by-side 3D mode it definitely bothered me that I was not able to get 3D Vision running for this game on my LG 4K OLED.
So I fiddled around a little more with settings and drivers and FINALLY had success! Using driver 398.82 there is absolutely no back-and-forth switching and the game simply launches in beautifully stunning 3D Vision.
Sliders may be messed up. For me both 3D-related sliders were set to max which definitely breaks the stereoscopic view but with depth-slider at 50% and pop-out slider still maxed the game just looks stunning.
I don't know how long the above stays valid but I launched the game several times and every single time the game launched in 3D Vision without any issues!
I will post this in both SOTTR-related threads as the switching issue has been discussed in both of them.
@ddr0390
You definitely should give driver 398.82 a try since your reported issue seemed to be identical with mine.....
Although I was pretty satisfied with the visuals in side-by-side 3D mode it definitely bothered me that I was not able to get 3D Vision running for this game on my LG 4K OLED.
So I fiddled around a little more with settings and drivers and FINALLY had success! Using driver 398.82 there is absolutely no back-and-forth switching and the game simply launches in beautifully stunning 3D Vision.
Sliders may be messed up. For me both 3D-related sliders were set to max which definitely breaks the stereoscopic view but with depth-slider at 50% and pop-out slider still maxed the game just looks stunning.
I don't know how long the above stays valid but I launched the game several times and every single time the game launched in 3D Vision without any issues!
I will post this in both SOTTR-related threads as the switching issue has been discussed in both of them.
@ddr0390
You definitely should give driver 398.82 a try since your reported issue seemed to be identical with mine.....
[quote="TheBigDogma"]It's really strange. I had Rise working properly on 399.07, but rolled back to 384.76 to see if I would have better luck with Shadow. Neither Rise or Shadow would engage 3DV properly in 384.76 and Rise started crashing any time that it was activated, both in-game and in the launcher.
So, I went back to 399.07 - same problems as have been reported with Shadow - and Rise now crashes (black screen) in 3DV any time it is activated (crashes to black right after the intial loading/logo screen.)[/quote]
I would go and Delete the Registry keys! (Regedit.exe) Don't worry the game will generate new one on next launch! I bet there is something there that breaks things!
(MAKE A BACKUP just in case ^_^)
I am currently investigating a crash in 3D Surround + SLI, as there is something wrong with the SLI profile (provided above) in 3D Vision + 3D Surround (the display driver crashes).
SLI works in this game flawless in 2D, but Nvidia didn't bother to add it. As a matter of fact, they force everything on one GPU in their latest driver update... I honestly don't understand it, but oh well...
Now, I only need to see about 3D Vision in Surround - where everything stressed to the max ofc...
TheBigDogma said:It's really strange. I had Rise working properly on 399.07, but rolled back to 384.76 to see if I would have better luck with Shadow. Neither Rise or Shadow would engage 3DV properly in 384.76 and Rise started crashing any time that it was activated, both in-game and in the launcher.
So, I went back to 399.07 - same problems as have been reported with Shadow - and Rise now crashes (black screen) in 3DV any time it is activated (crashes to black right after the intial loading/logo screen.)
I would go and Delete the Registry keys! (Regedit.exe) Don't worry the game will generate new one on next launch! I bet there is something there that breaks things!
(MAKE A BACKUP just in case ^_^)
I am currently investigating a crash in 3D Surround + SLI, as there is something wrong with the SLI profile (provided above) in 3D Vision + 3D Surround (the display driver crashes).
SLI works in this game flawless in 2D, but Nvidia didn't bother to add it. As a matter of fact, they force everything on one GPU in their latest driver update... I honestly don't understand it, but oh well...
Now, I only need to see about 3D Vision in Surround - where everything stressed to the max ofc...
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
Thanks Helifax,
Turns out that the problem with Rise was rectified by lowering the graphic settings - still strange because I had never changed the graphic settings since making the initial changes upon the game's release.
The syncing issue for Shadow obviously remains. At this point, I (we) probably just need to be patient and trust that Nixxes will continue updating/fixing/patching and do the good work that they've always done.
Turns out that the problem with Rise was rectified by lowering the graphic settings - still strange because I had never changed the graphic settings since making the initial changes upon the game's release.
The syncing issue for Shadow obviously remains. At this point, I (we) probably just need to be patient and trust that Nixxes will continue updating/fixing/patching and do the good work that they've always done.
Right!
Try this:
- Set it to zero.
- Start Photo Viewer. It should start. If is in 2D, press CTRL+T to activate 3D Vision.
- Start the game. If you get to the main menu and is 2D try to CTRL+T and see it 3D Vision activates and sticks!
I am a bit at a loss here on why it behaves different on your system, but since it's a timing issue, I expect something takes a different amount of time there... hence this might not work:(
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)
Unfortunately it still doesn't work. After using CRTL+T (or in game settings) there is an initial flickering that enables 3D Vision but then it gets disabled again (also for Photo Viewer) and there are no more trials to enable it (no permanent flickering as with StereoDefaultOn 1). Also tried 3D Vision Discovery as switching to anaglyph mode should be faster than enabling the IR emitter and synchronizing the glasses. But the same result.
Obviously I have bad luck with the timing on my PC. Maybe Yours is faster so the switching on/off finally sticks to "on" whereas on my slower PC it has enough time to switch to "off" again and stick there.
My original display name is 3d4dd - for some reason Nvidia changed it..?!
Mine also works by chance once in a while. Right now, this is the procedure I'm following to get it working.
1. Start the game with Exclusive Full Screen OFF and Stereoscopic OFF.
2. Toggle both the above settings to ON within the game. If this works fine, you're good to go, else continue to step 3.
3. If the enable/disable loop begins, ALT + TAB out of the game or CTRL + ALT + DEL to open task manager.
4. Wait for a few seconds till the game reverts back to previous settings.
5. Go back to into the game and start over from step 2 till you get lucky.
I really hope this gets fixed soon either by Nvidia or SOTTR devs.
The game also crashes often in DX11 in the Peruvian Jungle and The Hidden City regions every now and then.
Hope that gets addressed as well. Anyone else having crashes in these regions?
My system specs:
Hardware:
CPU: Core i7 8700K @ stock
Mobo: Asus Z370-E Gaming
RAM: 32 GB (4x8GB) G.Skill 3200MHz CL16
GPU: 2 x GTX 1080 (MSI Gaming X) @ stock
Software:
OS: Windows 10 Pro 64-bit Build 17134
Nvidia Driver version: 399.24
i7 8700K, Asus Z370-E Gaming, 32 GB RAM, MSI RTX 2080 Ti Gaming X Trio.
Do you use the SLI bits posted in the profile or is this with a default profile?
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)
Me too, same issue of ddr0390.
With this method of "invisiblearrow" sometimes im lucky and the game work in 3dvision.
The problem for me is the Sli, if i disable Sli the method of Helifax work fine everytime, and the game start directly in 3dvision.. and in 3d this game is increeedibleee!!!
Another strange things are the FPS, with the game maxed i have 30/50 fps in sli and 30/50 with 1 1080ti at 1440p, i tried helifax profile, sli bit of Rise of tomb raider but nothing, same fps... with msi afterburner i see Sli scaling good..
2x GTX 1080Ti Founders edition
Monitor Asus PG278QE 3D Vision 2
Monitor Philips 4k 40 BDM4065UC
i7 4790K @ 5.0Ghz
DDR3 Dominator 32GB 1866
2 RAID0 256GB SSDs
2 RAID0 1TB Mechanical HDD (WD Black)
-
Yes, this is the way I managed to get 3D Vision running by chance. But I don't want try it any more as I fear that it might harm the hardware. I still hope that Nixxes will take a look at this bug and doesn't regard the workaround that helps some/many lucky guys as the final solution.
BTW I tried something else regarding this possible timing issue. For many actual games I'm overclocking my CPU (and sometimes GPU). But I decided to try the workaround with the default settings for my hardware. And indeed it happened more often that there was only one flickering, 3D Vision running and stereoscopic on - but the game only displayed the image for one eye! I wasn't just 2D as changing the depth settings moved the image to the left/right. Changing stereoscopic, frequency or resolution didn't have any effect. It asked for confirmation but didn't change anything. So also in this case the detection of the hardware status didn't work. Using the lowest graphic settings and minimum resolution didn't help.
But maybe it helps others to disable any overclocking settings...
My original display name is 3d4dd - for some reason Nvidia changed it..?!
I used the SLI bits posted in the link you mentioned. Default profile didn't utilize the 2nd GPU at all.
The scaling is pretty good in most regions (managed to get 60 FPS) except in heavily populated regions, where the usage on both GPUs drops into 50%-60% range and the FPS drops to 30s. Perhaps it's one of the problems with using SLI when the GPUs are on x8/x8 PCIe lanes since I'm on a Z370 board.
BTW guys, I have an update on the 3D vision on/off loop problem.
I decided to run Rise of the Tomb Raider to compare it with Shadow of the Tomb Raider.
And guess what, I got the same problem with Rise of the Tomb Raider. I know for a fact that ROTTR was working perfectly fine before, so I guessed it must be a driver issue.
So, I rolled back to driver version 385.69 which I knew worked well with ROTTR.
Now, both ROTTR and SOTTR work well without the 3D vision on/off problem at startup.
ddr0390, give this a try and see if it fixes things on your setup as well.
On another note, Witcher 3 has a weird hairworks bug with most of the recent drivers as mentioned here:
https://forums.geforce.com/default/topic/1058926/geforce-drivers/hairworks-bug-in-last-month-drivers/1/
Looks like 385.69 was the last good driver for everyone on SLI and/or 3D Vision setups.
i7 8700K, Asus Z370-E Gaming, 32 GB RAM, MSI RTX 2080 Ti Gaming X Trio.
Many interesting things there! Many thanks for sharing this!
On my Laptop (single 880M - single Monitor) I get the SOTTR 3D Vision bug. My provided workaround seems to work only at 1920x1080 but not at any other resolution :-s
I will give those drivers a go! Many thanks again!
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)
For this reason I didn't try other driver versions.
As I had driver 382.53 still extracted on my system I tried SOTTR with this version. Unfortunately the flickering occured as always. Tried the imported .nib for SOTTR and also added SOTTR to the ROTTR profile but it made no difference.
My original display name is 3d4dd - for some reason Nvidia changed it..?!
Hmm, this is a pretty strange problem indeed. I might have just gotten lucky somehow with my driver rollback.
I can however confirm that the new driver (399.24) broke ROTTR 3D Vision as well. Had the same flickering problem as SOTTR. One other thing I did notice with driver 399.24 with ROTTR is that the splash screen (where the brand logos appear) took 3-5 seconds to come up even with 3D vision turned off. On 385.69, this screen loads up almost instantaneously with 3D Vision on or off. SOTTR also takes longer to load up initially with 399.24, but even with the older driver, it isn't instantaneous as ROTTR. I have a feeling that the delay in startup here might be causing the problem as others have suggested in some of the previous replies.
I'm wondering if loading up another non-resource intensive 3D app (like Trine 1 or 3D vision photo viewer) in the background first will help. I guess you've already tried that, but just mentioning it again.
i7 8700K, Asus Z370-E Gaming, 32 GB RAM, MSI RTX 2080 Ti Gaming X Trio.
So, I went back to 399.07 - same problems as have been reported with Shadow - and Rise now crashes (black screen) in 3DV any time it is activated (crashes to black right after the intial loading/logo screen.)
So I fiddled around a little more with settings and drivers and FINALLY had success! Using driver 398.82 there is absolutely no back-and-forth switching and the game simply launches in beautifully stunning 3D Vision.
Sliders may be messed up. For me both 3D-related sliders were set to max which definitely breaks the stereoscopic view but with depth-slider at 50% and pop-out slider still maxed the game just looks stunning.
I don't know how long the above stays valid but I launched the game several times and every single time the game launched in 3D Vision without any issues!
I will post this in both SOTTR-related threads as the switching issue has been discussed in both of them.
@ddr0390
You definitely should give driver 398.82 a try since your reported issue seemed to be identical with mine.....
I would go and Delete the Registry keys! (Regedit.exe) Don't worry the game will generate new one on next launch! I bet there is something there that breaks things!
(MAKE A BACKUP just in case ^_^)
I am currently investigating a crash in 3D Surround + SLI, as there is something wrong with the SLI profile (provided above) in 3D Vision + 3D Surround (the display driver crashes).
SLI works in this game flawless in 2D, but Nvidia didn't bother to add it. As a matter of fact, they force everything on one GPU in their latest driver update... I honestly don't understand it, but oh well...
Now, I only need to see about 3D Vision in Surround - where everything stressed to the max ofc...
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)
Turns out that the problem with Rise was rectified by lowering the graphic settings - still strange because I had never changed the graphic settings since making the initial changes upon the game's release.
The syncing issue for Shadow obviously remains. At this point, I (we) probably just need to be patient and trust that Nixxes will continue updating/fixing/patching and do the good work that they've always done.