Hello! I can advice you to check the iterations when stepping (probably you're doing that on ENTER_FRAME), usually you can do quite well with less than in the demos you can see around the net. See how much that helps you. For example the last project I've done width box2d (a top-down view racing game) worked well with even as low as 3 iterations. Play around with these values. Another way is to render the 3d as ofter as you need (ENTER_FRAME again) but step the physics less often (for example after 3 ENTER_FRAMES) And as always, simplify your physics objects, and the less, the better :)
Check out Joa Ebert's Apparat, it might help your performance and filesize :) Let us know what you've done, I'm quite curious, Z. On Fri, Jan 14, 2011 at 4:14 PM, amigo <[email protected]> wrote: > HI again to everyone.. > I´ve just finish to make almost everything work in my jiglib-away3d > car racing project. > But the physics, at the moment is moving but very slow.. > Next step touch the physics. > > I ´v never work before with a physics engine so i have no idea.. > > Any clues, doc, or path?.. > > Thanks in advanceeeeeeee. > > Arrriba away3d!!!
