Viber appears to be written using Qt framework (therefore using ANGLE). Both Opera and Brave are also Chromium-based. There was another recent post where the user encountered render problems with Opera, Brave and Viber. If the problem was solely on the SVGA driver, how does that explain it does not seem to happen on Windows VMs that run on Workstation on Linux hosts and macOS Fusion? Just relying on Chromium developer comment also does not explain why it does not happen to your Edge browser. Unless the vmx entries you added resulted in disabled DX11renderer and the GLRenderer was not enabled (typo error perhaps?)Īs I said, I don't know where the root cause of the problem. So it is strange that once you switched to GLRenderer that the Nvidia GPU is not being used and 3D acceleration is disabled (hence disables Chrome graphics acceleration). With Intel HD630 as default and OpenGL renderer in the vmx, the horrible rendering problems even with Windows logon/menus still occur though. With laptops, Nvidia Control Panel lets you choose a Default graphics processor so there is no need to use to choose. mks-sandbox.exe still appears on GPU Activity and Chrome inside still has "Hardware Acceleration"). Switching to GLRenderer for VMware Workstation also does not disable 3D acceleraton (i.e. I don't get that problem (white screen, rendering problemsw with Chrome) with a laptop with Skylake CPU HD630 with GTX 960M on a Windows 11 Home host. However, it's time someone compelled VMware to acknowledge and accept responsibility for it choosing either to devote resounces towards a solution, or to take the hit and let it ride. I simply use an alternate browser in my Windows VMs due to the bug, and I imagine many others do the same. Notice that I personally did not initiate this thread, and modest amount of Google searching will reveal numerous reports of the same issue encountered worldwide. VMware developers should have addressed it by now since Chromium developers have clearly identified the VMware SVGA driver as the root of the problem (per my fourth post). You're correct, it has existed for far too long as it affects hundreds, if not thousands of users with and without support agreements. The other configurations and platforms you cited are irrelevant to this issue. I challenge you to submit any reproducible configuration meeting the above criteria that solves the problem very clearly defined in my third post. However ANY GPU on a Windows 10 host running VMware Workstation 16 Pro with a Windows 10 guest will exhibit the problem in Google Chrome. Both of them support OpenGL 4.x and I can reproduce the problem using either one. My GPUs are NVidia Geforce GTX 1050Ti and I ntel HD Graphics 630. Hardware Compatibility is Workstation 16.x.
0 Comments
Leave a Reply. |