views have default cameras and scenes, but all of these can be reset to whatever you want - views can share the same cameras, and the same scenes if necessary. so if you want to go the multiple view route, you can! but i'm not sure why you wouldn't just use containers with rendersessions... less views is definitely a good thing from an optmisation point of view
Rob On Wed, Feb 18, 2009 at 11:55 PM, buganamo <[email protected]> wrote: > > One technique I've used lately is having a base scene3D that is for > all of the floor graphics, a main scene that is for all the main > characters / objs, and then another scene that's for all of the > shadows / floor decals / etc. Then they each have their own > respective View3D's, stacked, base, decal, then main, and registered > accordingly on the stage. Then the EXACT SAME camera3D seems to > function fine when added to multiple scenes. It's also nice, because > you get really clean layering of floor decals / details without the > flickering of the floor or main objects. > > I've noticed that the 2.3 release of Away kinda makes this difficult, > since now the View3D makes its own Scene3D and Camera3D internally. > But if they can be seperated, then this solution actually works quite > well, and there is no need to call send to back / front. It also > allows you to put effects on the entire view, which may circumvent the > necessity of using ownCanvas. > > Just another idea! :) -- Rob Bateman Flash Development & Consultancy [email protected] www.infiniteturtles.co.uk www.away3d.com
