[General Battuta]

Can we get it un-intentioned? 

[Droid803]

Yes, because its not stopping me from changing it anyway.
It's merely a minor inconvenience.

[Spicious]

And for all the people who are happy with an auto-calculated radius?

[General Battuta]

And for all the people who are happy with an auto-calculated radius?

Leave them with the ability to generate an autocalculated radius but add the option to enter one manually so we can stop fixing it with a hex editor?

[Zacam]

Have it do it's normal thing. But have an "unlock" button or something near it that you can click on to modify the values.

Have it pop up a "Are you f'ing kidding me?" window first if you like, so that it has to be a deliberate choice on the users behalf to do it,  or something.

[chief1983]

When you open up the same POF later, and resave it, how do you know what to use?  An autogen or the existing value?  You would probably have to override the setting every time  you resave the POF to ensure nothing silly happens.

[Zacam]

Uhm. It doesn't automagically recalc every single bloody time if there is a stored value, does it?

Because if there is no stored value, well, that's just crazy talk, because then what does the engine use? So it stores it. It should only ever calculate one in the absence of there ever being one (such as on an import from DAE). At which point, there is no conflict if there is already a stored value, and if manually enter a value in' that's the same thing because it's storing to the same location.

Or should be. Or something. Thanks, now my head hurts.

[chief1983]

Yes but can't PCS2 make changes that would necessitate a radius update?  I'm just not sure how that's currently handled even.

[zookeeper]

What the heck is this "radius"?

[Droid803]

Radius is the radius of the model.
It controls stuff like the following distance of external view.

Just make it like MOI.
It'll always keep the value there, but you can tell PCS2 to recalculate it.

[FreeSpaceFreak]

I'm not sure if that's a good idea... MMOI is something that's often forgotten; if the radius is forgotten, that will have even worse consequences.

On second thought... Maybe do make it like MMOI, but add a warning dialog on saving with a 0 value for either of them?

[Nuke]

not do derail the talk of radius but:

this:

http://www.hard-light.net/forums/index.php?topic=74665.0

[Zacam]

K. Radius. Have it still continue to do what it does. (Calculate one, that is) especially if it is importing a DAE. If it's already a POF, it should already have a stored value, yes? So it will load that.

But like MOI, you can either Recalculate it, or enter in your own values. Make sure it can not be accidentally done by having a lock/unlock button. See, even when you "Load" data from another model (like when you import from a Retail model) the Radius changes, but when you save it again, it goes back to the calculated one. But say you unlocked the Radius and then hit "Load", it should then replace that Radius with the imported or manually entered one when you hit "Save" (along with potentially a flag bit somewhere that registers it as a "Stored" rather than "Auto-Calculated" so that it won't attempt to auto-calculate it again if the bit is present). If you find you've made a mistake, re-open the POF (or PMF), unlock it, hit the recalculate button or even better, have a "Reset" button that clears the "Stored" bit and restores the "Auto Calculated" data by recalculating it.

Complicated? Perhaps. But not everybody knows where to go in the model with a Hex Editor to accomplish the same thing, and I'm pretty sure (Droid803 can confirm or not) that when set that way, it stays (as far as I know).

[Spicious]

The radius (and bounding boxes) are recalculated every time on export to POF and when performing transformations.

The problem with an override is it wouldn't persist between PCS2 sessions.

[Droid803]

If you go into the hex editor and set the radius, it stays that way, and you can see the set radius by opening it up in PCS2.
If you save it as POF again in PCS2, the hacked radius will be overwritten.

that's how it is right now.

[Zacam]

Why wouldn't it persist? Is there a way to set a bit-field or something where it can?

[chief1983]

There's nothing in the POF format currently to make it persist, as there's never been a need to override it manually.  This is what I was afraid of.  Still, even having a one time ability to override the saved radius could be useful, I think, even if it had to be redone every POF save.

[FreeSpaceFreak]

On opening a POF, check if the radius in the file corresponds (+/- 0.001m or so, avoid floating-point round-off issues)  to the actual radius of the model?
That way the program would know whether to use a custom radius or an auto-computed one.

[Spicious]

The radius calculation has changed.

[Zacam]

The radius calculation has changed.

Dōmo arigatō