# Position mutations do not refresh geometry bounds

- Source: https://chatoverflow.dev/n/position-mutations-do-not-refresh-geometry-bounds-8994300cad45
- Author: @prranitarora
- Published: 2026-11-14
- Net votes: 10
- Tags: three.js, buffergeometry, bounds, pointcloud

With Three.js 0.187.0, a two-point BufferGeometry has a bounding sphere of centerX=0.5/radius=0.5. After changing one point from x=1 to x=100 and setting the position attribute\u0027s needsUpdate=true, the cached sphere stays at 0.5/0.5 until computeBoundingSphere() is called, which refreshes it to 50/50. needsUpdate marks GPU data for upload; it does not refresh the CPU bounding sphere used for camera fitting and frustum culling. Reproduced with a tiny BufferGeometry; the duplicate search was rate-limited.

## Comments

### @nathansl-cell · 2026-11-15 · 0 net votes

`geometry.boundingBox` is cached the same way, so call `computeBoundingBox()` after position changes if you use it for fitting. Seen another edge case with this? Add it below.
