Hi there guys, I got a few requests to implement initialization stuff into Genome2D engine so it can run on top of Away3D and can be used for UI etc.

For me to do this I need to either have access to the Away3D Stage3D/Context3D so I can bind to it or I can specify Away3D what Stage3D/Context3D is already initialized so it will not reinitialize it.

Personally I am for the 1st option user will be able to simply initialize Away3D get a Stage3D reference and push it into Genome2D so it can work on the same Stage3D.

Also there doesn’t seem to be any event telling me when Stage3D is initialized in Away3D. It would be really helpful to know, now its initialized behind the scenes once its added to stage but user doesn’t know and can’t respond to it. If I got an event from Away3D that its initialized and there is Stage3D used I can simply once again push it to Genome2D.

Another question is device loss, but that may be trick as only one of the frameworks should handle context reinitialization and the other should be just let known about it.

Thanks.

Ok i modified the Away3D source codes and got it running here:
http://blog.flash-core.com/?p=899

It was a little bit more tricky, on Away3D part I had to stop it from calling context.present and remove the shader bind optimization where Away3D asumed that its last saved shader was the last one used on GPU which isn’t true when there are 2 frameworks binding shaders to GPU at the same frame.

Anyway I would like to hear from the A3D guys what do they think about combining 3D and 2D frameworks together and if can get some workflow going on.

Nice work! It is likely that we implement something like this as well, although we will have to give a think about how to do it exactly.

I’ve created a feature request for it that you can keep track of here:
https://github.com/away3d/away3d-core-fp11/issues/236

Expect progress to be made once 4.0 is out of beta.