[Droid803]

This is getting seriously annoying.
Whoever made it so that you could manually edit the radius of subobjects messed up bigtime because it keeps setting values to 0 or some really tiny number like 0.00000171, or sometimes even negative values (what the **** is a negative radius D:).
Which causes (predictably) a whole ton of trouble, including SUPER LAG, madly-spinning debris, etc. Not to mention a whole slew of collision errors.

Easily fixed by going through and hitting reset on every afflicted subobject, but usually, that means every single subobject.
NOT COOL.

[Droid803]

*poke* anyone here?
As seen here clearly I am not the only one experiencing this issue.

[Droid803]

Bumping because this is ****ing annoying and adds like 10 minutes to every conversion cycle.
Which is seriously putting me off doing it.

Would it ****ing kill someone to even respond?

This happens during DAE->POF saving process. The DAE has the correct radii but the pof does not. Fixing it on the pof (pof->pof) is fine.
Purging BSP cache does not help in any phase.

The longer this error persists the bigger chance there is of having an era of ****ed up models because people aren't thorough enough to reset the radius of EVERY GODDAMN SUBOBJECT...

[Talon 1024]

I think it would help if you provided a sample DAE that causes this problem so that Spicious or someone else can reproduce this issue.

BTW I'm using the April 1st build of PCS2, and I haven't had to reset the radius of every subobject in models I've converted...  Although I haven't made any models with LODs or Debris recently.

[Droid803]

Every DAE causes this problem.
At least, every one with Debris.

[zookeeper]

Well, I can respond but can't really help.

Yes, it's a bug and a very annoying one, so hopefully someone will fix it soon. Unfortunately Spicious doesn't seem to be around much these days.

[Spicious]

Yay, 2 character fix.

[attachment removed and sold on the black market]