View Revisions: Issue #4252

Summary 0004252: OpenGL2: Slicer crashes on start when started through Windows Remote Desktop
Revision 2016-09-09 09:45 by lassoan
Description

Windows Remote Desktop seems to support only OpenGL1.1. If Slicer with OpenGL2 is attempted to started in a remote session, Slicer crashes. If Slicer is already running when the Remote Desktop session starts then there is no problem.

If Slicer is built with console display enabled, it prints this message:
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.
Segmentation doesn't appear in slice viewer - add to higher level layer?

But by default console display is disabled so the user has no idea what's happening, why Slicer crashes.

Revision 2016-09-09 09:38 by lassoan
Description

Windows Remote Desktop seems to support only OpenGL1.1. If Slicer with OpenGL2 is attempted to started in a remote session, Slicer crashes.

If Slicer is built with console display enabled, it prints this message:
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.
Segmentation doesn't appear in slice viewer - add to higher level layer?

But by default console display is disabled so the user has no idea what's happening, why Slicer crashes.