Page MenuHomeFeedback Tracker

A scripting bounds command that only takes actual geometry into account
Acknowledged, WishlistPublic

Description

I maybe wrong but the current bounds commands (boundingBox and boundingBoxReal) come in rather large and look like they incorporate all vertices including things like memoryPoints for getIn position and the like.

Would it be possible to supply a bounds command that would only query vertices from a specified LoD like Geometry, so we can get bounds that are more relevant to the area actually occupied by the the visual model?

Currently doing boundingBoxReal on something like a "O_Truck_02_transport_F" produces a bound area that extends >4m front and back of the vehicle and about 2m above and below. I realise the front and below expansion is due to the largest offset from [0,0,0] but with their current returned values these commands have wasted potential for use as object placement mechanics.

Details

Legacy ID
3949364907
Severity
None
Resolution
Open
Reproducibility
N/A
Category
Feature Request

Event Timeline

Larrow set Category to Feature Request.Oct 4 2015, 2:49 PM
Larrow set Reproducibility to N/A.
Larrow set Severity to None.
Larrow set Resolution to Open.
Larrow set Legacy ID to 3949364907.May 8 2016, 12:53 PM
R3vo added a subscriber: R3vo.May 8 2016, 12:53 PM
R3vo added a comment.Oct 4 2015, 3:05 PM

It's great that they added the bounding boxes to the editor, but I started to notice that these boxes are also, like the old icons, useless, since in most cases they do not represent the correct size of the objects.