Details
-
Bug
-
Resolution: Out of scope
-
P3: Somewhat important
-
None
-
5.9
-
None
-
{noformat}
Qt 5.9.0 (i386-little_endian-ilp32 shared (dynamic) release build; by GCC 5.3.0) on "windows"
OS: Windows 7 SP 1 (6.1) [winnt version 6.1.7601]
Architecture: x86_64; features: SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 AVX AVX2
SSL is not supported.
Platform capabilities: ThreadedPixmaps OpenGL ThreadedOpenGL WindowMasks MultipleWindows ForeignWindows NonFullScreenWindows NativeWidgets WindowManagement RasterGLSurface AllGLFunctionsQueryable SwitchableWidgetComposition
Theme:
Available : windows
Styles : WindowsVista,WindowsXP,Windows
System font : "MS Shell Dlg 2" 8
Native file dialog
Screens: 1, High DPI scaling: inactive
# 0 "\\.\DISPLAY1" Depth: 32 Primary: yes
Manufacturer:
Model:
Serial number:
Geometry: 2560x1440+0+0 Available: 2560x1400+0+0
Physical size: 903x508 mm Refresh: 60 Hz Power state: 0
Physical DPI: 72.0089,72 Logical DPI: 96,96 Subpixel_None
DevicePixelRatio: 1 Pixel density: 1
Primary orientation: 2 Orientation: 2 Native orientation: 0 OrientationUpdateMask: 0
Dynamic GL LibGL Vendor: VMware, Inc.
Renderer: Gallium 0.4 on SVGA3D; build: RELEASE; LLVM;
Version: 3.0 Mesa 11.2.0 (git-b9d3786)
Shading language: 1.30
Format: Version: 3.0 Profile: 0 Swap behavior: 2 Buffer size (RGBA): 8,8,8,8 Depth buffer: 24 Stencil buffer: 8
GPU:
Card name: VMware SVGA 3D
Driver Name: vm3dum.dll
Driver Version: 8.15.1.50
Vendor ID: 0x15AD
Device ID: 0x0405
SubSys ID: 0x040515AD
Revision ID: 0x0000
{noformat}{noformat} Qt 5.9.0 (i386-little_endian-ilp32 shared (dynamic) release build; by GCC 5.3.0) on "windows" OS: Windows 7 SP 1 (6.1) [winnt version 6.1.7601] Architecture: x86_64; features: SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 AVX AVX2 SSL is not supported. Platform capabilities: ThreadedPixmaps OpenGL ThreadedOpenGL WindowMasks MultipleWindows ForeignWindows NonFullScreenWindows NativeWidgets WindowManagement RasterGLSurface AllGLFunctionsQueryable SwitchableWidgetComposition Theme: Available : windows Styles : WindowsVista,WindowsXP,Windows System font : "MS Shell Dlg 2" 8 Native file dialog Screens: 1, High DPI scaling: inactive # 0 "\\.\DISPLAY1" Depth: 32 Primary: yes Manufacturer: Model: Serial number: Geometry: 2560x1440+0+0 Available: 2560x1400+0+0 Physical size: 903x508 mm Refresh: 60 Hz Power state: 0 Physical DPI: 72.0089,72 Logical DPI: 96,96 Subpixel_None DevicePixelRatio: 1 Pixel density: 1 Primary orientation: 2 Orientation: 2 Native orientation: 0 OrientationUpdateMask: 0 Dynamic GL LibGL Vendor: VMware, Inc. Renderer: Gallium 0.4 on SVGA3D; build: RELEASE; LLVM; Version: 3.0 Mesa 11.2.0 (git-b9d3786) Shading language: 1.30 Format: Version: 3.0 Profile: 0 Swap behavior: 2 Buffer size (RGBA): 8,8,8,8 Depth buffer: 24 Stencil buffer: 8 GPU: Card name: VMware SVGA 3D Driver Name: vm3dum.dll Driver Version: 8.15.1.50 Vendor ID: 0x15AD Device ID: 0x0405 SubSys ID: 0x040515AD Revision ID: 0x0000 {noformat}
Description
I run Windows using VMware Fusion on my Mac. My application uses Qt3D.
When I look at the OpenGL capabilities of Windows under VMware using "OpenGL Extensions Viewer" (http://realtech-vr.com/admin/glview ) it tells me that it is capable of using a 3.3 core profile:
Renderer: Gallium 0.4 on SVGA3D; build: RELEASE; LLVM;
Vendor: VMware, Inc.
Memory: 384 MB
Version: 3.3 (Core Profile) Mesa 11.2.0 (git-b9d3786)
Shading language version: 3.30
I can run the real time tests for 3.3 and it works fine.
No matter what I try from within Qt (5.9), I can't get it to give me that profile. If I request 3.3 Core, this is the "best" profile I can get out of Qt:
OpenGL Info
Vendor: VMware, Inc.
Renderer: Gallium 0.4 on SVGA3D; build: RELEASE; LLVM;
Version: 3.0 Mesa 11.2.0 (git-b9d3786)
Shading language: 1.30
Requested format: (version 3.3, profile [core], depthBufferSize 24, stencilBufferSize 8, rgba BufferSizes (-1, -1, -1, -1 ), samples 8, swapBehavior 0, swapInterval 1)
Current format: (version 3.0, profile [none], depthBufferSize 24, stencilBufferSize 8, rgba BufferSizes (8, 8, 8, 8 ), samples 8, swapBehavior 2, swapInterval 1)
I've tried all different combinations of versions and CoreProfile vs. CompatibilityProfile with no luck.
qtdiag also only reports a 3.0 context (see Environment section - no surprise since I think I'm using the same method to request and check the context).