BoundingBox in GameObjectDisplayInfo, what is it for ?

[Magnus]

Hi

When I add some new display models in GameObjectDisplayInfo.dbc I always copy the bounding box vectors from an existing record.

The models seems to work for me, regardless of the values of this bounding box.

My question:
What is this bounding box for and how does it affect the game ? And if it is important, how do I have to calculate it ?

[schlumpf]

probably culling. just take the values from the models themselves.

[Magnus]

Ok, if it´s f.ex. for frustum culling, it's also maybe not so critical.

But from where I would get these values? I select a model in Noggit, see the path and modelname and make an new id in GameObjectDisplayInfo.

[Amaroth]

As far as I know when you leave 0s there model's base hardcoded values will be used.

[schlumpf]

M2: http://wowdev.wiki/index.php?title=M2/WotLK, VertexBox in header.
WMO: http://wowdev.wiki/index.php?tit ... MOHD_chunk bounding_box in MOHD

[Magnus]

Just wanted to update the info:

The BoundingBox values seems indeed not to be important.  

But if you change on a Trinity Core the type from 13 (Map Object) to 33 (Destructible Building) buildings appears very smooth. There is near no difference between client objects and server side objects.

Didn't tested the effect on other objects like trees.

[Amaroth]

By smooth appearing you mean that they don't just instantly "flash" out on your screen? I use client side spawn for every bigger model, but still quite good to know, especially for some other guys.

[Magnus]

That was what I meant. It doesn't pop up.