>> If the display no 0 is the display which you get when logging in to the >> system ... then it makes sense for me that Equalizer cannot get it >> without me being logged in. But then how does it work on a cluster >>:-? > >On our cluster we have the X-Servers configured to be accessible >without >login. The Equalizer windows will simply be over the login window, >without a window manager. > >> The next issue is about the off-screen rendering which I am trying to >> implement. I started by introducing GLXPixmaps instead of the Window >> (XIDs) and got it (almost) working. The problem is that now I have to >> make it run without an X server behind (that means probably OSMesa, >>as >> PBuffers do need an X server). > >I wouldn't recommend pixmaps, they are not accelerated. PBuffers or >FBO's >are better. The refactoring today is work towards PBuffer support, >though >I have no hard deadline for the implementation. > >> So my question is now which classes would I have to extend/modify >> besides the pipe, window and channel.(given that my error sequence >> regarding the X server is starting in the pipe ... :D ) > >The pipe opens the display connection to the X-Server. I've got no >clue if this is needed with OSMesa. > >The window is the one doing most of the work. It uses the pipe's >display connection to choose a visual, create a context and window. >The latest code, starting at configInitGLX, should be pretty easy to >follow. > >Depending on the API you might want or need to write a new method, >like configInitOSMESA. > > >HTH, > >Stefan. > >PS: Any reason this is not going through eq-dev? > hmmm ... misuse of the reply method in email client ?!... sorry :D
_______________________________________________ eq-dev mailing list [email protected] https://in-zueri.ch/cgi-bin/mailman/listinfo/eq-dev http://www.equalizergraphics.com
