Sorry for the delay on this-- things have been hectic the past few months. This issue has been fixed in the VirtualGL SVN repository and will be rolled into a new release within the next week. In a nutshell, VGL was not properly handling cases in which glXSwapBuffers() was called with a drawable that was not current. A reply from one of the voreen developers in their forum gave me the critical clue.
On 2/10/14 8:44 AM, Dr. Roman Grothausmann wrote: > Just noticed that when voreen (double buffering disabled) is running with > vglrun > the graphics of other 3D apps started with vglrun (e.g. itk-snap, even the > instances started by other users) are effected (e.g. artefacts in the > rendering, > bg-color taken from the voreen canvas). > > Is that as expected or a bug in specific for voreen over virtualGL? ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ VirtualGL-Users mailing list VirtualGL-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-users
