Hi Maximilian, Away3D 4.0 is built from the ground up around the Molehill APIs. To port the exact same API to Flash Player 10 and maintain it would mean a huge amount of work that is not really justified seeing as how there are already the 3.x versions of Away3D for Flash Player 10. So there are currently no plans to support anything other than Molehill-enabled versions of Flash Player (presumingly "Flash Player 11" and onward.)
The differences between Molehill and the methods to do 3D in Flash Player 10 are absolutely enormous, both in features, performance and how it works. So my guess is that if you want to maintain versions of your game for both Molehill and Flash Player 10, you're probably best off keeping two separate branches of your code, and not try to use the same code for both versions. I guess what you could do is try to separate game logic into a shared library and then build two different versions of the game for Away3D 3.6 and 4.0 respectively, both interfacing with the shared game library. There are several API differences in Away3D 4.0 compared to 3.6, but I would estimate that around 1/3 are just spelling changes, while 1/3 are new features, and 1/3 are paradigm changes as a result of the new platform. Cheers /R On Mar 11, 7:47 pm, Maximilian <[email protected]> wrote: > Hi, > > I need to start working on a Flash 3D game soon, that should take > advantage of Flash Player 11 hardware acceleration, but should also > work with Flash Player 10.2 (low poly-models and textures will be used > for FP 10). > > I do not have any experience in 3D with Flash so far, so here are my > questions: > 1) Do you have plans to add some "backward compatibility" in Away3D > 4.0 so it can run in FP 10? > 2) If not, how different will the Away3D 4.0 API and the 3.x API be? > How hard would it be to have two builds of the application, one for > FP10 and one for FP11? > > Thanks, > Max
