[vtkusers] OpenGL driver issue with VTK 7.0

[ianl]

Hi, I have now had a chance to do some testing.

The setups I tested had any additional graphics card removed/disabled and
the on-board Intel graphics enabled and updated to the latest drivers from
the Intel website (not via the Windows update driver button as this does not
always get the latest).

Testing was carried out with our test app which loads a 250 slice CT image
set and displays it as 3 MPR views and a 3D volume. The app was compiled
with a build of VTK from master taken on 23rd September 2016, 64 bit release
built on Visual Studio 2012. The test app was run on the target systems
prior to disabling the main graphics cards to ensure it was working as
expected. The following two systems were checked:

-----------
Ivy Bridge based system - Intel i5-3470 with HD 2500 graphics running
Windows 7:
The test app worked fine, performance was reduced as expected. While
manipulating the volume, the graphics driver reset and this was not handled
gracefully with the app crashing. It is not clear whether this was due to
VTK or our app code. No useful logging was generated and the app then went
on to run fine after restarting.

-----------
Sandy Bridge based system - Intel Core i3-2120, HD 2000 graphics running
Windows 10:
The test app crashed on startup, giving the following error during window
creation:

<10256> 2016/10/03 17:02:19.032 : Error raised by vtk : ERROR: In
D:\Build\VTK\VTK 7.1.x
23_09_2016\VTKSource\Rendering\OpenGL2\vtkOpenGLRenderWindow.cxx, line 640
vtkWin32OpenGLRenderWindow (0000000022F61160): 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.

-----------
Hope this helps - it looks likely that the Sandy Bridge fix has not fully
worked from my testing. The Ivy Bridge variant seemed better, but it is not
clear what the cause of the driver reset was.



--
View this message in context: http://vtk.1045678.n5.nabble.com/OpenGL-driver-issue-with-VTK-7-0-tp5737190p5740653.html
Sent from the VTK - Users mailing list archive at Nabble.com.