Custom Bounding Box not working

[tycho911]

Hi, I’m using a custom vertex shader on an object that deforms the vertices a bit, so I need to expand the bounding box for proper frustum culling. I thought I could just do it script like
renderer.bounds.Expand() … but this doesn’t seem to have any effect…what’s the proper way to change the bounding box for an object? thanks…

[Kurt-Dekker]

Using the renderer.bounds property is frequently confusing and/or surprising:

How to retrieve bounding box of all active objects in scene

Just for the record, before anyone goes too far down the Bounds rathole, I have personally observed dozens of people come in here posting about how the renderer.bounds property disappoints them in some way. While it is an exposed API and is supported, it appears from the many posts that renderer.bounds frequently surprises users who attempt to employ it for their own purposes. Now the actual concept of an AABB Bounds object is solid, that’s just data, just a struct, so of course that’s fine, i…

I’m not sure what the right way is vis-a-vis vertex deformation, but perhaps putting some degenerate zero-surface-area triangles a little ways outside of your object’s natural bounds could help you increase the effective area? You might need to turn off mesh optimization on import, depending on if mesh optimization removes zero-area triangles…

[tycho911]

Thanks. What I am doing in specific is using a shader to make sprite objects face the camera rather to doing it in script, so there is no geometry to access per se. It should be a straightforward thing to enlarge the bounding box… this is weird

[Bunny83]

You should not mess with renderer.bounds as doing so will disable any auto update of the bounding box since this is a worldspace bounding box. So moving the object would have no effect on the bounds. You usually want to change the localBounds if the Renderer or the Mesh (in case of a MeshRenderer).