CEF (Chromium Embedded Framework) incompatibility after 388.xx
  1 / 2    
There is a known severe issue Nvidia is ignoring with recent driver since 388.xx: [url=https://en.wikipedia.org/wiki/Chromium_Embedded_Framework]CEF (Chromium Embedded Framework[/url] components) based web-tools like GeForce Experience, recent GOG Galaxy client, Chrome browser etc. [i]GUIs appear blurry, with bad colors, and blurry fonts[/i], when HW gfx acceleration is ON. Maybe this happens only with some GPUs (see my signature, I have gtx 980m) + new drivers, I don't know why, but I know the problem is real and reproducible for many users in other forums. Hope Nvidia will fix it soon because it's carrying over this bug at least since 3 WHQL releases ago. Screenshot examples for GeForce Experience, Chrome, GOG Galaxy: [url=https://ibb.co/gjEX2m][img]https://thumb.ibb.co/gjEX2m/image.png[/img][/url] - [url=https://ibb.co/fyYAVn][img]https://thumb.ibb.co/fyYAVn/image.png[/img][/url] - [url=https://ibb.co/m1JzO7][img]https://thumb.ibb.co/m1JzO7/image.png[/img][/url] Please, notice that if I disable gfx HW acceleration in Chrome, the GUI in the browser will be rendered correctly. This seems to prove it's a gfx HW acceleration issue between CEF and Nvidia drivers with some GPUs. Resetting Nvidia drivers settings to default and reinstalling the driver after DDU won't solve the issue. Windows 10 x64 FCU 1709 (16299.248), Nvidia drivers 390.77 WHQL EDIT: for a temporary fix read comment [url=https://forums.geforce.com/default/topic/1037275/geforce-drivers/cef-chromium-embedded-framework-incompatibility-after-388-xx/post/5296333/#5296333]#9[/url]
There is a known severe issue Nvidia is ignoring with recent driver since 388.xx:
CEF (Chromium Embedded Framework components) based web-tools like GeForce Experience, recent GOG Galaxy client, Chrome browser etc. GUIs appear blurry, with bad colors, and blurry fonts, when HW gfx acceleration is ON.
Maybe this happens only with some GPUs (see my signature, I have gtx 980m) + new drivers, I don't know why, but I know the problem is real and reproducible for many users in other forums.

Hope Nvidia will fix it soon because it's carrying over this bug at least since 3 WHQL releases ago.

Screenshot examples for GeForce Experience, Chrome, GOG Galaxy:

Image - Image - Image

Please, notice that if I disable gfx HW acceleration in Chrome, the GUI in the browser will be rendered correctly. This seems to prove it's a gfx HW acceleration issue between CEF and Nvidia drivers with some GPUs.
Resetting Nvidia drivers settings to default and reinstalling the driver after DDU won't solve the issue.

Windows 10 x64 FCU 1709 (16299.248), Nvidia drivers 390.77 WHQL

EDIT:
for a temporary fix read comment #9

Gaming laptop ASUS G751JY
Chipset: Intel HM87 Lynx Point, CPU: i7-4860HQ, RAM: Kingston KHX2133C11S3L 24GB DDR3L 2133MHz, Gfx card: GTX 980M (GM204M, 10DE-1617/1043-22DA Rev A1, vBIOS v84.04.48.00.39), 4GB GDDR5 (Micron), OS: Windows 10 x64 FCU 1709, Laptop display: G-Sync LG Philips LP173WF4-SPD1 (LGD046C) 17", desktop native res: 1920x1080 75Hz, Audio: Realtek HD (ALC668).

#1
Posted 02/13/2018 01:09 PM   
Some users on GOG forum (also new GOG Galaxy client is affected) wrote the issue disappears rolling back to 388.71 WHQL.
Some users on GOG forum (also new GOG Galaxy client is affected) wrote the issue disappears rolling back to 388.71 WHQL.

Gaming laptop ASUS G751JY
Chipset: Intel HM87 Lynx Point, CPU: i7-4860HQ, RAM: Kingston KHX2133C11S3L 24GB DDR3L 2133MHz, Gfx card: GTX 980M (GM204M, 10DE-1617/1043-22DA Rev A1, vBIOS v84.04.48.00.39), 4GB GDDR5 (Micron), OS: Windows 10 x64 FCU 1709, Laptop display: G-Sync LG Philips LP173WF4-SPD1 (LGD046C) 17", desktop native res: 1920x1080 75Hz, Audio: Realtek HD (ALC668).

#2
Posted 02/21/2018 08:55 AM   
...Nothing from Customer Care? It's a very annoying issue for all users without an IGP, using only discrete Nvidia cards (no Optimus).
...Nothing from Customer Care?
It's a very annoying issue for all users without an IGP, using only discrete Nvidia cards (no Optimus).

Gaming laptop ASUS G751JY
Chipset: Intel HM87 Lynx Point, CPU: i7-4860HQ, RAM: Kingston KHX2133C11S3L 24GB DDR3L 2133MHz, Gfx card: GTX 980M (GM204M, 10DE-1617/1043-22DA Rev A1, vBIOS v84.04.48.00.39), 4GB GDDR5 (Micron), OS: Windows 10 x64 FCU 1709, Laptop display: G-Sync LG Philips LP173WF4-SPD1 (LGD046C) 17", desktop native res: 1920x1080 75Hz, Audio: Realtek HD (ALC668).

#3
Posted 02/23/2018 11:10 AM   
Thanks. I got your feedback and filed a bug. Can you confirm you are not seeing this with 388.71? Your first post states it starts with any 388.xx driver but in your 2nd post, GOG users don't see this with 388.71.
Thanks. I got your feedback and filed a bug. Can you confirm you are not seeing this with 388.71? Your first post states it starts with any 388.xx driver but in your 2nd post, GOG users don't see this with 388.71.

We can't fix your bug if we can't reproduce it. Please provide as much details as possible including specs, steps to reproduce, graphics settings used, etc..

For GeForce driver issues, please leave feedback in driver feedback form: Driver Feedback

For SHIELD Android TV issues/requests, please leave feedback in the SHIELD feedback form: SHIELD Feedback

For SHIELD Tablet issues/requests, please leave feedback in the SHIELD Tablet feedback form: SHIELD Tablet Feedback

I am also available on Twitter:
www.twitter.com/manuelguzman

#4
Posted 02/24/2018 02:00 AM   
Yes, sorry, as far as I've read here one user rolled back to 388.71 WHQL to solve this issue with CEF components: https://www.gog.com/forum/general/gog_galaxy_blurry_text_after_update/post24 EDIT: BUT... [url=https://forums.geforce.com/default/topic/1029432/geforce-experience/geforce-experience-3-11-0-73-feedback-thread-/post/5251392/#5251392]from my personal experience[/url] it was already present with 388.31 and 388.43! So I think it actually started with 388.xx family, at least on my gtx 980m, and I was right...
Yes, sorry, as far as I've read here one user rolled back to 388.71 WHQL to solve this issue with CEF components: https://www.gog.com/forum/general/gog_galaxy_blurry_text_after_update/post24

EDIT:
BUT... from my personal experience it was already present with 388.31 and 388.43!
So I think it actually started with 388.xx family, at least on my gtx 980m, and I was right...

Gaming laptop ASUS G751JY
Chipset: Intel HM87 Lynx Point, CPU: i7-4860HQ, RAM: Kingston KHX2133C11S3L 24GB DDR3L 2133MHz, Gfx card: GTX 980M (GM204M, 10DE-1617/1043-22DA Rev A1, vBIOS v84.04.48.00.39), 4GB GDDR5 (Micron), OS: Windows 10 x64 FCU 1709, Laptop display: G-Sync LG Philips LP173WF4-SPD1 (LGD046C) 17", desktop native res: 1920x1080 75Hz, Audio: Realtek HD (ALC668).

#5
Posted 02/25/2018 09:21 AM   
[i]WORKAROUND FOR GEFORCE EXPERIENCE: [/i] If I edit "C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA GeForce Experience.json" and remove the line with: "nv-enable-gpu", the GeForce Panel will look fine again.
WORKAROUND FOR GEFORCE EXPERIENCE:

If I edit
"C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA GeForce Experience.json"

and remove the line with:
"nv-enable-gpu",

the GeForce Panel will look fine again.

Gaming laptop ASUS G751JY
Chipset: Intel HM87 Lynx Point, CPU: i7-4860HQ, RAM: Kingston KHX2133C11S3L 24GB DDR3L 2133MHz, Gfx card: GTX 980M (GM204M, 10DE-1617/1043-22DA Rev A1, vBIOS v84.04.48.00.39), 4GB GDDR5 (Micron), OS: Windows 10 x64 FCU 1709, Laptop display: G-Sync LG Philips LP173WF4-SPD1 (LGD046C) 17", desktop native res: 1920x1080 75Hz, Audio: Realtek HD (ALC668).

#6
Posted 02/25/2018 09:32 AM   
windows DPI config at 100% or larger than?
windows DPI config at 100% or larger than?



In Memory of Chris "ChrisRay" Arthington, 1982-2010

Specs:
CPU:Intel Xeon x5690 @ 4.2Ghz, Mainboard:Asus Rampage III Extreme, Memory:48GB Corsair Vengeance LP 1600
Video:EVGA Geforce GTX 1080 Founders Edition, NVidia Geforce GTX 1060 Founders Edition
Monitor:ROG PG279Q, BenQ BL2211, Sound:Creative XFI Titanium Fatal1ty Pro
SDD:Crucial MX300 275, Crucial MX300 525, Crucial MX300 1000
HDD:500GB Spinpoint F3, 1TB WD Black, 2TB WD Red, 1TB WD Black
Case:NZXT Phantom 820, PSU:Seasonic X-850, OS:Windows 7 SP1
Cooler: ThermalRight Silver Arrow IB-E Extreme

CPU:Intel Xeon x5670 @ 3.8Gz, Mainboard:Asus Rampage II Gene, Memory:24GB Corsair Vengeance LP 1600
Video:EVGA Geforce GTX 680+ 4GB
Monitor:55" Thorn TV, Sound:Sony Muteki 7.1
SDD:Crucial MX200 250, HDD: 1TB Samsung Spinpoint F3
Case:NZXT Phantom 410, PSU:Corsair 620HX, OS:Windows 10
Cooler: ThermalRight TRUE Spirit 120M BW Rev.A

#7
Posted 02/25/2018 10:03 AM   
untouched 100%
untouched 100%

Gaming laptop ASUS G751JY
Chipset: Intel HM87 Lynx Point, CPU: i7-4860HQ, RAM: Kingston KHX2133C11S3L 24GB DDR3L 2133MHz, Gfx card: GTX 980M (GM204M, 10DE-1617/1043-22DA Rev A1, vBIOS v84.04.48.00.39), 4GB GDDR5 (Micron), OS: Windows 10 x64 FCU 1709, Laptop display: G-Sync LG Philips LP173WF4-SPD1 (LGD046C) 17", desktop native res: 1920x1080 75Hz, Audio: Realtek HD (ALC668).

#8
Posted 02/25/2018 10:31 AM   
NEWS: forcing Anisotropic Filter to DISABLED in the Nvidia panel for "galaxyclient helper.exe" solves the corrupt GUI with GOG Galaxy client (that recently introduced CEF based gfx HW acceleration)! To be exact I've forced the following settings in the Nvidia panel: [img]https://image.ibb.co/erLBqx/image.png[/img] This seems a good workaround, but I still hope Nvidia will cooperate with CEF developers to fix this annoying issue once and for all, since CEF is widely used nowadays... EDIT: it works also with Chrome browser, leaving HW acceleration ON!
NEWS:
forcing Anisotropic Filter to DISABLED in the Nvidia panel for "galaxyclient helper.exe" solves the corrupt GUI with GOG Galaxy client (that recently introduced CEF based gfx HW acceleration)!

To be exact I've forced the following settings in the Nvidia panel:
Image

This seems a good workaround, but I still hope Nvidia will cooperate with CEF developers to fix this annoying issue once and for all, since CEF is widely used nowadays...

EDIT: it works also with Chrome browser, leaving HW acceleration ON!

Gaming laptop ASUS G751JY
Chipset: Intel HM87 Lynx Point, CPU: i7-4860HQ, RAM: Kingston KHX2133C11S3L 24GB DDR3L 2133MHz, Gfx card: GTX 980M (GM204M, 10DE-1617/1043-22DA Rev A1, vBIOS v84.04.48.00.39), 4GB GDDR5 (Micron), OS: Windows 10 x64 FCU 1709, Laptop display: G-Sync LG Philips LP173WF4-SPD1 (LGD046C) 17", desktop native res: 1920x1080 75Hz, Audio: Realtek HD (ALC668).

#9
Posted 02/25/2018 11:18 AM   
This is exactly the issue that Firefox way back when they first introduced hardware accelerated rendering, I'll see if theres still a bug for it. Wait- misremembering It wasn't Firefox, it was the Windows Live suite back when they first added DirectWrite fonts. The behavior in firefox's case was the font went extremely blurry. The fix in firefox's case was to go to Greyscale font smoothing instead of full colour. It came down to how the different layers were being mixed together and a fix from both microsofts side, and changes to component alpha and glyph antialiasing.
This is exactly the issue that Firefox way back when they first introduced hardware accelerated rendering, I'll see if theres still a bug for it.


Wait- misremembering

It wasn't Firefox, it was the Windows Live suite back when they first added DirectWrite fonts.

The behavior in firefox's case was the font went extremely blurry.

The fix in firefox's case was to go to Greyscale font smoothing instead of full colour.


It came down to how the different layers were being mixed together and a fix from both microsofts side, and changes to component alpha and glyph antialiasing.



In Memory of Chris "ChrisRay" Arthington, 1982-2010

Specs:
CPU:Intel Xeon x5690 @ 4.2Ghz, Mainboard:Asus Rampage III Extreme, Memory:48GB Corsair Vengeance LP 1600
Video:EVGA Geforce GTX 1080 Founders Edition, NVidia Geforce GTX 1060 Founders Edition
Monitor:ROG PG279Q, BenQ BL2211, Sound:Creative XFI Titanium Fatal1ty Pro
SDD:Crucial MX300 275, Crucial MX300 525, Crucial MX300 1000
HDD:500GB Spinpoint F3, 1TB WD Black, 2TB WD Red, 1TB WD Black
Case:NZXT Phantom 820, PSU:Seasonic X-850, OS:Windows 7 SP1
Cooler: ThermalRight Silver Arrow IB-E Extreme

CPU:Intel Xeon x5670 @ 3.8Gz, Mainboard:Asus Rampage II Gene, Memory:24GB Corsair Vengeance LP 1600
Video:EVGA Geforce GTX 680+ 4GB
Monitor:55" Thorn TV, Sound:Sony Muteki 7.1
SDD:Crucial MX200 250, HDD: 1TB Samsung Spinpoint F3
Case:NZXT Phantom 410, PSU:Corsair 620HX, OS:Windows 10
Cooler: ThermalRight TRUE Spirit 120M BW Rev.A

#10
Posted 02/25/2018 12:29 PM   
Mmmh, yes I remember those bugs of the past... Now that I've found the specific driver area causing the issue I hope Nvidia/CEF devs will be able to fix CEF open source code (or fix drivers on the Nvidia side) in one of the next versions.
Mmmh, yes I remember those bugs of the past...
Now that I've found the specific driver area causing the issue I hope Nvidia/CEF devs will be able to fix CEF open source code (or fix drivers on the Nvidia side) in one of the next versions.

Gaming laptop ASUS G751JY
Chipset: Intel HM87 Lynx Point, CPU: i7-4860HQ, RAM: Kingston KHX2133C11S3L 24GB DDR3L 2133MHz, Gfx card: GTX 980M (GM204M, 10DE-1617/1043-22DA Rev A1, vBIOS v84.04.48.00.39), 4GB GDDR5 (Micron), OS: Windows 10 x64 FCU 1709, Laptop display: G-Sync LG Philips LP173WF4-SPD1 (LGD046C) 17", desktop native res: 1920x1080 75Hz, Audio: Realtek HD (ALC668).

#11
Posted 02/25/2018 01:05 PM   
Though i have AF forced globally here and don't have issues.... Maybe Windows 10 did something to DirectWrite Battlenet app should be using the accelerated CEF.
Though i have AF forced globally here and don't have issues.... Maybe Windows 10 did something to DirectWrite

Battlenet app should be using the accelerated CEF.



In Memory of Chris "ChrisRay" Arthington, 1982-2010

Specs:
CPU:Intel Xeon x5690 @ 4.2Ghz, Mainboard:Asus Rampage III Extreme, Memory:48GB Corsair Vengeance LP 1600
Video:EVGA Geforce GTX 1080 Founders Edition, NVidia Geforce GTX 1060 Founders Edition
Monitor:ROG PG279Q, BenQ BL2211, Sound:Creative XFI Titanium Fatal1ty Pro
SDD:Crucial MX300 275, Crucial MX300 525, Crucial MX300 1000
HDD:500GB Spinpoint F3, 1TB WD Black, 2TB WD Red, 1TB WD Black
Case:NZXT Phantom 820, PSU:Seasonic X-850, OS:Windows 7 SP1
Cooler: ThermalRight Silver Arrow IB-E Extreme

CPU:Intel Xeon x5670 @ 3.8Gz, Mainboard:Asus Rampage II Gene, Memory:24GB Corsair Vengeance LP 1600
Video:EVGA Geforce GTX 680+ 4GB
Monitor:55" Thorn TV, Sound:Sony Muteki 7.1
SDD:Crucial MX200 250, HDD: 1TB Samsung Spinpoint F3
Case:NZXT Phantom 410, PSU:Corsair 620HX, OS:Windows 10
Cooler: ThermalRight TRUE Spirit 120M BW Rev.A

#12
Posted 02/25/2018 01:15 PM   
Do you know what other systems are affected by users? It might be possible this is panel specific so it might only affect certain notebooks.
Do you know what other systems are affected by users? It might be possible this is panel specific so it might only affect certain notebooks.

We can't fix your bug if we can't reproduce it. Please provide as much details as possible including specs, steps to reproduce, graphics settings used, etc..

For GeForce driver issues, please leave feedback in driver feedback form: Driver Feedback

For SHIELD Android TV issues/requests, please leave feedback in the SHIELD feedback form: SHIELD Feedback

For SHIELD Tablet issues/requests, please leave feedback in the SHIELD Tablet feedback form: SHIELD Tablet Feedback

I am also available on Twitter:
www.twitter.com/manuelguzman

#13
Posted 02/26/2018 02:50 PM   
Mmmh, have to ask on GOG forum, hoping they'll reply giving detailed infos...
Mmmh, have to ask on GOG forum, hoping they'll reply giving detailed infos...

Gaming laptop ASUS G751JY
Chipset: Intel HM87 Lynx Point, CPU: i7-4860HQ, RAM: Kingston KHX2133C11S3L 24GB DDR3L 2133MHz, Gfx card: GTX 980M (GM204M, 10DE-1617/1043-22DA Rev A1, vBIOS v84.04.48.00.39), 4GB GDDR5 (Micron), OS: Windows 10 x64 FCU 1709, Laptop display: G-Sync LG Philips LP173WF4-SPD1 (LGD046C) 17", desktop native res: 1920x1080 75Hz, Audio: Realtek HD (ALC668).

#14
Posted 02/26/2018 03:52 PM   
I have an Asus RoG G751JY hooked up to a Dell 2716DG monitor with G-Sync and can report that this issue persists on all of the latest driver builds. It's -super- annoying and doesn't just affect GoG - it seems to affect other applications that use the same font rendering.
I have an Asus RoG G751JY hooked up to a Dell 2716DG monitor with G-Sync and can report that this issue persists on all of the latest driver builds. It's -super- annoying and doesn't just affect GoG - it seems to affect other applications that use the same font rendering.

#15
Posted 03/18/2018 01:29 AM   
  1 / 2    
Scroll To Top