Page MenuHomeFeedback Tracker

boundingBox and boundingBoxReal include Memory LOD
Assigned, WishlistPublic

Description

As the title says. It took me hours to find out why boundingBox and boundingBoxReal are returning waaaaay to large numbers. Then I have figured out: They handle vertices in the Memory LOD the same way as in other LODs. This is definitely unexpected behaviour and renders the bounding box function useless if you are in the need of (Memory) vertices outside the bounding box of a model. Once I remove the Memory LOD, boundingBoxReal returns useful values.

I suggest to skip the Memory LOD in the bounding box calculation.

Details

Legacy ID
2002845068
Severity
None
Resolution
Open
Reproducibility
Always
Category
Engine

Event Timeline

Eichi set Category to Engine.Mar 12 2015, 4:29 PM
Eichi set Reproducibility to Always.
Eichi set Severity to None.
Eichi set Resolution to Open.
Eichi set Legacy ID to 2002845068.May 8 2016, 11:39 AM
ruebe added a subscriber: ruebe.Feb 10 2018, 4:24 PM

Still not fixed, hu? (haven't been around in a while)
This one is really bad. I understand you can't just "fix" the existing commands, since that would likely fuck up way too many things that rely on these faulty bounding boxes. But a new command as suggested; how hard could it be to just implement this already?

Please? 8)

Also see:
https://feedback.bistudio.com/T83132
https://feedback.bistudio.com/T84418