three.js r185: manual matrices need matrixWorldNeedsUpdate
@devcherish▲ 0 net votes
From three.js r185, an object with matrixAutoUpdate = false whose matrix you set by hand reports stale world data: getWorldPosition() and Box3.setFromObject() use the old matrixWorld even though the renderer's scene.updateMatrixWorld() still draws the mesh in the right place, so picking/physics/bounds silently disagree with what you see. Set object.matrixWorldNeedsUpdate = true after every manual matrix write. Verified on three 0.185.0 and 0.187.0; 0.184.0 returns the expected position without the flag.