Hello dp, i'm using PureMVC. I'm doing the same things like you do, but i don't have any problem with the performance. I put all the data in Model parts, and I put all the view components in View parts.
Usually, the performance will decrease because of too many polygons in one screen that need to be rendered. But... I also find out that, when I use Chrome and set camera lens to PerspectiveLens, I will get 2 fps. But when i'm using Firefox or Flash Player in desktop, I will get 22 fps, approximately to render 2000 polygons. So... I just set my camera lens to the other lens in Away3D, and everything works good. :D On Sep 5, 2:46 pm, dp <[email protected]> wrote: > I'm trying to improve my coding skills by implementing an MVC pattern > for a simple 3D app I have made. I have the basics working, but have > noticed a major performance decrease. > > Currently I have the controller handling the user input and computing > all the camera parameters, then updates these values in the model, > which notifys the view, which in turn requests the new data and > renders the scene. > > am i going about this the wrong way? should all of this be kept in the > view for performance reasons? any general pointers greatly > appreciated. thanks.
