Login  Register

Re: Using a display connection name fails (through NewtFactory)

Posted by Sven Gothel on Jun 09, 2013; 5:58pm
URL: https://forum.jogamp.org/Using-a-display-connection-name-fails-through-NewtFactory-tp4029333p4029359.html

On 06/09/2013 07:17 PM, neothemachine [via jogamp] wrote:
> @Sven Just one more question for clarification: Is it definitely
> possible with JOGL 2 to use a custom display connection _without_ having
> a default device configured (in Linux through the DISPLAY environment
> variable)?
>

1st: One default DISPLAY [must|should] be given to allow
     the default-device query - which should not be empty!
     We could change code .. but this somewhats makes things complicated.

2nd: You are able to use other devices than the default
     (currently _only_ on X11).
     I tested w/ the named unit tests TestRemoteGLWindows01NEWT, TestRemoteWindow01NEWT
     a while ago w/ another remote NV GPU.
     I have to admit, AMD to NV didn't work w/ the GLX protocol.

3rd: I have not tested [xvfb + mesa-soft] yet.
     Can you elaborate on this configuration ?
     I.e. post the 'glxgears -info' on that remote connection
     to your xvfb.
     I will the go ahead and test it.

Have you already added a bug report ?
Please do so, if not done yet - and pls use a simple JOGL unit test,
like
  com.jogamp.opengl.test.junit.jogl.demos.es2.newt.TestGearsES2NEWT
  com.jogamp.newt.opengl.GLWindow

you can see/edit them in
  jogl/make> vi scripts/tests.sh

and start them:
  jogl/make> bash scripts/tests-x64.sh

given that you have build the beast, and java/ant env. vars configured.

~Sven



signature.asc (911 bytes) Download Attachment