Geometry vs. BufferGeometry Best Practices for New Projects? (R68)

I read a lot of comments about BufferGeometry and Geometry. Most comments are from February 2014. But I do not know if they are all true.

As far as I understand the comments, BufferGeometry should be faster, less hungry, and less user friendly.

I conducted several tests with a project that I am working on, and I could not confirm these claims. I used ThreeJS r68. I created 9 objects each with 12,000 faces. I tested speed and memory usage with: Geometry, BufferGeometry and BufferGeometry (dynamic = true). Memory usage has always been ~ 650 MB. The speed was always ~ 90 FPS. (or ~ 340FPS on another computer) I could only confirm that it is less friendly;)

With iOS8 (releasing tomorrow?) And the goal of getting my application to work on tablets, my question is:

Should I use geometry or buffer geometry? Or ThreeJS has been developing so fast since February 2014 that there is no difference, because in fact Geometry is just the front for BufferGeometry?

Regards Benedict

+6
source share
1 answer

If BufferGeometry meets your needs, use it. It will be faster and less hunger.

+1
source

Source: https://habr.com/ru/post/975033/


All Articles