Why is the Geometry faster than BufferGeometry?

[hofk]

This post belongs rather to

THREE.Geometry will be removed from core with r125

The upcoming release r125 will contain a major, potentially breaking change. The class THREE.Geometry will be no longer part of the core but moved to jsm/deprecated/Geometry.js. It will only be available as an ES6 module and not as a global script. What does that mean for me? If you are loading your assets with one of the official loaders like GLTFLoader or procedurally generate geometry data with THREE.BufferGeometry, this change won’t affect you. If you are using THREE.Geometry, please note …

where from
THREE.Geometry will be removed from core with r125 - #26 by hofk
the solution of the imaginary problem can be found. See original post SOLUTION.

---

---

Yes , BufferGeometry is certainly more difficult for beginners.

Therefore my contribution: From the Collection of examples from discourse.threejs.org :

BeginnerExample

BufferGeometryIndexed
BufferGeometryNonIndexed
BufferGeometryNormals

BumblebeeMara and in the source code the link to the old Geometry version.