In general three.js is immensely useful and well designed. There is one design decision that makes no sense to me: Geometry does not derive from Object3D. Why? Some context: I often have the need to manipulate geometry before I insert it into a mesh. But all the properties I would expect to be part…

In a scene graph library you usually have a class for modelling the 3D hierarchy. Sometimes it’s called Node, Entity, Component or Object3D in the case of three.js. Such 3D objects have a position, rotation and scale component and also derive their transformation to their descendants. Materials and…

I get that. It just makes it awkward If I simply want to position and orient a box or cylinder independent of it its parent mesh.

For context see my question - which I solved here: [image] How do I align a cylinder along an axis? Questions I am trying to position and orient a set of cylinders. As input I have a list of xyz locations. Each cylinder is positioned and oriented from successive pairs of x…

Geometry does not derive from Object3D. Why?

Questions

dugla October 18, 2021, 2:08pm 4

For context see my question - which I solved here:

Topic		Replies	Views
We should be able to draw with Geometry only --- without object3d Discussion geometry , object3d	11	1402	December 31, 2017
Why is everything BufferGeometry? Questions geometry	1	1297	March 5, 2021
Difference between Mesh and Object 3D? Questions object3d	2	6599	October 1, 2020
Why THREE.Geometry() not working? Questions geometry , 2d , primitive	4	647	April 24, 2023
Is ThreeJS object hierarchy documented anywhere? Questions geometry	6	2051	June 17, 2019

Geometry does not derive from Object3D. Why?

Related topics