Green youtube Video when full screen in recent drivers when 3dvision is enabled in NCP (windows 10)
Anyone else experiencing this? Everything works as normal, until you try and view a youtube video full screen. emitter kicks in and you are greeted with a corrupt green video. Previously the emitter would not try to start I have't confirmed if this is a problem with the "flash" player or windows 10 or the drivers as yet. But my cousin who I recently just got into 3dvision was turning it off because of the same problem happening for him.
Anyone else experiencing this?

Everything works as normal, until you try and view a youtube video full screen. emitter kicks in and you are greeted with a corrupt green video. Previously the emitter would not try to start

I have't confirmed if this is a problem with the "flash" player or windows 10 or the drivers as yet. But my cousin who I recently just got into 3dvision was turning it off because of the same problem happening for him.

i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
EVGA 1080TI SLI
Samsung SSD 840Pro
ASUS Z97-WS
3D Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)

#1
Posted 02/01/2017 12:53 AM   
I don't get that exactly, but one of the most annoying issues I've been facing ever since I switched to Win 10 is that every time I switch to full screen when viewing a youtube video my screen will immediately go completely black for about 5 seconds, come back for a split second, then go black for another 5 seconds, turn on my green light for the built in 3D emitter, and then finally it will come back and work properly... so kinda similar except I don't get any green corrupted video. Doesn't really help you much, but know that I feel your pain. ;)
I don't get that exactly, but one of the most annoying issues I've been facing ever since I switched to Win 10 is that every time I switch to full screen when viewing a youtube video my screen will immediately go completely black for about 5 seconds, come back for a split second, then go black for another 5 seconds, turn on my green light for the built in 3D emitter, and then finally it will come back and work properly... so kinda similar except I don't get any green corrupted video. Doesn't really help you much, but know that I feel your pain. ;)

3D Gaming Rig: CPU: i7 7700K @ 4.9Ghz | Mobo: Asus Maximus Hero VIII | RAM: Corsair Dominator 16GB | GPU: 2 x GTX 1080 Ti SLI | 3xSSDs for OS and Apps, 2 x HDD's for 11GB storage | PSU: Seasonic X-1250 M2| Case: Corsair C70 | Cooling: Corsair H115i Hydro cooler | Displays: Asus PG278QR, BenQ XL2420TX & BenQ HT1075 | OS: Windows 10 Pro + Windows 7 dual boot

Like my fixes? Dontations can be made to: www.paypal.me/DShanz or rshannonca@gmail.com
Like electronic music? Check out: www.soundcloud.com/dj-ryan-king

#2
Posted 02/01/2017 07:30 AM   
Sounds like the same problem but you got lucky =)
Sounds like the same problem but you got lucky =)

i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
EVGA 1080TI SLI
Samsung SSD 840Pro
ASUS Z97-WS
3D Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)

#3
Posted 02/01/2017 09:30 AM   
Do you have any codec Pack installed? Try to remove that one and see if it works then;) Every time I got a green video was related to codecs (in the past 10+ years) :) If that fixes it, look for an updated version of the codec pack;) K-Lite Codec Pack is the one I normally use and shouldn't have this problem.
Do you have any codec Pack installed? Try to remove that one and see if it works then;)
Every time I got a green video was related to codecs (in the past 10+ years) :)
If that fixes it, look for an updated version of the codec pack;)
K-Lite Codec Pack is the one I normally use and shouldn't have this problem.

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)

#4
Posted 02/01/2017 10:40 AM   
If you never need 3D in your browser, you could probably use Nvidia Inspector to find and remove the profile associated with the exe for the browser. Or go into the browser options and turn off /disable the plug-in? Which browser? Driver version? I'm using older drivers for the time being, so this must be due to a newer driver?
If you never need 3D in your browser, you could probably use Nvidia Inspector to find and remove the profile associated with the exe for the browser. Or go into the browser options and turn off /disable the plug-in?

Which browser? Driver version?

I'm using older drivers for the time being, so this must be due to a newer driver?

#5
Posted 02/01/2017 12:35 PM   
I am not using any codec packs. I haven't really played around this video at all so it should be close to as standard as possible. So I am using chrome and the latest driver, but this has been an issue for me for along time now and I have just been putting up with it. that said things just got a little more interesting. So I fired up a you tube video in chrome full screen, emitter kicks in Green screen. as normal. On my second screen I opened edge. (euurgh) As soon as I maximized the screen, the emitter turns off! Playing around with it a bit more I find it's kinda tempremental but I can get the emitter to turn off sometimes by playing around with additional windows, browser file exporer what ever on another screen. It's like windows is removing focus from the video and then detects it should be in 2d mode and turns it off. Ultimately I guess, it's the fact that it turns green at all, otherwise it would be tolerable, it's obvious something is buggy somewhere.. I'm a bit surprized no one else here is seeing this because I have never touched my cousins machine and we arent running anything similar as far as I am aware. He simply saw I 3d kit somewhere and I urged him to pick it up.
I am not using any codec packs. I haven't really played around this video at all so it should be close to as standard as possible.

So I am using chrome and the latest driver, but this has been an issue for me for along time now and I have just been putting up with it. that said things just got a little more interesting.

So I fired up a you tube video in chrome full screen, emitter kicks in Green screen. as normal.

On my second screen I opened edge. (euurgh) As soon as I maximized the screen, the emitter turns off!
Playing around with it a bit more I find it's kinda tempremental but I can get the emitter to turn off sometimes by playing around with additional windows, browser file exporer what ever on another screen.

It's like windows is removing focus from the video and then detects it should be in 2d mode and turns it off.

Ultimately I guess, it's the fact that it turns green at all, otherwise it would be tolerable, it's obvious something is buggy somewhere..

I'm a bit surprized no one else here is seeing this because I have never touched my cousins machine and we arent running anything similar as far as I am aware. He simply saw I 3d kit somewhere and I urged him to pick it up.

i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
EVGA 1080TI SLI
Samsung SSD 840Pro
ASUS Z97-WS
3D Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)

#6
Posted 02/01/2017 02:56 PM   
I tried in both, Firefox and Chrome, with the latest Drivers(378.49) on Win10 and neither made 3D kick in when visiting YouTube or viewing Fullscreen... my emitter wouldn't even turn on, it usually only does when I visit 3DVisionLive.com A bit off-topic but Chrome has the weirdest Profile: [code]Profile "Google Chrome" ShowOn GeForce ProfileType Application Executable "chrome.exe" Setting ID_0x0045ab1f = 0x00000000 Setting ID_0x00666665 = 0x00000000 Setting ID_0x0067345e = 0x00008000 Setting ID_0x1034cb89 = 0x00000000 // NVIDIA Predefined FXAA Usage Setting ID_0x1035db89 = 0x00000000 Setting ID_0x10a879cf = 0x00000001 Setting ID_0x10ecdb82 = 0x00000001 // Antialiasing - Behavior Flags Setting ID_0x10fdec23 = 0x00000001 Setting ID_0x701eb457 = 0x2241ab21 InternalSettingFlag=V0 // MysteryStereoSetting Setting ID_0x702a0ab2 = 0xe374baf1 InternalSettingFlag=V0 // AutoConvergence SettingString ID_0x703c4026 = "Techland" // Developer SettingString ID_0x7049c7ec = "2.0" // Value SettingString ID_0x704cde5a = "F,A" // Issues SettingString ID_0x704d456e = "2D crosshair, very hard to aim. Some nature objects are very 2D and flat" // Comments SettingString ID_0x7051e5f5 = "2" // Compat Setting ID_0x7058b6e1 = 0x6e0326f8 InternalSettingFlag=V0 // LaserSight SettingString ID_0x705fafec = "2003-11-06 00:00:00" // Rel SettingString ID_0x706c7030 = "Strategy First" // Publisher Setting ID_0x708db8c5 = 0x2204cbca InternalSettingFlag=V0 // StereoConvergence SettingString ID_0x709cc5e0 = "ACTION/3D" // Style Setting ID_0x70a1411a = 0x5a865888 InternalSettingFlag=V0 // FrustumAdjustMode SettingString ID_0x70b5603f = "D3D" // API Setting ID_0x70e46f20 = 0x8d9c3201 InternalSettingFlag=V0 // StereoHiddenProfile SettingString ID_0x70e46f2a = "npnv3dv.dll,coolirisstub.dll,cooliris.dll,webplayer_win.dll,vkvslkernel.vkmodule" // StereoLinkDll Setting ID_0x80303a19 = 0x00000000 Setting ID_0x80857a28 = 0x00000000 Setting ID_0x809d5f60 = 0x00000000 EndProfile[/code] AutoConvergence?? LaserSight?? 2D Crosshair?? "Techland" // Developer?? "Strategy First" // Publisher?? Who in the hell came up with this Profile?? There was no other instance of Techland in NVIDIA Profile.txt, so I Google it... apparently they made Dying Light... seems like it might have been a Dying Light Profile at one point or at least part of one... Odd [code]Profile "Dying Light" ShowOn GeForce ProfileType Application Executable "dyinglightgame.exe" Setting ID_0x00a06946 = 0x080000f5 // SLI Compatibility Bits (DX1x) Setting ID_0x1033cec2 = 0x00000002 Setting ID_0x1033dcd3 = 0x00000004 Setting ID_0x701eb457 = 0x2241ab21 InternalSettingFlag=V0 // MysteryStereoSetting SettingString ID_0x7049c7ec = "웪ꑌ" InternalSettingFlag=V0 // Value SettingString ID_0x704d456e = "Some objects render at wrong depth. Some effects render incorrectly." // Comments SettingString ID_0x7051e5f5 = "籪鸙" InternalSettingFlag=V0 // Compat Setting ID_0x708db8c5 = 0x5ca16975 InternalSettingFlag=V0 // StereoConvergence Setting ID_0x709a1ddf = 0x4b1cd968 InternalSettingFlag=V0 // StereoCutoff Setting ID_0x709adada = 0x37f58357 InternalSettingFlag=V0 // 2DDHUDSettings Setting ID_0x709adadb = 0xca44cf8c InternalSettingFlag=V0 // 2DDConvergence SettingString ID_0x709adadc = "ݧ浒???䬼⚝湥㿔㶩䐕鋃쫺待욻ꐩ쪒ₐ쀴???㓹僠娋簭鹼瀣딅ᤩ叁???" InternalSettingFlag=V0 // Notes SettingString ID_0x70b5603f = "榻鳈⏹ꢗ" InternalSettingFlag=V0 // API Setting ID_0x70edb381 = 0x24208b6c InternalSettingFlag=V0 // StereoTextureEnable EndProfile[/code]
I tried in both, Firefox and Chrome, with the latest Drivers(378.49) on Win10 and neither made 3D kick in when visiting YouTube or viewing Fullscreen... my emitter wouldn't even turn on, it usually only does when I visit 3DVisionLive.com

A bit off-topic but Chrome has the weirdest Profile:
Profile "Google Chrome"
ShowOn GeForce
ProfileType Application
Executable "chrome.exe"
Setting ID_0x0045ab1f = 0x00000000
Setting ID_0x00666665 = 0x00000000
Setting ID_0x0067345e = 0x00008000
Setting ID_0x1034cb89 = 0x00000000 // NVIDIA Predefined FXAA Usage
Setting ID_0x1035db89 = 0x00000000
Setting ID_0x10a879cf = 0x00000001
Setting ID_0x10ecdb82 = 0x00000001 // Antialiasing - Behavior Flags
Setting ID_0x10fdec23 = 0x00000001
Setting ID_0x701eb457 = 0x2241ab21 InternalSettingFlag=V0 // MysteryStereoSetting
Setting ID_0x702a0ab2 = 0xe374baf1 InternalSettingFlag=V0 // AutoConvergence
SettingString ID_0x703c4026 = "Techland" // Developer
SettingString ID_0x7049c7ec = "2.0" // Value
SettingString ID_0x704cde5a = "F,A" // Issues
SettingString ID_0x704d456e = "2D crosshair, very hard to aim. Some nature objects are very 2D and flat" // Comments
SettingString ID_0x7051e5f5 = "2" // Compat
Setting ID_0x7058b6e1 = 0x6e0326f8 InternalSettingFlag=V0 // LaserSight
SettingString ID_0x705fafec = "2003-11-06 00:00:00" // Rel
SettingString ID_0x706c7030 = "Strategy First" // Publisher
Setting ID_0x708db8c5 = 0x2204cbca InternalSettingFlag=V0 // StereoConvergence
SettingString ID_0x709cc5e0 = "ACTION/3D" // Style
Setting ID_0x70a1411a = 0x5a865888 InternalSettingFlag=V0 // FrustumAdjustMode
SettingString ID_0x70b5603f = "D3D" // API
Setting ID_0x70e46f20 = 0x8d9c3201 InternalSettingFlag=V0 // StereoHiddenProfile
SettingString ID_0x70e46f2a = "npnv3dv.dll,coolirisstub.dll,cooliris.dll,webplayer_win.dll,vkvslkernel.vkmodule" // StereoLinkDll
Setting ID_0x80303a19 = 0x00000000
Setting ID_0x80857a28 = 0x00000000
Setting ID_0x809d5f60 = 0x00000000
EndProfile

AutoConvergence?? LaserSight?? 2D Crosshair?? "Techland" // Developer?? "Strategy First" // Publisher?? Who in the hell came up with this Profile??

There was no other instance of Techland in NVIDIA Profile.txt, so I Google it... apparently they made Dying Light... seems like it might have been a Dying Light Profile at one point or at least part of one... Odd

Profile "Dying Light"
ShowOn GeForce
ProfileType Application
Executable "dyinglightgame.exe"
Setting ID_0x00a06946 = 0x080000f5 // SLI Compatibility Bits (DX1x)
Setting ID_0x1033cec2 = 0x00000002
Setting ID_0x1033dcd3 = 0x00000004
Setting ID_0x701eb457 = 0x2241ab21 InternalSettingFlag=V0 // MysteryStereoSetting
SettingString ID_0x7049c7ec = "웪ꑌ" InternalSettingFlag=V0 // Value
SettingString ID_0x704d456e = "Some objects render at wrong depth. Some effects render incorrectly." // Comments
SettingString ID_0x7051e5f5 = "籪鸙" InternalSettingFlag=V0 // Compat
Setting ID_0x708db8c5 = 0x5ca16975 InternalSettingFlag=V0 // StereoConvergence
Setting ID_0x709a1ddf = 0x4b1cd968 InternalSettingFlag=V0 // StereoCutoff
Setting ID_0x709adada = 0x37f58357 InternalSettingFlag=V0 // 2DDHUDSettings
Setting ID_0x709adadb = 0xca44cf8c InternalSettingFlag=V0 // 2DDConvergence
SettingString ID_0x709adadc = "ݧ浒???䬼⚝湥㿔㶩䐕鋃쫺待욻ꐩ쪒ₐ쀴???㓹僠娋簭鹼瀣딅ᤩ叁???" InternalSettingFlag=V0 // Notes
SettingString ID_0x70b5603f = "榻鳈⏹ꢗ" InternalSettingFlag=V0 // API
Setting ID_0x70edb381 = 0x24208b6c InternalSettingFlag=V0 // StereoTextureEnable
EndProfile
#7
Posted 02/01/2017 03:58 PM   
lol, I saw the same thing awhile back. There was a game called Chrome https://en.wikipedia.org/wiki/Chrome_(video_game)
lol, I saw the same thing awhile back. There was a game called Chrome


https://en.wikipedia.org/wiki/Chrome_(video_game)

#8
Posted 02/02/2017 01:33 AM   
Weird. I wonder what the commonality that's causing the emitter is kicking in for me, my relative and Djrk in chrome but not you guys. Just running edge in the background seems to prevent it from happening for me now, well at least it's a work around. thanks guys.
Weird. I wonder what the commonality that's causing the emitter is kicking in for me, my relative and Djrk in chrome but not you guys.

Just running edge in the background seems to prevent it from happening for me now, well at least it's a work around.

thanks guys.

i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
EVGA 1080TI SLI
Samsung SSD 840Pro
ASUS Z97-WS
3D Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)

#9
Posted 02/02/2017 02:23 AM   
You could try adding the StereoNotSupported Flag... if using nvidiaProfileInspector > Select "Google Chrome" > Click Magnifying Glass(Show Unknown Settings...) > Scroll Down to Unknown > Select 0x709AA171 > Set Value to 0x00000001 > Click Apply Changes (if using DarkStarSword's updated [url=https://raw.githubusercontent.com/DarkStarSword/3d-fixes/master/CustomSettingNames_en-EN.xml]CustomSettingNames.xml[/url] with nvidiaProfileInspector > Select "Google Chrome" > Select StereoNotSupported > Set Value to 0x00000001 > Click Apply Changes) if using GeForce 3D Profile Manager > Add the following line to the "Google Chrome" Profile... [quote]Setting ID_0x709aa171 = 0x349addfb InternalSettingFlag=V0 // StereoNotSupported[/quote]Edit:Or you might try removing the StereoProfile(0x701EB457) Flag or setting it to 0...
You could try adding the StereoNotSupported Flag...

if using nvidiaProfileInspector > Select "Google Chrome" > Click Magnifying Glass(Show Unknown Settings...) > Scroll Down to Unknown > Select 0x709AA171 > Set Value to 0x00000001 > Click Apply Changes

(if using DarkStarSword's updated CustomSettingNames.xml with nvidiaProfileInspector > Select "Google Chrome" > Select StereoNotSupported > Set Value to 0x00000001 > Click Apply Changes)

if using GeForce 3D Profile Manager > Add the following line to the "Google Chrome" Profile...
Setting ID_0x709aa171 = 0x349addfb InternalSettingFlag=V0 // StereoNotSupported
Edit:Or you might try removing the StereoProfile(0x701EB457) Flag or setting it to 0...
#10
Posted 02/02/2017 03:44 AM   
Not sure if this has anything to do with anything here but when I was tinkering with something else I noticed they added a VSync(?) Setting Flag to the "Adobe Flash Application/Player" Profiles... [code]Profile "Adobe Flash Application" ShowOn All ProfileType Application Executable "flash.exe" Setting ID_0x0045ab1f = 0x00000000 Setting ID_0x1035db89 = 0x00000000 Setting ID_0x10a879cf = 0x00000001 Setting ID_0x10fdec23 = 0x00000001 // Added Setting ID_0x80303a19 = 0x00000000 Setting ID_0x80857a28 = 0x00000000 Setting ID_0x809d5f60 = 0x00000000 EndProfile Profile "Adobe Flash Player" ShowOn All ProfileType Application Executable "flashplayer.exe" Executable "flashplayerplugin_17_0_0_190.exe" Executable "flashplayerplugin_17_0_0_188.exe" Setting ID_0x0045ab1f = 0x00000000 Setting ID_0x1035db89 = 0x00000000 Setting ID_0x10a879cf = 0x00000001 Setting ID_0x10fdec23 = 0x00000001 // Added Setting ID_0x80303a19 = 0x00000000 Setting ID_0x80857a28 = 0x00000000 Setting ID_0x809d5f60 = 0x00000000 EndProfile [/code] might want to try setting it to 0x00000000 in nPI(Vsync - Behavior Flags) or removing it completely with GF3DPM...
Not sure if this has anything to do with anything here but when I was tinkering with something else I noticed they added a VSync(?) Setting Flag to the "Adobe Flash Application/Player" Profiles...

Profile "Adobe Flash Application"
ShowOn All
ProfileType Application
Executable "flash.exe"
Setting ID_0x0045ab1f = 0x00000000
Setting ID_0x1035db89 = 0x00000000
Setting ID_0x10a879cf = 0x00000001
Setting ID_0x10fdec23 = 0x00000001 // Added
Setting ID_0x80303a19 = 0x00000000
Setting ID_0x80857a28 = 0x00000000
Setting ID_0x809d5f60 = 0x00000000
EndProfile

Profile "Adobe Flash Player"
ShowOn All
ProfileType Application
Executable "flashplayer.exe"
Executable "flashplayerplugin_17_0_0_190.exe"
Executable "flashplayerplugin_17_0_0_188.exe"
Setting ID_0x0045ab1f = 0x00000000
Setting ID_0x1035db89 = 0x00000000
Setting ID_0x10a879cf = 0x00000001
Setting ID_0x10fdec23 = 0x00000001 // Added
Setting ID_0x80303a19 = 0x00000000
Setting ID_0x80857a28 = 0x00000000
Setting ID_0x809d5f60 = 0x00000000
EndProfile

might want to try setting it to 0x00000000 in nPI(Vsync - Behavior Flags) or removing it completely with GF3DPM...
#11
Posted 02/04/2017 05:41 PM   
Scroll To Top