In terms of performance, how much of an impact is total elements? I know, its hard to quantify or even ballpark. If I remember correctly, about 10,000 elements is considered the feasible max for away3d, but is that rendered elements or total elements? If it is rendered elements, is there such a max for total elements?
I ask this because I'm struggling with some transitions between scenes on my away3d app using greensock timelines, as well as having lots and lots of fun trying to track down and release memory. My thinking was that if total elements wasn't really a concern, I would just create all my objects right at the beginning (rather than when they are needed) and just use visibility to make them appear and disappear, not remove/addChild(). This seems like it would by nature make memory management easier. It would use more up front, but I would get less surprises in terms of memory being chewed up as the application continues to run. Thoughts?
