Open hamza-hajji opened 6 months ago
My observation after looking at it for a while, is that after the rotation (e.g. changing position doesn't seem to have a problem) the size of aabb seems probably fine, but its the position of aabb which is wrong. I can't find out however why wrong aabb is actually calculated. SceneModelEntity during get aabb() do this += this.origin of the aabb, so maybe there is something with this origin. But it's difficult to spot how this origin is being calculated and when.
I tried to dig a little further, found out that for some reason in web-ifc example there is no such problem after rotation
Few additional observations:
Has this been fixed? #1379 seems to be closed.
@intrida-dev It has not been fixed. For distantly-placed models, I have not been able to make individual object rotations on objects work within xeokit's RTC tiles coordinate system. I'm not sure of a solution for that at this stage. Only translations currently work for all models.
@xeolabs Ok. We will try applying translations until this gets fixed. Thanks
Describe the bug Rotating a model makes its aabb wrong
To Reproduce Steps to reproduce the behavior:
viewer.scene.models.myModel.rotation = [0, 40, 0]
Expected behavior The aabb is still right after rotation
Screenshots
I made a script that draws a transparent cube given an aabb for testing:
It is correct initially before rotation
But after rotating:
Desktop (please complete the following information):