Details
-
Bug
-
Resolution: Unresolved
-
P2: Important
-
None
-
5.9.4, 5.9.5
-
None
-
See above.
Description
1) Using this environment, we get only a black screen for any OpenGL view in any Qt-based application:
- Using Remote Desktop
- To connect to a VM running inside a VMWare product (I believe VMSphere) [with VMWare Tools 10.0.9 installed on client OS)
- Windows 2008 R2 Enterprise, SP1 installed on the VM (64-bit)
This is easily reproducible using both QDemoBrowser and the Qt Cube OpenGL ES demos, unchanged from their original source code, both built in 64-bit Release using QtCreator and deployed using the windeployqt command-line tool. When the apps run, any Qt GUI is visible (menu bar, window border) but the OpenGL widget is entirely black.
Please note that the this bug is only visible on this specific setup (VM running Windows 2008 R2).
2) We also have the same issue when running with the following setup (which does NOT use Remote Desktop):
- Running on a VM using VMWare Workstation 12
- Running Windows 7 (both x86 and 64-bit) OS
- Using VMWare Workstation Hardware Compatibility 6.5 (I believe this is due to having created a VM with an older version of VMWare Workstation - such as version 8 or 9, and using that VM in VMWare Workstation 12)
Qt demo apps that use OpenGL again show a black screen OR outright crash. This problem goes away, however, in this case, by changing VMWare's Hardware Compatibility version to "12"
There are other configurations (running in VMWare) that also show black screens (and for our Qt applications, even crash) but at the moment I'm having trouble logging into some of our remote VM machines, so I'll have to update this bug report with more information later.
PLEASE NOTE!
Before you write this off as a 'VMWare Issue', it should be noted that Chrome runs various WebGL demos just fine (albeit very slowly, indicating softwareGL mode). I've read that Chrome uses OpenGL ES as its implementation for WebGL content, showing that OpenGL ES *works* inside VMWare on these 'problem' machines. This points to an issue with Qt's implementation. [That, OR Chrome somehow detects that it should use software GL for compatibility.]