Hi Alistair,
Thanks for your details answer. I will try option 3. Thanks.
Regards,
Clement
________________________________________
From: osg-users [[email protected]] on behalf of
Alistair Baxter [[email protected]]
Sent: Wednesday, 4 March 2015 21:50
To: OpenSceneGraph Users
Subject: Re: [osg-users] Remote Deskstop Display issue
Your remote display problem is a limitation of Windows Remote Desktop's OpenGL
support. There are three potential solutions:
1) Only use OpenGL 1.1 features if you're using remote desktop - not very
practical possibly not even possible with OpenSceneGraph.
2) Use ANGLE and OpenGL ES - Angle is a wrapper for Direct3D that exposes the
OpenGL ES 2.0 and 3.0 API. Direct3D works across RDP, but only from windows 7
SP1, or the equivalent server version via a technology called RemoteFX. This
also will require rebuilding OpenSceneGraph, and writing your own replacement
for GraphicsWindowWin32 using GraphicsWindoEmbedded and EGL (or QT 5). Also
you'll be restricted to OpenGL Es's feature-set.
3) Use Mesa. If you can get builds of OPENGL32.DLL and GLU32.DLL for Mesa, you
can just drop them into your executable directory, and your app will support
desktop OpenGL 2.1 using software rendering. You'll need to remove those two
dlls to return to using proper desktop OpenGL. Obviously that's awkward, and
Mesa is slow and restricted in features compared to full, modern desktop OpenGL
(although conveniently it's a similar feature set to compatibility mode on OSX).
Internally, we use option 2 and option 3 on different products.
Your only other alternative is to use a different remote desktop protocol
product, like VNC or something commercial.
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
