<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">2016-06-26 11:42 GMT+02:00 Elvis Stansvik <span dir="ltr"><<a href="mailto:elvis.stansvik@orexplore.com" target="_blank">elvis.stansvik@orexplore.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><div class="h5">2016-06-26 11:05 GMT+02:00 Elvis Stansvik <span dir="ltr"><<a href="mailto:elvis.stansvik@orexplore.com" target="_blank">elvis.stansvik@orexplore.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span>2016-06-26 11:01 GMT+02:00 Elvis Stansvik <span dir="ltr"><<a href="mailto:elvis.stansvik@orexplore.com" target="_blank">elvis.stansvik@orexplore.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span>2016-05-25 17:08 GMT+02:00 Elvis Stansvik <span dir="ltr"><<a href="mailto:elvis.stansvik@orexplore.com" target="_blank">elvis.stansvik@orexplore.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span>2016-05-25 13:49 GMT+02:00 Ken Martin <span dir="ltr"><<a href="mailto:ken.martin@kitware.com" target="_blank">ken.martin@kitware.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Yes, you should be fine with VTK 7.0, OpenGL2 and Haswell. - Ken</div></blockquote></span></div></div></div></blockquote><div><br></div></span><div>Hm, initially it seemed like things were working fine. I was using the GPU based volume mapper without problems (using a modified QVTKRenderWindowInteractor), and I _think_ I was using the OpenGL2 backend (how can I tell btw?).<br><br></div><div>But now, as I started trying to make a QOpenGLWidget-based Qt<->VTK adapter class instead, I get the following when trying to initialize the render window:<br><br>ERROR: In /home/estan/Blandat/vtk-python3/src/VTK-7.0.0/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, line 545<br>vtkGenericOpenGLRenderWindow (0x205fb10): 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.<br><br></div><div>And sure enough:<br><br>estan@newton:~$ glxinfo | grep "OpenGL version"<br>OpenGL version string: 3.0 Mesa 11.2.0<br><br></div><div>However:<br><br>estan@newton:~$ glxinfo | grep "OpenGL core profile version"<br>OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.2.0<br><br></div><div>I'm a little unsure about which of these version numbers I should be looking at to see if my graphics has what it takes.<br><br></div><div>Also, I'm now even unsure if I was ever using the OpenGL2 backend.. perhaps VTK was falling back to OpenGL1 somehow, and that's why it worked in the beginning? Or is the selection of backend always a compile time thing?<br><br></div><div>I build my VTK 7.0.0 in a Personal Package Archive at:<br><br> <a href="https://launchpad.net/~elvstone/+archive/ubuntu/vtk7" target="_blank">https://launchpad.net/~elvstone/+archive/ubuntu/vtk7</a><br><br></div><div>and the full build log is at:<br><br> <a href="https://launchpadlibrarian.net/261625779/buildlog_ubuntu-xenial-amd64.vtk7_7.0.0-0ubuntu2_BUILDING.txt.gz" target="_blank">https://launchpadlibrarian.net/261625779/buildlog_ubuntu-xenial-amd64.vtk7_7.0.0-0ubuntu2_BUILDING.txt.gz</a></div></div></div></div></blockquote><div><br></div></span><div>Okay, so looking at that build log, I see:<br><br><pre>-- Setting rendering backend to 'OpenGL2' as none was specified.
-- Backend OpenGL modules: vtkRenderingContextOpenGL;vtkRenderingOpenGL;vtkRenderingLIC;vtkRenderingVolumeOpenGL;vtkRenderingGL2PS
-- Backend OpenGL2 modules: vtkRenderingContextOpenGL2;vtkRenderingVolumeOpenGL2;vtkRenderingOpenGL2;vtkRenderingLICOpenGL2;vtkDomainsChemistryOpenGL2
-- Enabling modules for OpenGL2.<br></pre><br>Does this mean I'll always be using the OpenGL2 backend, or that OpenGL vs OpenGL2 is a runtime choice?<span><font color="#888888"><br></font></span></div></div></div></div></blockquote><div><br></div></div></div><div>I've now done some testing here at home, on my old Sandybridge laptop which I think only has a HD 3000 graphics chip:<br><br>[estan@pyret ~]$ glxinfo | grep "OpenGL version"<br>OpenGL version string: 3.0 Mesa 11.2.2<br><br></div><div>and the "Extended renderer info" section says:<br><br>Extended renderer info (GLX_MESA_query_renderer):<br> Vendor: Intel Open Source Technology Center (0x8086)<br> Device: Mesa DRI Intel(R) Sandybridge Mobile (0x126)<br> Version: 11.2.2<br> Accelerated: yes<br> Video memory: 1536MB<br> Unified memory: yes<br> Preferred profile: core (0x1)<br> Max core profile version: 3.3<br> Max compat profile version: 3.0<br> Max GLES1 profile version: 1.1<br> Max GLES[23] profile version: 3.0<br><br></div><div>And it turns out that all I had to do in my little QOpenGLWidget-adapter was:<br><br> surfaceFormat.setMajorVersion(3)<br> surfaceFormat.setMinorVersion(2)<br> surfaceFormat.setProfile(QSurfaceFormat.CompatibilityProfile)<br> self.setFormat(surfaceFormat)<br><br></div><div>to request OpenGL 3.2 compatibility profile. After this I no longer get the error and rendering seems to work.<br><br></div><div>I'm actually a little surprised this works, since I didn't think my old home laptop would support the OpenGL2 backend. And the glxinfo output shows "Max compat profile version: 3.0". But printing the .format().majorVersion() and .format().minorVersion() after setting it on the QOpenGLWidget confirms that I've gotten the 3.2 format set.<br><br></div><div>Oh well, I'm happy now, but would still like some clarification from someone who knows more than me about these things.<span class=""><font color="#888888"><br></font></span></div></div></div></div></blockquote><div><br></div><div>For full disclosure, on this older home laptop I run Arch Linux and not Kubuntu 16.04 like at work. The VTK I build using a custom Arch Linux package which does<br><br> for lib in EXPAT FREETYPE JPEG PNG TIFF ZLIB LIBXML2 OGGTHEORA TWISTED ZOPE SIX AUTOBAHN MPI4PY JSONCPP GLEW GL2PS; do<br> cmake_system_flags+="-DVTK_USE_SYSTEM_${lib}:BOOL=ON "<br> done<br><br> ...<br><br> cmake \<br> -Wno-dev \<br> -DCMAKE_SKIP_RPATH=ON \<br> -DBUILD_SHARED_LIBS:BOOL=ON \<br> -DCMAKE_INSTALL_PREFIX:FILEPATH=/usr \<br> -DBUILD_DOCUMENTATION:BOOL=ON \<br> -DDOCUMENTATION_HTML_HELP:BOOL=ON \<br> -DDOCUMENTATION_HTML_TARZ:BOOL=ON \<br> -DBUILD_EXAMPLES:BOOL=ON \<br> -DVTK_USE_FFMPEG_ENCODER:BOOL=ON \<br> -DVTK_BUILD_ALL_MODULES:BOOL=ON \<br> -DVTK_USE_LARGE_DATA:BOOL=ON \<br> -DVTK_QT_VERSION:STRING="5" \<br> -DVTK_WRAP_JAVA:BOOL=ON \<br> -DVTK_WRAP_PYTHON:BOOL=ON \<br> -DVTK_WRAP_TCL:BOOL=ON \<br> -DCMAKE_CXX_FLAGS="-D__STDC_CONSTANT_MACROS" \<br> -DVTK_CUSTOM_LIBRARY_SUFFIX="" \<br> -DVTK_INSTALL_INCLUDE_DIR:PATH=include/vtk \<br> -DVTK_INSTALL_TCL_DIR=/usr/lib/tcl${_tkver}/vtk/ \<br> -DVTK_PYTHON_VERSION=3 \<br> -DPYTHON_EXECUTABLE=/usr/bin/python3 \<br> -DPYTHON_INCLUDE_DIR=/usr/include/python3.5m \<br> -DPYTHON_LIBRARY=/usr/lib/<a href="http://libpython3.5m.so">libpython3.5m.so</a> \<br> -DVTK_USE_SYSTEM_HDF5=OFF \<br> ${cmake_system_flags} \<br> -DCMAKE_BUILD_TYPE=Release \<br> "${srcdir}/VTK-$pkgver" \<br> -GNinja<br><br></div><div> ninja<br><br></div><div>to build VTK. I don't have the build log for it, but I would think the above would give me the OpenGL2 backend (?), since I didn't specify anything special in the cmake command.<br><br></div><div>Elvis<br><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><span class=""><font color="#888888"><br></font></span></div><span class=""><font color="#888888"><div>Elvis<br><br></div></font></span><div><div class="h5"><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><span><font color="#888888"><br></font></span></div><span><font color="#888888"><div>Elvis<br></div></font></span><div><div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br><br></div><div>Any advice is much appreciated!<br><br></div><div>I'm considering switching to the old OpenGL1 backend anyway, since I realized my laptop at home only has a Sandybridge chipset (at work it's Haswell), and it's convenient to be able to do some work from my home laptop. But I'd like to know why I get the above error on my work laptop, since I thought it'd be compatible.<span><font color="#888888"><br><br></font></span></div><span><font color="#888888"><div>Elvis<br><br></div></font></span><span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span><div><br></div></span><div>Great, thanks!<span><font color="#888888"><br><br></font></span></div><span><font color="#888888"><div>Elvis<br> <br></div></font></span><span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Wed, May 25, 2016 at 4:50 AM, Elvis Stansvik <span dir="ltr"><<a href="mailto:elvis.stansvik@orexplore.com" target="_blank">elvis.stansvik@orexplore.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div><div dir="ltr"><div><div><div>Hi all,<br><br></div>I'm about to try a compile of VTK 7.0.0 release on Ubuntu 16.04 (Xenial).<br><br></div>The machine where I need this to run has a Haswell Intel graphics chip (Intel(R) HD Graphics 4400), which supports the OpenGL 3.3 profile. Will the new OpenGL backend (the version in 7.0.0) support this graphics card, or will I need to use the old backend with -DVTK_RENDERING_BACKEND=OpenGL?<br><br></div><div>I read that support for is for Ivy Bridge and later in 7.0.0, so I think I should be OK right?<br><br></div><div>Thanks in advance,<br></div><div>Elvis<br></div></div>
<br></div></div>_______________________________________________<br>
Powered by <a href="http://www.kitware.com" rel="noreferrer" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the VTK FAQ at: <a href="http://www.vtk.org/Wiki/VTK_FAQ" rel="noreferrer" target="_blank">http://www.vtk.org/Wiki/VTK_FAQ</a><br>
<br>
Search the list archives at: <a href="http://markmail.org/search/?q=vtkusers" rel="noreferrer" target="_blank">http://markmail.org/search/?q=vtkusers</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://public.kitware.com/mailman/listinfo/vtkusers" rel="noreferrer" target="_blank">http://public.kitware.com/mailman/listinfo/vtkusers</a><br>
<br></blockquote></div><span><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div>Ken Martin PhD<div>Chairman & CFO<br>Kitware Inc.<br>28 Corporate Drive<br>Clifton Park NY 12065<br><a href="tel:518%20371%203971" value="+15183713971" target="_blank">518 371 3971</a><div><br></div><div><span style="font-size:10pt;font-family:Tahoma,sans-serif">This communication,
including all attachments, contains confidential and legally privileged
information, and it is intended only for the use of the addressee. Access to this email by anyone else is
unauthorized. If you are not the intended recipient, any disclosure, copying,
distribution or any action taken in reliance on it is prohibited and may be
unlawful. If you received this communication in error please notify us
immediately and destroy the original message.
Thank you.</span></div></div></div>
</font></span></div>
</blockquote></span></div><br></div></div>
</blockquote></span></div><br></div></div>
</blockquote></div></div></div><br></div></div>
</blockquote></div></div></div><br></div></div>
</blockquote></div><br></div></div>