Mika wrote: > I plan to target FP10, but I have a 3d designer doing the modelling work, so > i will need to import models. The app is part of a large project, and I want > it to be able to grow overtime. > A solid engine is hence required. > > The models will range from soccer balls, rugby ball, hand ball ... to > shirts, sockets and so on. But I'd like to be able to extend to any kind of > 3d model over time. > We might also model a full character to 'wear' the products.
Then Flash's rather weak built-in 3D capabilities won't work for you. They're good for primitives (spheres, cubes, and the like), but not complex models. You should probably look into Papervision--it's a much more capable 3D engine. Or, if you're not married to Flash, you should look into Unity or Director. Both offer much more powerful 3D engines. Unity is probably easier to user, and the company seems to have a stronger commitment to it than Adobe does to Shockwave, but the Shockwave player penetration is way, way higher than Unity's. And, despite rumors you may have heard, Director isn't dead. I hear rumors that a Director update is coming, and may be in alpha or beta testing. And, while you're exploring the engine, You might want to advise your 3D designers to go light on the polygons (I assume your models will be polygon-based, and not bones). The more polygons your model has, the more it will tax the system. I'd use enough to make it look good, but not go overboard. It doesn't sound like you're going to need things like lights or shaders, which also can stress the system, but you still need to keep the poly count low. Cordially, Kerry Thompson _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
