Re: [Paraview] OpenGL inside VMWare virtual machine
On Wed, Nov 15, 2017 at 11:40:43 -0500, Ken Martin wrote: > Basically there is a bug in Qt on windows where it refuses to see the 3.2 > context from Mesa because it is not a compatibility context. On startup, Qt makes a context without a profile. Mesa gives it the best compatibility profile it can: 2.0. Qt then interprets this as the highest OpenGL version available and clamps all requests to this version. The entire behavior is mystifying to me, but the issue has been filed here: https://bugreports.qt.io/browse/QTBUG-60742 --Ben ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] OpenGL inside VMWare virtual machine
Question not any more relevant: setting an environment variable before starting paraview does indeed the trick: it works now indeed as expected! Thanks and regards, Cornelis Am Mittwoch, den 15.11.2017, 18:54 +0100 schrieb Cornelis Bockemühl: > Thanks for the hint: I will definitely try this! > > > Only one question: you write environment which sounds like an environment variable, but maybe you mean a variable ti be set in the CMake configuration!?! > > Regards, Cornelis > > > > Am 15.11.2017 17:40 schrieb "Ken Martin" : > > > > This could be a PV Qt interaction. Try setting MESA_GL_VERSION_OVERRIDE=3.2 in your environment > > > > > > Basically there is a bug in Qt on windows where it refuses to see the 3.2 context from Mesa because it is not a compatibility context. > > > > > > > > On Wed, Nov 15, 2017 at 10:09 AM, Cornelis Bockemühl wrote: > > > Dear all, > > > > > > > > > > > > > > > > > > I know that I cannot go for any performance > > > > > > > > > > > > > > > > > > record with this setup, but having both systems available without reboot has advantages if it is about testing some new development. WOULD have - if it fully worked! So far it looks like I am "almost there" - however not knowing whether the last 10 meters will be feasible at all... > > > > > > This is my setup: > > > > > > > > > Main system: Opensuse Linux "Leap" 42.3, with Paraview reporting the following in the About dialog: > > > OpenGL Vendor: Intel Open Source Technology Center > > > OpenGL Version: 3.3 (Core Profile) Mesa 17.0.5 > > > OpenGL Renderer: Mesa DRI Intel(R) Ivybridge Mobile > > > > > > > > > On this system Paraview (latest version, self compiled) runs just fine. > > > > > > > > > Guest system inside VMWare Player version 14: Windows 10, with Paraview reporting the following: > > > OpenGL Vendor: VMware, Inc. > > > OpenGL Version: 3.3 (Core Profile) Mesa 11.2.0 (git-b9d3786) > > > OpenGL Renderer: Gallium 0.4 on SVGA3D; build: RELEASE; LLVM; > > > > > > > > > Here Paraview immediately complains on startup, reporting the following in the message output dialog: see below. > > > > > > > > > > > > > > > For me the version numbers look ok (OpenGL 3.3 is more > > > > > > > > > > > > than 3.2, and Mesa 11.2.0 is more than 10.6.5), but there is some "fineprint" about shader capabilities that are going a bit above my understanding... > > > > > > Anybody able to help with this? > > > > > > > > > Any possibility to "cheat" somehow? Note that I am certainly not going to render billions of data in this configuration! > > > > > > Or should I abandon this tricky setup altogether? > > > > > > Thanks and regards, > > > Cornelis > > > > > > > > > Here the error output from the Windows Paraview inside the VMWare virtual machine: > > > > > > > > > ERROR: In Z:\ultrabay\ParaView\Sources\ParaView- v5.4.1\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx, line 831 > > > > > > > > > > > > > > > > > > vtkGenericOpenGLRenderWindow > > > > > > > > > > > > > > > > > > (02438C350630): GL version 2.1 with the gpu_shader4 extension is not supported by your graphics driver but is required for the new OpenGL rendering backend. Please update your OpenGL driver. If you are using Mesa please make sure you have version 10.6.5 or later and make sure your driver in Mesa supports OpenGL 3.2. > > > > > > > > > ERROR: In Z:\ultrabay\ParaView\Sources\ParaView- v5.4.1\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 408 > > > vtkShaderProgram (02438C1B80C0): 1: #version 150 > > > 2: #ifdef GL_ES > > > 3: #if __VERSION__ == 300 > > > 4: #define attribute in > > > 5: #define varying out > > > 6: #endif // 300 > > > 7: #else // GL_ES > > > 8: #define highp > > > 9: #define mediump > > > 10: #define lowp > > > 11: #if __VERSION__ == 150 > > > 12: #define attribute in > > > 13: #define varying out > > > 14: #endif > > > 15: #endif // GL_ES > > > 16: > > > 17: > > > > > > > > > 18: /*=== == > > > 19: > > > 20: Program: Visualization Toolkit > > > 21: Module:vtkPolyDataVS.glsl > > > 22: > > > 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen > > > 24: All rights reserved. > > > > > > 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details. > > > 26: > > > > > > 27: This software is distributed WITHOUT ANY WARRANTY; without even > > > > > > 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR > > > > > > 29: PURPOSE. See the above copyright notice for more information. > > > 30: > > > > > > > > > 31: = */ > > > 32: > > > 33: attribute vec4 vertexMC; > > > 34: > > > 35: // frag position in VC > > > 36: //VTK::PositionVC::Dec > > > 37: > > > 38: // optional normal declaration > > > 39: //VTK::Normal::Dec > > > 40: > > > 41: // extra lighting parameters > > > 42: //VTK::Light::Dec > > > 43: > > > 44: // Texture coordinat
Re: [Paraview] OpenGL inside VMWare virtual machine
Thanks for the hint: I will definitely try this!
Only one question: you write environment which sounds like an environment
variable, but maybe you mean a variable ti be set in the CMake
configuration!?!
Regards, Cornelis
Am 15.11.2017 17:40 schrieb "Ken Martin" :
> This could be a PV Qt interaction. Try setting MESA_GL_VERSION_OVERRIDE=3.2
> in your environment
>
> Basically there is a bug in Qt on windows where it refuses to see the 3.2
> context from Mesa because it is not a compatibility context.
>
> On Wed, Nov 15, 2017 at 10:09 AM, Cornelis Bockemühl <
> cornelis.bockemu...@gmail.com> wrote:
>
>> Dear all,
>>
>> I know that I cannot go for any performance record with this setup, but
>> having both systems available without reboot has advantages if it is about
>> testing some new development. WOULD have - if it fully worked! So far it
>> looks like I am "almost there" - however not knowing whether the last 10
>> meters will be feasible at all...
>>
>> This is my setup:
>>
>> Main system: Opensuse Linux "Leap" 42.3, with Paraview reporting the
>> following in the About dialog:
>> OpenGL Vendor: Intel Open Source Technology Center
>> OpenGL Version: 3.3 (Core Profile) Mesa 17.0.5
>> OpenGL Renderer: Mesa DRI Intel(R) Ivybridge Mobile
>>
>> On this system Paraview (latest version, self compiled) runs just fine.
>>
>> Guest system inside VMWare Player version 14: Windows 10, with Paraview
>> reporting the following:
>> OpenGL Vendor: VMware, Inc.
>> OpenGL Version: 3.3 (Core Profile) Mesa 11.2.0 (git-b9d3786)
>> OpenGL Renderer: Gallium 0.4 on SVGA3D; build: RELEASE; LLVM;
>>
>> Here Paraview immediately complains on startup, reporting the following
>> in the message output dialog: see below.
>>
>> For me the version numbers look ok (OpenGL 3.3 is more than 3.2, and Mesa
>> 11.2.0 is more than 10.6.5), but there is some "fineprint" about shader
>> capabilities that are going a bit above my understanding...
>>
>> Anybody able to help with this?
>>
>> Any possibility to "cheat" somehow? Note that I am certainly not going to
>> render billions of data in this configuration!
>>
>> Or should I abandon this tricky setup altogether?
>>
>> Thanks and regards,
>> Cornelis
>>
>> Here the error output from the Windows Paraview inside the VMWare virtual
>> machine:
>>
>> ERROR: In Z:\ultrabay\ParaView\Sources\ParaView-v5.4.1\VTK\Rendering\O
>> penGL2\vtkOpenGLRenderWindow.cxx, line 831
>> vtkGenericOpenGLRenderWindow (02438C350630): GL version 2.1 with the
>> gpu_shader4 extension is not supported by your graphics driver but is
>> required for the new OpenGL rendering backend. Please update your OpenGL
>> driver. If you are using Mesa please make sure you have version 10.6.5 or
>> later and make sure your driver in Mesa supports OpenGL 3.2.
>>
>> ERROR: In
>> Z:\ultrabay\ParaView\Sources\ParaView-v5.4.1\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx,
>> line 408
>> vtkShaderProgram (02438C1B80C0): 1: #version 150
>> 2: #ifdef GL_ES
>> 3: #if __VERSION__ == 300
>> 4: #define attribute in
>> 5: #define varying out
>> 6: #endif // 300
>> 7: #else // GL_ES
>> 8: #define highp
>> 9: #define mediump
>> 10: #define lowp
>> 11: #if __VERSION__ == 150
>> 12: #define attribute in
>> 13: #define varying out
>> 14: #endif
>> 15: #endif // GL_ES
>> 16:
>> 17:
>> 18: /*==
>> ===
>> 19:
>> 20: Program: Visualization Toolkit
>> 21: Module:vtkPolyDataVS.glsl
>> 22:
>> 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen
>> 24: All rights reserved.
>> 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for
>> details.
>> 26:
>> 27: This software is distributed WITHOUT ANY WARRANTY; without even
>> 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A
>> PARTICULAR
>> 29: PURPOSE. See the above copyright notice for more information.
>> 30:
>> 31:
>> =*/
>> 32:
>> 33: attribute vec4 vertexMC;
>> 34:
>> 35: // frag position in VC
>> 36: //VTK::PositionVC::Dec
>> 37:
>> 38: // optional normal declaration
>> 39: //VTK::Normal::Dec
>> 40:
>> 41: // extra lighting parameters
>> 42: //VTK::Light::Dec
>> 43:
>> 44: // Texture coordinates
>> 45: //VTK::TCoord::Dec
>> 46:
>> 47: // material property values
>> 48: //VTK::Color::Dec
>> 49:
>> 50: // clipping plane vars
>> 51: //VTK::Clip::Dec
>> 52:
>> 53: // camera and actor matrix values
>> 54: uniform mat4 MCDCMatrix;
>> 55:
>> 56: // Apple Bug
>> 57: //VTK::PrimID::Dec
>> 58:
>> 59: // Value raster
>> 60: //VTK::ValuePass::Dec
>> 61:
>> 62: void main()
>> 63: {
>> 64: //VTK::Color::Impl
>> 65:
>> 66: //VTK::Normal::Impl
>> 67:
>> 68: //VTK::TCoord::Impl
>> 69:
>> 70: //VTK::Clip::Impl
>> 71:
>> 72: //VTK::PrimID::Impl
>> 73:
>> 74: gl_Position = MCDCMatrix * vertexMC;
>> 75:
>> 76:
>> 77: //VTK::ValuePass::Impl
>> 78:
>> 79: //VTK::Light::Impl
>> 80: }
>> 81:
>>
>>
>> ERROR
Re: [Paraview] OpenGL inside VMWare virtual machine
This could be a PV Qt interaction. Try setting MESA_GL_VERSION_OVERRIDE=3.2
in your environment
Basically there is a bug in Qt on windows where it refuses to see the 3.2
context from Mesa because it is not a compatibility context.
On Wed, Nov 15, 2017 at 10:09 AM, Cornelis Bockemühl <
cornelis.bockemu...@gmail.com> wrote:
> Dear all,
>
> I know that I cannot go for any performance record with this setup, but
> having both systems available without reboot has advantages if it is about
> testing some new development. WOULD have - if it fully worked! So far it
> looks like I am "almost there" - however not knowing whether the last 10
> meters will be feasible at all...
>
> This is my setup:
>
> Main system: Opensuse Linux "Leap" 42.3, with Paraview reporting the
> following in the About dialog:
> OpenGL Vendor: Intel Open Source Technology Center
> OpenGL Version: 3.3 (Core Profile) Mesa 17.0.5
> OpenGL Renderer: Mesa DRI Intel(R) Ivybridge Mobile
>
> On this system Paraview (latest version, self compiled) runs just fine.
>
> Guest system inside VMWare Player version 14: Windows 10, with Paraview
> reporting the following:
> OpenGL Vendor: VMware, Inc.
> OpenGL Version: 3.3 (Core Profile) Mesa 11.2.0 (git-b9d3786)
> OpenGL Renderer: Gallium 0.4 on SVGA3D; build: RELEASE; LLVM;
>
> Here Paraview immediately complains on startup, reporting the following in
> the message output dialog: see below.
>
> For me the version numbers look ok (OpenGL 3.3 is more than 3.2, and Mesa
> 11.2.0 is more than 10.6.5), but there is some "fineprint" about shader
> capabilities that are going a bit above my understanding...
>
> Anybody able to help with this?
>
> Any possibility to "cheat" somehow? Note that I am certainly not going to
> render billions of data in this configuration!
>
> Or should I abandon this tricky setup altogether?
>
> Thanks and regards,
> Cornelis
>
> Here the error output from the Windows Paraview inside the VMWare virtual
> machine:
>
> ERROR: In Z:\ultrabay\ParaView\Sources\ParaView-v5.4.1\VTK\Rendering\
> OpenGL2\vtkOpenGLRenderWindow.cxx, line 831
> vtkGenericOpenGLRenderWindow (02438C350630): GL version 2.1 with the
> gpu_shader4 extension is not supported by your graphics driver but is
> required for the new OpenGL rendering backend. Please update your OpenGL
> driver. If you are using Mesa please make sure you have version 10.6.5 or
> later and make sure your driver in Mesa supports OpenGL 3.2.
>
> ERROR: In
> Z:\ultrabay\ParaView\Sources\ParaView-v5.4.1\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx,
> line 408
> vtkShaderProgram (02438C1B80C0): 1: #version 150
> 2: #ifdef GL_ES
> 3: #if __VERSION__ == 300
> 4: #define attribute in
> 5: #define varying out
> 6: #endif // 300
> 7: #else // GL_ES
> 8: #define highp
> 9: #define mediump
> 10: #define lowp
> 11: #if __VERSION__ == 150
> 12: #define attribute in
> 13: #define varying out
> 14: #endif
> 15: #endif // GL_ES
> 16:
> 17:
> 18: /*==
> ===
> 19:
> 20: Program: Visualization Toolkit
> 21: Module:vtkPolyDataVS.glsl
> 22:
> 23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen
> 24: All rights reserved.
> 25: See Copyright.txt or http://www.kitware.com/Copyright.htm for
> details.
> 26:
> 27: This software is distributed WITHOUT ANY WARRANTY; without even
> 28: the implied warranty of MERCHANTABILITY or FITNESS FOR A
> PARTICULAR
> 29: PURPOSE. See the above copyright notice for more information.
> 30:
> 31:
> =*/
> 32:
> 33: attribute vec4 vertexMC;
> 34:
> 35: // frag position in VC
> 36: //VTK::PositionVC::Dec
> 37:
> 38: // optional normal declaration
> 39: //VTK::Normal::Dec
> 40:
> 41: // extra lighting parameters
> 42: //VTK::Light::Dec
> 43:
> 44: // Texture coordinates
> 45: //VTK::TCoord::Dec
> 46:
> 47: // material property values
> 48: //VTK::Color::Dec
> 49:
> 50: // clipping plane vars
> 51: //VTK::Clip::Dec
> 52:
> 53: // camera and actor matrix values
> 54: uniform mat4 MCDCMatrix;
> 55:
> 56: // Apple Bug
> 57: //VTK::PrimID::Dec
> 58:
> 59: // Value raster
> 60: //VTK::ValuePass::Dec
> 61:
> 62: void main()
> 63: {
> 64: //VTK::Color::Impl
> 65:
> 66: //VTK::Normal::Impl
> 67:
> 68: //VTK::TCoord::Impl
> 69:
> 70: //VTK::Clip::Impl
> 71:
> 72: //VTK::PrimID::Impl
> 73:
> 74: gl_Position = MCDCMatrix * vertexMC;
> 75:
> 76:
> 77: //VTK::ValuePass::Impl
> 78:
> 79: //VTK::Light::Impl
> 80: }
> 81:
>
>
> ERROR: In
> Z:\ultrabay\ParaView\Sources\ParaView-v5.4.1\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx,
> line 409
> vtkShaderProgram (02438C1B80C0): 0:1(10): error: GLSL 1.50 is not
> supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, and 3.00 ES
>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/open
[Paraview] OpenGL inside VMWare virtual machine
Dear all,
I know that I cannot go for any performance record with this setup, but
having both systems available without reboot has advantages if it is
about testing some new development. WOULD have - if it fully worked! So
far it looks like I am "almost there" - however not knowing whether the
last 10 meters will be feasible at all...
This is my setup:
Main system: Opensuse Linux "Leap" 42.3, with Paraview reporting the
following in the About dialog:
OpenGL Vendor: Intel Open Source Technology Center
OpenGL Version: 3.3 (Core Profile) Mesa 17.0.5
OpenGL Renderer: Mesa DRI Intel(R) Ivybridge Mobile
On this system Paraview (latest version, self compiled) runs just fine.
Guest system inside VMWare Player version 14: Windows 10, with Paraview
reporting the following:
OpenGL Vendor: VMware, Inc.
OpenGL Version: 3.3 (Core Profile) Mesa 11.2.0 (git-b9d3786)
OpenGL Renderer: Gallium 0.4 on SVGA3D; build: RELEASE; LLVM;
Here Paraview immediately complains on startup, reporting the following
in the message output dialog: see below.
For me the version numbers look ok (OpenGL 3.3 is more than 3.2, and
Mesa 11.2.0 is more than 10.6.5), but there is some "fineprint" about
shader capabilities that are going a bit above my understanding...
Anybody able to help with this?
Any possibility to "cheat" somehow? Note that I am certainly not going
to render billions of data in this configuration!
Or should I abandon this tricky setup altogether?
Thanks and regards,
Cornelis
Here the error output from the Windows Paraview inside the VMWare
virtual machine:
ERROR: In Z:\ultrabay\ParaView\Sources\ParaView-
v5.4.1\VTK\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx, line 831
vtkGenericOpenGLRenderWindow (02438C350630): GL version 2.1 with
the gpu_shader4 extension is not supported by your graphics driver but
is required for the new OpenGL rendering backend. Please update your
OpenGL driver. If you are using Mesa please make sure you have version
10.6.5 or later and make sure your driver in Mesa supports OpenGL 3.2.
ERROR: In Z:\ultrabay\ParaView\Sources\ParaView-
v5.4.1\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 408
vtkShaderProgram (02438C1B80C0): 1: #version 150
2: #ifdef GL_ES
3: #if __VERSION__ == 300
4: #define attribute in
5: #define varying out
6: #endif // 300
7: #else // GL_ES
8: #define highp
9: #define mediump
10: #define lowp
11: #if __VERSION__ == 150
12: #define attribute in
13: #define varying out
14: #endif
15: #endif // GL_ES
16:
17:
18:
/*=
19:
20: Program: Visualization Toolkit
21: Module:vtkPolyDataVS.glsl
22:
23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen
24: All rights reserved.
25: See Copyright.txt or http://www.kitware.com/Copyright.htm for
details.
26:
27: This software is distributed WITHOUT ANY WARRANTY; without
even
28: the implied warranty of MERCHANTABILITY or FITNESS FOR A
PARTICULAR
29: PURPOSE. See the above copyright notice for more information.
30:
31:
===
==*/
32:
33: attribute vec4 vertexMC;
34:
35: // frag position in VC
36: //VTK::PositionVC::Dec
37:
38: // optional normal declaration
39: //VTK::Normal::Dec
40:
41: // extra lighting parameters
42: //VTK::Light::Dec
43:
44: // Texture coordinates
45: //VTK::TCoord::Dec
46:
47: // material property values
48: //VTK::Color::Dec
49:
50: // clipping plane vars
51: //VTK::Clip::Dec
52:
53: // camera and actor matrix values
54: uniform mat4 MCDCMatrix;
55:
56: // Apple Bug
57: //VTK::PrimID::Dec
58:
59: // Value raster
60: //VTK::ValuePass::Dec
61:
62: void main()
63: {
64: //VTK::Color::Impl
65:
66: //VTK::Normal::Impl
67:
68: //VTK::TCoord::Impl
69:
70: //VTK::Clip::Impl
71:
72: //VTK::PrimID::Impl
73:
74: gl_Position = MCDCMatrix * vertexMC;
75:
76:
77: //VTK::ValuePass::Impl
78:
79: //VTK::Light::Impl
80: }
81:
ERROR: In Z:\ultrabay\ParaView\Sources\ParaView-
v5.4.1\VTK\Rendering\OpenGL2\vtkShaderProgram.cxx, line 409
vtkShaderProgram (02438C1B80C0): 0:1(10): error: GLSL 1.50 is not
supported. Supported versions are: 1.10, 1.20, 1.30, 1.00 ES, and 3.00
ES___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView
Search the list archives at: http://markmail.org/search/?q=ParaView
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview
