Jump to content

Energy.js playground


Samuel Girardin
 Share

Recommended Posts

Yeah, I noticed it jumping back up to 60FPS when things settle down but I didn't always see this. I guess that means we can leave the impostors hanging around rather than trying to optimise them away at least until the scene gets really crazy!

I've been talking about this over at 

if you want to continue the conversation there. Maybe leave this to Energy.js specific stuff.

Link to comment
Share on other sites

@PhilT http://www.babylonjs-playground.com/#URPXQB#4 . It's quite better here.  Physics engine  have their own specifications, it's quite hard to compare them even with raw perfs. Could you share your code, It will be interesting for me to see what value you used with the engines. 

Link to comment
Share on other sites

@PhilT, Ok I see your file, main problem with physic engine is there are a hundred ways to do the same thing. Look at this one : http://www.babylonjs-playground.com/#URPXQB#12

Fps is better and at the end we have a solid 60 fps, because idle boxes are out of the simulation. They are not totally out, if a new collision occurs, they will be in again in the simulation. 

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...