Hi Pete - I'm not sure how to answer your question. I spent the last few weeks developing a testbed to see how well aw3d handles a lot of models and polys in a scene: (http://www.vicware.com/flyover/FlyOver03.html)
I was pleased to see that aw3d handled what I wanted to do, although now I see aw3d (or maybe I should say flash) is not geared for creating relatively dense scenes like this. I learned a lot, and now would do things very differently. Why wouldn't I want to progress to new versions, to take advantage of improvements and expansions of the aw3d lib? If I had a finished project, then of course I would leave that alone. But I just started with this, and already there's a major change that I'm glad I hadn't gone further with - i.e. textField3d. I really liked textField3d - it was simple and easy way to put 2d textfields into aw3d 3d space - no fuss, no muss (but with a bad clipping problem - you can see it in my demo). Very useful to my project. But a few days ago Fabrice cryptically said to "stop using it." There was no explanation if textField3d was going to be replaced, or if there's another way to accomplish the same task. I think it would be unfortunate if there was no quick way of putting 2d text into the 3d environment. I saw that post about "Big changes ahead," and I don't want to get stuck with obsolete code while producing new apps. I assume (a word I'm not crazy about) that the upcoming major revisions will include new services, less bugs and maybe faster results. i.e. If I upgrade to PS CS5 (or whatever), why would I possibly continue to do stuff with CS4? So, I evidently happen to come on board in the middle of big changes and developments of aw3d. I want to see where this is going. Thanks - Vic -- To unsubscribe, reply using "remove me" as the subject.
