Fabien, if you want someone do do a custom implementation of that sort of
thing, we can be hired to do so. ;)
On Mon, Nov 21, 2016 at 7:27 AM, Riccardo Corsi
wrote:
> Hi Fabien,
>
> in your situation the approach suggested by Chris is certainly the most
> promising.
> Create a second GL context
Hi Fabien,
in your situation the approach suggested by Chris is certainly the most
promising.
Create a second GL context (shared), render everything you need to with osg
in the second context to an FBO target and have Qt retrieve the fbo's
texture content, to display it in one of its widgets/primi
On 21 November 2016 at 09:12, Fabien Boco wrote:
> This is why I'm looking for an OpenGL ES alternative for glPush/PopAttrib
> which works fine on the Windows version application.
The alternative to using glPush/glPop on the OSG would be to dirty the
associated modes and attributes that are tra
I'm actually facing the second situation.
I'm trying to render some OSG with QML. Qt provide a "scope" where you can do
your custom stuff (OSG here). If you know Qt : you have to connect a slot where
you can do your custom OpenGL to a specific signal.
I already tried to play with contexts (as
Are you trying to render combined 3D scenes, or have OSG render a texture
that will be used on a surface within your other renderer's scene?
When we were faced with the second situation, what we did was to create a
whole new context (shared) for OSG let OSG render into a texture with that,
and the
Hi,
I'm trying to use OSG with an existing renderer. I found the FAQ about it which
advises us to use glPush/PopAttrib to make it work
(.../faq#CanIuseOSGwithinanexistingrenderer)
But here's my problem : I'm moving an OSG app (running with QML) from Windows
to iOS and iOS means OpenGL ES which
6 matches
Mail list logo
