Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

not compatible with webgl ? #19

Open
limbo127 opened this issue Nov 1, 2024 · 3 comments
Open

not compatible with webgl ? #19

limbo127 opened this issue Nov 1, 2024 · 3 comments

Comments

@limbo127
Copy link

limbo127 commented Nov 1, 2024

Hi there,

I've set up an MVisor VM running on Windows 11 with an MVisor vGPU. All initial tests seem fine (the vGPU is detected, and GPU benchmarks like FurMark pass).
However, when I use browsers like Chrome, Edge, or Firefox, WebGL is still using a software renderer instead of the dedicated MVisor vGPU, as confirmed by the browser's graphics information (chrome://gpu or about:support).
Is this a normal occurrence? Our goal is to utilize the hardware acceleration provided by the vGPU.

Thanks,
Nicolas

@nooodles2023
Copy link
Collaborator

oh WebGL was not supported yet. WebGL doesn't use api exported from opengl32.dll.

@limbo127
Copy link
Author

limbo127 commented Nov 2, 2024

webgl using google Angle that's use backend as opengl, or directx on windows.
I'm trying to config angle --user-angle=gl or --use-gl=desktop without succes, I don't understand where the problem is, in theory the solution seems to be near, can you explain why ?

@nooodles2023
Copy link
Collaborator

nooodles2023 commented Nov 4, 2024

Maybe you could check if the opengl32.dll and MVisorVGPUx64.dll were loaded by chrome first.
If it called api in opengl32.dll but failed, try to use dbgview to get some debug info.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants