mantra "out of bounds" error clarity

[Guest xionmark]

Greetings,

When getting the "out of bounds" error from mantra, e.g.:

mantra: /obj/geo_cluster: Procedural generated out of bounds geometry
xmin -0.901058 -0.873573
ymin -5.4849 -5.44343
zmin 15.4209 15.4214
xmax 1.64481 1.62438
ymax 1.30675 1.2853
zmax 23.0744 23.0107

I'm confused with mantra requesting the bbox after initializing the mantra procedural (via the initialize() method) but *before* the render() method. One would have to generate all the geo at init time to properly calculate the bbox ... which seems backwards. I know the renderer has to test the bbox to know when to trigger a procedural's execution but shouldn't there be a way to inform the renderer of the true bbox once it's been properly calculated in the render() method?

Perhaps the proper workflow is to generate all geo at init time? Seems like an elementary issue yet there's no example I've found in the HDK that solves this.

So for now one has to estimate some sort of fudge factor in calculating the bbox? I really don't like that idea.

--Mark

Edited December 5, 2012 by xionmark

[Guest xionmark]

No takers?

I guess I should submit this as a BUG/RFE.

--Mark