Page MenuHomePhabricator

Hardware Volume Rendering and hardware shaders do not run on all linux machines
Closed, ResolvedPublic

Description

On some Linux machines the volume rendering only runs in software mode and hardware shaders can not be executed. the error message says: could not find OpenGL 2.0. It is easy to test, whether a machine supports hardware rendering: start 3M, load ball.stl, open the property list view and change the shader from fixed to "mitkshaderlighing". If the appearance in the 3D view changes, everythig's fine. If not, your machine has the malfunctioning configuration. Everyone who has a linux machine should test this and post his configuration here... the version fo the OS, Graphics driver, group membership of the current user ect.

Known computers, which do not work appropiately are:

Xin's
Michael M (with user hartmanp)
Daniel M

working

Sascha
Thiago

Event Timeline

Could everybody please add the name of his/her computer?

This would make it easier to collect information about system configuration.

Please also install and configure openssh-server and shorty check your ITK and VTK versions. Thanks.

(In reply to comment #1)

Please also install and configure openssh-server and shorty check your ITK and
VTK versions. Thanks.

I Think this is most important: VTK version and whether it is self-compiled, /opt/toolkits or distribution package!

The Problem seems to be a missing CMake Option in VTK. Everyone, who didi not compile VTK himself, should do so using the description on

http://mbits/mbiwiki/HowTo%3A%20Ben%C3%B6tigte%20Toolkits%20kompilieren

This solves the problem. The VTK versions /opt/toolkits do not have the option avaivable at present.

@Michael: Could you upload a proper compiled VTK to /opt/toolkits ?

Please comment on experiences with your local configurations here!!!

MBI029 (Sascha): Hardware VR works

Fedora 11
VTK 5.4.0 from /opt/toolkits/...
QT 4.5.2 (Fedora 11 rpm)

VTK_USE_QVTK_QTOPENGL seems to be OFF

After Sascha's comment I guess this issue is not solved yet.

I don't think that this has something to do with VTK_USE_QVTK_QTOPENGL. It is probably rather due to an incorrectly configured nvidia driver. Run "glxinfo" in a console to see if direct rendering is enabled. If not, check your /var/log/Xorg.0.log file.

The VTK_USE_QVTK_QTOPENGL option solved the problem on Michi's computer without any modification in the driver configuration.
Maybe there are some things that can influence that, but this variable has definitely something to do.

i agree with thiago. philllippp told me that it also works on Xin`s PC by turning VTK_USE_QVTK_QTOPENGL on. is that right?
i dont think that QTOpenGl changes something in your X config files. And if it did, that would be an acceptable solution for this bug.
Can we close it?

As michale commented, it works with the described option on xins computer now. Since there's no machine left with the described malfunction, the bug can be closed.

Sorry that I didn't follow the discussion..

This issue is not completely solved. I'd like to know

  • what the VTK build option VTK_USE_QVTK_QTOPENGL actually does
  • if VTK_USE_QVTK_QTOPENGL should be turned on for all builds in /opt/toolkits
    • does it do any harm / slowdown / ... ?

To learn about this stuff is a nice job for a bugsquashing party.

(I will now compile a VTK for Fedora 12 with VTK_USE_QVTK_QTOPENGL turned ON and see if it works).

The QtOpenGL module offers classes that make it easy to use OpenGL in Qt applications. Obviously, VTK uses this API to work with OpenGL in their Qt Widgets. Unfortunately, i did not find any good documentation on how this API is actually incorporated in VTK and what effects occur when turning this feature off

can we close this? problem is solved by toggling VTK_USE_QVTK_QTOPENGL