We are using getBoundingBox on the node to implement collision detection with nodes that have dimensions added to them. When we add dimensions to the node with an offset, the getBoundingBox is returning a box that includes the dimensions with the offset value and therefore is much larger than the node. I could see that you might want to know the bounding box with dimensions, but it would be helpful is there was a way to get the box without them.
Example for a window from my testing:
- Bounding box with no dimensions has a width of 0.5 and height of 1.0
- Bounding box with Width dimension offset by 0.25 (x direction) and Height offset by 0.1 (y direction) results in a bounding box with a width of 1.0 and height of 1.2
We are doing a workaround by having a top level node in the model we create with all the geometry underneath it and then putting dimensions at the same level as it. We can then transform that node (Window1.shed-window.Window) in this example assuming Window1 was the name for the node added:
But we really want to transform the whole model using Window1 as the name because doing this transform of a sub-node results in more complexity for our users (without going in to detail as to why).
Is there any way to get the bounding box without including the dimensions in your APIs? I was unable to find anything. I view dimensions as just an annotation and not part of the node for calcs.