Jump to content

Slow FPS remains even after prim.dispose()


Recommended Posts



Just to report that on the example given in the documentation:  http://www.babylonjs-playground.com/#OWCCR#8 

Increasing the number of primitive slows down the fps, but when reducing that number fps stays low even after dispose(). 


I don't know it if was reported before, and I did not remember this behavior last time I checked this example... @Nockawa

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.

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.


  • Recently Browsing   0 members

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