Free Support Forum - aspose.com

Node.GetBoundingBox() wrong value

I’m getting inconsistent results with node.GetBoundingBox();

        [Test]
    public void BadBounds()
    {
        Scene inScene1 = new Scene();
        var c1 = inScene1.RootNode.CreateChildNode( "Cube4", new Box( ).ToMesh());
        c1.Transform.Translation =  new Vector3( -20, 0, 120  );

        Scene inScene2 = new Scene();
        var c2 = inScene2.RootNode.CreateChildNode( "Cube2", new Box( ).ToMesh());
        c2.Transform.Translation =  new Vector3( 80, 0, 120 );

        Scene inScene3 = new Scene();
        var c3 = inScene3.RootNode.CreateChildNode( "Cube3", new Box( ).ToMesh());
        c3.Transform.Translation = new Vector3( -20, 0, 20 );

        Scene inScene4 = new Scene();
        var c4 = inScene4.RootNode.CreateChildNode( "Cube4", new Box( ).ToMesh());
        c4.Transform.Translation =  new Vector3( 80, 0, 20 );
        
        var bounds1 = c1.GetBoundingBox();
        var bounds2 = c2.GetBoundingBox();
        var bounds3 = c3.GetBoundingBox();
        var bounds4 = c4.GetBoundingBox();

    }

image.png (18.3 KB)

As you can see in the above image, Cube3 has incorrect bounding box for an unknown reason. Documentation is also unclear which coordinate system the bounding box should be in.

Bounds1, 2 and 4 have what I expected, but bounds3 seems to be local?

@bortos,

Thanks for contacting support.

Can you please share desired result in form of sample along with comparison screenshot so that we may work on this issue to help you out.

AsposeBugs.zip (1.8 KB)

I’ve attached a small sln that reproduces the issue with unit tests

Could you also clarify and update whether node.GetBoundingBox() is supposed to be global values?

Thanks

@bortos

We are looking into this and will get back to you with feedback soon.

@bortos,

I have observed your comments and logged it as THREEDNET-670 in our issue tracking system. We will further look into details of the issue and keep you posted with the status of its correction. Please be patient and spare us little time.

We are sorry for the inconvenience.

The issues you have found earlier (filed as THREEDNET-670) have been fixed in this update.