Trouble Deploying opengl32.dll (with mesa) with newer versions of Chromium

70 views
Skip to first unread message

Greg Clark

unread,
Feb 22, 2018, 2:17:12 AM2/22/18
to Chromium-discuss


Hello,

With previous versions of chrome I was able to place opengl32.dll in the same directory as the chrome executable.  The opengl32.dll is a mesa build.   Then I launched chrome with the --use-gl=desktop switch and everything worked fine and I was able to verify that Mesa was being used as a GPU driver when looking at the Chrome://gpu values.  This worked fine with Chrome Version 44


With newer versions 59 and above this is now not working.   I have tried a number of switches -enable-webgl --ignore-gpu-blacklist but nothing seems to work. 


Does anyone know how to get this to work with current versions?


Thanks

Greg




Note:  I do not want to use --use-gl=osmesa, this is way to slow only get 1 fps  where is the 13 and 17 build of mesa gets around 13-17 fps.

Ken Russell

unread,
Feb 22, 2018, 9:39:19 PM2/22/18
to gr...@storybulbs.com, Chromium-discuss
Sorry, we have never tested anything like that in-house on the Chromium project and can't help.

You might get somewhere with --use-angle=gl instead of --use-gl=desktop ; ANGLE's OpenGL backend is well tested, while Chromium's raw OpenGL backend on Windows is unsupported.

-Ken



--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss


Reply all
Reply to author
Forward
0 new messages