Every time I reboot settings default to 3D Vision Discover!
  3 / 6    
Try going to power options in the control panel, in the advanced settings, set USB selective suspend setting to "Disabled"
Try going to power options in the control panel, in the advanced settings, set USB selective suspend setting to "Disabled"

#31
Posted 04/21/2015 09:29 PM   
I'll drop this here in case anyone watching this thread wants to give this a try for me so we can find out which settings are being changed in the registry on reboot ... if I know what settings are changing on you guys then I should be able to come up with something at least for the rebooting issue. [quote="TsaebehT"]I don't think there's a way to remove it but there may be a way to create a task that runs on startup to set it back to your original settings, try this for me save the following code as Settings.bat and when your 3D is setup properly run it, it'll spit all the 3D settings out to a file, then reboot and run it again and it'll spit out any differences in the Stereo3D reg key to SettDiff.txt so we can see what's changing. [code]@Echo Off SetLocal EnableDelayedExpansion if Exist "%PROGRAMFILES(X86)%" Set $Wow=Wow6432Node\ Set $Key="HKLM\SOFTWARE\!$Wow!NVIDIA Corporation\Global\Stereo3D" if Exist Settings.txt ( For /F %%? in (Settings.txt) do (Set "%%?") > SettDiffs.txt ( For /F "tokens=1,3" %%? in ('Reg Query !$Key!^|Findstr REG_') do ( if "!%%?!" NEQ "%%@" Echo %%?=!%%?!,%%@ ))) else ( > Settings.txt ( For /F "tokens=1,3" %%? in ('Reg Query !$Key!^|Findstr REG_') do ( if "%%@" NEQ "" ( Echo %%?=%%@ ))))[/code] [/quote]
I'll drop this here in case anyone watching this thread wants to give this a try for me so we can find out which settings are being changed in the registry on reboot ... if I know what settings are changing on you guys then I should be able to come up with something at least for the rebooting issue.

TsaebehT said:I don't think there's a way to remove it but there may be a way to create a task that runs on startup to set it back to your original settings, try this for me save the following code as Settings.bat and when your 3D is setup properly run it, it'll spit all the 3D settings out to a file, then reboot and run it again and it'll spit out any differences in the Stereo3D reg key to SettDiff.txt so we can see what's changing.

@Echo Off
SetLocal EnableDelayedExpansion
if Exist "%PROGRAMFILES(X86)%" Set $Wow=Wow6432Node\
Set $Key="HKLM\SOFTWARE\!$Wow!NVIDIA Corporation\Global\Stereo3D"
if Exist Settings.txt (
For /F %%? in (Settings.txt) do (Set "%%?")
> SettDiffs.txt (
For /F "tokens=1,3" %%? in ('Reg Query !$Key!^|Findstr REG_') do (
if "!%%?!" NEQ "%%@" Echo %%?=!%%?!,%%@
))) else (
> Settings.txt (
For /F "tokens=1,3" %%? in ('Reg Query !$Key!^|Findstr REG_') do (
if "%%@" NEQ "" (
Echo %%?=%%@
))))

#32
Posted 04/22/2015 03:23 PM   
Hello TsaebehT, I still have this problem so I ran your batch file. SettDiffs.txt StereoViewerType=0x1,0x80000001 and Settings.txt DrsEnable=0x1 StereoAdjustEnable=0x1 StereoToggle=0x254 StereoSeparationAdjustLess=0x272 StereoSeparationAdjustMore=0x273 StereoConvergenceAdjustMore=0x275 StereoConvergenceAdjustLess=0x274 WriteConfig=0x276 DeleteConfig=0x476 ToggleAutoConvergence=0x277 ToggleAutoConvergenceRestore=0x477 RHWAtScreenLess=0x278 RHWAtScreenMore=0x279 RHWLessAtScreenLess=0x478 RHWLessAtScreenMore=0x479 StereoSuggestSettings=0x271 ToggleLaserSight=0x27b StereoUnsuggestSettings=0x471 CycleFrustumAdjust=0x27a SaveStereoImage=0x470 LaserSightEnabled=0x1 LaserSightProperty=0xf004b064 LaserSightIndex=0x0 LaserSightFile=DLL:0 StereoDisableTnL=0x0 SnapShotQuality=0x32 [u][b]StereoViewerType=0x1[/b][/u] StereoSeparation=0x64 StereoDefaultOn=0x1 ControlPanel=0x0 GammaAdjustMore=0x247 GammaAdjustLess=0x447 AnaglyphEnabled=0xdeadbeef LeftAnaglyphFilter=0xffff0000 RightAnaglyphFilter=0xff00ffff StereoGamma=0x3f800000 ShowAllViewerTypes=0x1 GlassesSwitchDelay=0x0 GlassesDelayPlus=0x4bb GlassesDelayMinus=0x4bd ToggleMemo=0xe2d EnableWindowedMode=0x5 Time=0x55254758 MonitorSize=0x36 StereoMonitorID=0x27e36904 StereoAnaglyphType=0x1 StereoDefaultONSet=0x1 StereoTypeSet=0x1 StereoVisionConfirmed=0x1 Thanks for your time.
Hello TsaebehT,

I still have this problem so I ran your batch file.

SettDiffs.txt

StereoViewerType=0x1,0x80000001


and Settings.txt

DrsEnable=0x1
StereoAdjustEnable=0x1
StereoToggle=0x254
StereoSeparationAdjustLess=0x272
StereoSeparationAdjustMore=0x273
StereoConvergenceAdjustMore=0x275
StereoConvergenceAdjustLess=0x274
WriteConfig=0x276
DeleteConfig=0x476
ToggleAutoConvergence=0x277
ToggleAutoConvergenceRestore=0x477
RHWAtScreenLess=0x278
RHWAtScreenMore=0x279
RHWLessAtScreenLess=0x478
RHWLessAtScreenMore=0x479
StereoSuggestSettings=0x271
ToggleLaserSight=0x27b
StereoUnsuggestSettings=0x471
CycleFrustumAdjust=0x27a
SaveStereoImage=0x470
LaserSightEnabled=0x1
LaserSightProperty=0xf004b064
LaserSightIndex=0x0
LaserSightFile=DLL:0
StereoDisableTnL=0x0
SnapShotQuality=0x32
StereoViewerType=0x1
StereoSeparation=0x64
StereoDefaultOn=0x1
ControlPanel=0x0
GammaAdjustMore=0x247
GammaAdjustLess=0x447
AnaglyphEnabled=0xdeadbeef
LeftAnaglyphFilter=0xffff0000
RightAnaglyphFilter=0xff00ffff
StereoGamma=0x3f800000
ShowAllViewerTypes=0x1
GlassesSwitchDelay=0x0
GlassesDelayPlus=0x4bb
GlassesDelayMinus=0x4bd
ToggleMemo=0xe2d
EnableWindowedMode=0x5
Time=0x55254758
MonitorSize=0x36
StereoMonitorID=0x27e36904
StereoAnaglyphType=0x1
StereoDefaultONSet=0x1
StereoTypeSet=0x1
StereoVisionConfirmed=0x1

Thanks for your time.

ASUS X58 P6T Deluxe MBO, 680 SLI, ASUS VG278HE 3D Monitor, Ideazon Merc Stealth Keyboard, Microsoft Sidewinder Mouse, Corsair Headphones, Windows 7 64 bit

#33
Posted 04/22/2015 03:53 PM   
Hmm, that's really odd ... [s]0x1 is what it was when it was working/first run(?) and when you rebooted it changed it to 0x80000001, that almost seems backwards. D-Man11 reported that his working setup had a StereoViewerType of 0x80000001 [VG278HE] awhile back.[/s] If it's really the case try running the following as admin after a reboot. [code]@Echo Off if Exist "%PROGRAMFILES(X86)%" Set $Wow=Wow6432Node\ Set $Key="HKLM\SOFTWARE\%$Wow%NVIDIA Corporation\Global\Stereo3D" /v "StereoViewerType" Reg Add %$Key% /t REG_DWORD /d 0x1 /f||Pause&&Goto :Eof [/code]
Hmm, that's really odd ... 0x1 is what it was when it was working/first run(?) and when you rebooted it changed it to 0x80000001, that almost seems backwards. D-Man11 reported that his working setup had a StereoViewerType of 0x80000001 [VG278HE] awhile back. If it's really the case try running the following as admin after a reboot.

@Echo Off
if Exist "%PROGRAMFILES(X86)%" Set $Wow=Wow6432Node\
Set $Key="HKLM\SOFTWARE\%$Wow%NVIDIA Corporation\Global\Stereo3D" /v "StereoViewerType"
Reg Add %$Key% /t REG_DWORD /d 0x1 /f||Pause&&Goto :Eof
#34
Posted 04/22/2015 04:27 PM   
Maybe somebody else will have better luck but for me the mystery continues. I erased SettDiffs.txt. Next I rebooted and ran the new batch file as Admin. Then ran Settings.bat and SetDiffs.txt was a blank file. But checking the Nvidia control panel I still had 3d Vision Discover as my only display type. I thought this was curious in Settings.txt... AnaglyphEnabled=0xdeadbeef :)
Maybe somebody else will have better luck but for me the mystery continues.
I erased SettDiffs.txt.
Next I rebooted and ran the new batch file as Admin.
Then ran Settings.bat and SetDiffs.txt was a blank file.
But checking the Nvidia control panel I still had 3d Vision Discover as my only display type.

I thought this was curious in Settings.txt...

AnaglyphEnabled=0xdeadbeef

:)

ASUS X58 P6T Deluxe MBO, 680 SLI, ASUS VG278HE 3D Monitor, Ideazon Merc Stealth Keyboard, Microsoft Sidewinder Mouse, Corsair Headphones, Windows 7 64 bit

#35
Posted 04/22/2015 04:58 PM   
Since my settings were the opposite of what you expected I double checked. Ran Settings.bat with 3d working. Played a 3D game. Shut down. Booted up and confirmed that as usual I had only 3d Vision Discover. Ran Settings.bat. SettDiffs.txt was again a single line, StereoViewerType=0x1,0x80000001
Since my settings were the opposite of what you expected I double checked.

Ran Settings.bat with 3d working.
Played a 3D game.
Shut down.
Booted up and confirmed that as usual I had only 3d Vision Discover.
Ran Settings.bat.
SettDiffs.txt was again a single line,

StereoViewerType=0x1,0x80000001

ASUS X58 P6T Deluxe MBO, 680 SLI, ASUS VG278HE 3D Monitor, Ideazon Merc Stealth Keyboard, Microsoft Sidewinder Mouse, Corsair Headphones, Windows 7 64 bit

#36
Posted 04/22/2015 05:15 PM   
StereoViewerType is 0x80000001 when anaglyph is enabled. 0x00000001 if Asus 120Hz 3D LCD is selected. I updated to 350.12 and am experiencing this problem now. I edited my previous post in the other thread to reflect my incorrect StereoViewerType.
StereoViewerType is 0x80000001 when anaglyph is enabled.

0x00000001 if Asus 120Hz 3D LCD is selected.

I updated to 350.12 and am experiencing this problem now.

I edited my previous post in the other thread to reflect my incorrect StereoViewerType.

#37
Posted 04/22/2015 05:18 PM   
deadbeef is an old programming thing, it's usually used to signify something that's obsolete/to be removed. It spells something but it's still hexadecimal. :) A long shot but have you tried rebooting, running the other batch file as admin and instead of going into the control panel, tried running a game? It still might kick it out if it's seeing it as an unsupported display type ... unless we lock the registry key or loop hack the value. Edit: ahh ok my bad I thought you said 0x80000001 was what the monitor's type was before.
deadbeef is an old programming thing, it's usually used to signify something that's obsolete/to be removed. It spells something but it's still hexadecimal. :)

A long shot but have you tried rebooting, running the other batch file as admin and instead of going into the control panel, tried running a game? It still might kick it out if it's seeing it as an unsupported display type ... unless we lock the registry key or loop hack the value.

Edit: ahh ok my bad I thought you said 0x80000001 was what the monitor's type was before.
#38
Posted 04/22/2015 05:29 PM   
For the sake of completeness I tried your suggestion and ran the admin batch file after a reboot and then fired up Assassins Creed II without going to the control panel, but no joy.
For the sake of completeness I tried your suggestion and ran the admin batch file after a reboot and then fired up Assassins Creed II without going to the control panel, but no joy.

ASUS X58 P6T Deluxe MBO, 680 SLI, ASUS VG278HE 3D Monitor, Ideazon Merc Stealth Keyboard, Microsoft Sidewinder Mouse, Corsair Headphones, Windows 7 64 bit

#39
Posted 04/22/2015 06:13 PM   
Some problem here, but nothing new, I have been experiencing this problem for the last 2 years. I usually solve the problem just unpluging/pluging the emitter. Anyway that is not a solution, it must be a driver problem, nothing related with the length of the cable, as I was suggested time ago.
Some problem here, but nothing new, I have been experiencing this problem for the last 2 years. I usually solve the problem just unpluging/pluging the emitter. Anyway that is not a solution, it must be a driver problem, nothing related with the length of the cable, as I was suggested time ago.

- Windows 7 64bits (SSD OCZ-Vertez2 128Gb)
- "ASUS P6X58D-E" motherboard
- "MSI GTX 660 TI"
- "Intel Xeon X5670" @4000MHz CPU (20.0[12-25]x200MHz)
- RAM 16 Gb DDR3 1600
- "Dell S2716DG" monitor (2560x1440 @144Hz)
- "Corsair Carbide 600C" case
- Labrador dog (cinnamon edition)

#40
Posted 04/22/2015 08:38 PM   
Same problem here. Since I updated my motherboard drivers and bios (Gigabyte Z87X-D3H) and Nvidia-drivers to 350.12 after every reboot of my pc I have to change manualy from "3D vision discover" to "Asus 120 Hz 3D-LCD", so annoying!!!
Same problem here. Since I updated my motherboard drivers and bios (Gigabyte Z87X-D3H) and Nvidia-drivers to 350.12 after every reboot of my pc I have to change manualy from "3D vision discover" to "Asus 120 Hz 3D-LCD", so annoying!!!

Win 8.1 pro 64 bit, Gigabyte Z87X-D3H - i7-4770K@3.5 - 32 GB, 2x Geforce TITAN SLI (EVGA), 3x ASUS 3D-Vision-Monitors

#41
Posted 04/29/2015 02:33 PM   
Same here I have learnt to just go to the gfx control panel and switch it over after boot up
Same here

I have learnt to just go to the gfx control panel and switch it over after boot up

Lord, grant me the serenity to accept the things I cannot change, the courage to change the things I can, and the wisdom to know the difference.
-------------------
Vitals: Windows 7 64bit, i5 2500 @ 4.4ghz, SLI GTX670, 8GB, Viewsonic VX2268WM

Handy Driver Discussion
Helix Mod - community fixes
Bo3b's Shaderhacker School - How to fix 3D in games
3dsolutionsgaming.com - videos, reviews and 3D fixes

#42
Posted 04/29/2015 03:15 PM   
Yep, this has happened to me only occasionally in the past, but now it's every time. I've learned to change it back in CP before booting up a game.
Yep, this has happened to me only occasionally in the past, but now it's every time. I've learned to change it back in CP before booting up a game.

|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

#43
Posted 04/29/2015 10:29 PM   
Still seems like a timing thing to me. Computer boots up too fast, or the driver kicks in before the USB is finished. Computer thinks the dongle is missing and switches over to Discover. How about a batch file that you drop into your startup items folder, that waits for say 15 seconds for things to stabilize after a boot, then does a stop/start of the nvidia service? One way to tell if that would work is for people who are having the problem to go to Services and do a stop/start of that service to see if it shows up normally. Another thing worth trying would be to change your BIOS settings for USB enumeration to try to make it faster, change from legacy mode for example.
Still seems like a timing thing to me. Computer boots up too fast, or the driver kicks in before the USB is finished. Computer thinks the dongle is missing and switches over to Discover.

How about a batch file that you drop into your startup items folder, that waits for say 15 seconds for things to stabilize after a boot, then does a stop/start of the nvidia service?

One way to tell if that would work is for people who are having the problem to go to Services and do a stop/start of that service to see if it shows up normally.

Another thing worth trying would be to change your BIOS settings for USB enumeration to try to make it faster, change from legacy mode for example.

Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers

#44
Posted 04/30/2015 03:19 AM   
I'm getting this too, and I have a built-in emitter. Doesn't seem to be every time, but it happens often when changing from projector to monitor.
I'm getting this too, and I have a built-in emitter. Doesn't seem to be every time, but it happens often when changing from projector to monitor.

#45
Posted 04/30/2015 12:16 PM   
  3 / 6    
Scroll To Top