Jump to content

PhilT
 Share

Recommended Posts

@PhilT welcome to the forum from me. The Gamelets are starting points for ideas using Babylon.js and as such were written as explorations and are about potential rather than efficiency and effectiveness. As Jerome said the PG is CPU intensive and time is of the order(N*N) where N is the number of balls, so for time of order 4 000 000 perhaps 10fps is not too bad for a start.

Link to comment
Share on other sites

In my old Athlon x2 with the GTX 650, it runs at 4fps (with 2000 particles, which are a lot :)). With less than 200 particles I can get 60fps, and with 400, 30fps.

 

But as you have already been told, the trigonometric calculations of the intersections consume a lot of CPU time. It seems totally normal to me.

Link to comment
Share on other sites

Thanks for the welcome, John :)

And thanks very much for the responses. Yeah, those are some big numbers! Good to know others are seeing similar performance. I'm still experimenting with BJS and trying to get a sense of what could be achieved and what the limits are. 

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...