Horde3D

While debugging a problem with my code I realized that the whole engine state is not shared across contexts: In the primary window backface culling is active, in the secondary it's disabled.

(this is not pyglet specific)

More infos


This means that a part of the initialization of the renderer has to be done per Context instead of once per application to get the state right. I'd suggest adding a function "Horde3D::initContext" which initializes the current context and is called automatically by "Horde3D::init" to initialize the initial context.

Affected code:
egRenderer.cpp, init: only "Init Opengl states"
egRendererBase.cpp, init
more?

I'm not sure in which way the EngineOptions are affected by this bug.

You are right, Horde currently expects to be run in a single context. Your proposition is a possibility to fix this, another option would be that you can call 'init' a second time and the function just (re)sets the states in that case.

That's an even better idea.

Did you already have a chance to try out if it is really enough to set the mentioned states in order to use a second context?

I've done no further tests.

I'm using a multi window setup with shared contexts and calling Horde3D::resize before drawing to a window. It just works, I even didn't see any problems until I realized that the culling is handled differently depending on the context.
When I do "Init OpenGL states" by hand after creating a new shared context culling works the same on all contexts.

So as long as the contexts are shared setting these states should fix the problem.

In the current SVN trunk, init now reinitializes the states if Horde3D has been initialized before.

I've just tested it and it works