@sgold, @pspeed does this make sense to you?
shouldn’t it return FrustumIntersect.Outside
if bound is null?
@sgold, @pspeed does this make sense to you?
shouldn’t it return FrustumIntersect.Outside
if bound is null?
I believe a null
bound indicates an empty volume, so it should return Outside
.
Thanks for the response.
Do you think fixing it would be a breaking change for v3.3?
At this point, I think it’s a moot question: there aren’t any more 3.3.x releases planned.
JME is inconsistent on this point and it seems very few places in the code were hardened for this idea. In at least a few cases, we’ve swung the other way of “always return some bound”.
For example, see: Node returns null bounding volume. · Issue #954 · jMonkeyEngine/jmonkeyengine · GitHub
It may be that the “right solution” is to have a NullBound that never intersects anything and can have a constant instance that these cases return instead of null.