Slicer crashes on start when started through Windows Remote Desktop => OpenGL2: Slicer crashes on start when started through Windows Remote Desktopįile Added: Screenshot from 18-59-41.pngįile Added: Screenshot from 11-58-52. Otherwise, did someone try to build with VTK_USE_OPENGL_DELAYED_LOAD set to ON ? You can use other remoting software such as nomachine A utility tool to check the performance of your OpenGL. Features and extensions are either supported or accepted and updated, ensuring developers don’t have to wait until the next release for a feature they wish to use. Remote desktop note that it only supports OpenGL 3.2 with nvidia The OpenGL download Windows 10 is free of cost and evolves continuously. If you are on windows and using Microsoft ![]() Later and make sure your driver in Mesa supports OpenGL 3.2 suchĪs llvmpipe or openswr. If you are using Mesa please make sure you have version 11.2 or Please update your video card driver to the latest version. Unable to find a valid OpenGL 3.2 or later implementation. On some linux drivers (such as nvidia version 384.111 and 387.34) setting theĬontext to zero causes a segfault so check before setting in cases where theĭestruction may be trying to pop to a zero context.Īnd following r27080 the following was integrated: * Improve error message reported when OpenGL is not supported. Segmentation doesn't appear in slice viewer - add to higher level layer?īut by default console display is disabled so the user has no idea what's happening, why Slicer crashes.įollowing r27104, the following is integrated: * (from Francois Budin Check that context exists before trying to pop context. 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. The OpenGL Extension viewer 5.02 reports version 3.1 of OpenGL, the latest 6.18 version simply crashes when querying the Intel HD Graphics 3000. 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. If Slicer is built with console display enabled, it prints this message: If Slicer is already running when the Remote Desktop session starts then there is no problem. If Slicer with OpenGL2 is attempted to started in a remote session, Slicer crashes. ![]() Windows Remote Desktop seems to support only OpenGL1.1. 0004252: OpenGL2: Slicer crashes on start when started through Windows Remote Desktop
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |