General - Manually Set and Keep Model Bounds

[shaddatic]

Although this will effect a small few, having model bounds always automatically generated will lead to issues that are currently unfixable with SAIO alone. The SAIO bounds calculator has no context on how the model will be used in-game, or even context on the rest of the object tree in the case the Clip Children eval flag (although the latter can be addressed).

For example: if a modder imports/creates a model that, in-game, is supposed to scale up to a larger size -- perhaps an explosion or a flashing light effect -- SAIO will create a radius that is too small and the model will end up clipped too early when scaled up. And, sadly, there's nothing that can be done about this because only the modder knows how it will be used in-game. This could also affect Events too; although I don't have any examples and rarely are things hovering off the side of the screen.

The current solution is to import into SAMDL and adjust/restore the bounds manually there after exporting from SAIO. Having to rely on a second program is undesirable though. Including a way to set and keep model bounds manually in SAIO would fix this issue and allow the creator to be in full control of their model and its parameters, especially if a visual reference can be added/used.

However, I see a potential issue when importing models; there's no real way of detecting if bounds were set automatically or manually. A solution to this would be to make calculating model bounds opt-in, rather than opt-out. Perhaps have imported models keep their bounds by default, while newly created objects automatically calculate them; perhaps this can be a toggleable flag in the SAIO Mesh Properties.

Or, stop calculating bounds on export and make it a tool used during the modeling process; similar to SALVL's Calculate Bounds option. The user can select the objects and click a Calculate Model Bounds tool option, which will replace the current bounds option with what SAIO believes is the best fit. This however means the user will have to do extra work, but it may end up being less confusing than having the export behavior change.

This would also fix issues with No Model Bounds flag importing as the given bounds will always be kept, avoiding the need to detect it.