[Bobboau]

does anyone have a problem model? I think I'll be able to work on this today

[chief1983]

I've sent most of mine to Kazan, I can forward it to you if you want.

[Bobboau]

that would be nice.
be sure to tell me what's wrong with them.

[TrashMan]

Alas, is there any news for the colission detection bug?

I so wanted to get the new Galaxy out before christmas that I converted it in PCS1.. all looked well. Then I Re-edited all POF data in PCS2 and the colision problem returned.

[DarkShadow-]

I once mentioned my problem with copying/adding turrets in PCS2, well, I tried the actual release candidate and, guess what:

Oh my GOD it's so HORABLE!!!
*ERROR*:Array out of bounds!
That's BAD!
(well, at least the error message is funny ^^)

This happens whenever I copy a turret-subobject, no matter what I do with the copy (renaming, relocating, doing nothing...). Well, there're some models that work, it's just random if they work or not. Whatever, here's a list of models that work and don't work, perhaps it's useful to know this when tracking down the bug.


Working:
GTD Boreas from Inferno R1
GTBC Blade by Trashman

Not Working:
GTCar Fury by Trashman
GTCa Galaxy v.1/2 by Trashman
Cobra Class Frigate by Trashman
GTD Sirona by c914
GTFg Retribution by Trashman
Blade v2 by Trashman
NTCv Echelon by Trashman
GTCv Reyena by c914

[Kazan]

thanks for the bug report.. please put it in mantis

i promise i'll make an effort to drag myself away from vanguard: saga of heroes and work on PCS2.... but we have 50% XP bonus until jan 3rd so i'm working on my crafters

yes.. yes. i sold my soul to MMOs.

[Scooby_Doo]

Sweet... I just realized you can add/delete subsystems now. 



...and you can move them between levels.

[chief1983]

yes.. yes. i sold my soul to MMOs.

Frak.  We'll never get PCS2.

[Kazan]

nah.. you will - i must make myself code more for FS2 in the next year because i need to learn Taylor-fu and other gaming greatness as i should be graduating next december

[chief1983]

* chief1983 imagines a monkey walking across the stage, pausing, turning to the audience and going, "I know Taylor-Fu".

[TrashMan]

*slams head against the table...again...and again*

Damn...collions..detection...damn...go-trough...faces!

[Kazan]

Ok.. so i'm looking through the code trying to find the cause of why the bounding boxes are switched..... needless to say it couldn't have been something easy like me swapping min/max on an asignment in conversion *Sigh*

[Kazan]

New build posted - any model with fux0red bounding boxes will need to be reconverted from COB - the bad bbox problem should not come back

[chief1983]

You're my hero Kaz. 

[Goober5000]

Cool. What was the problem?

[Kazan]

Cool. What was the problem?

could not reproduce - but i had some stuff from trashman that let me compare models from old builds vs new and it seems that the older builds had a missing coordinate space conversion somewhere

[Col. Fishguts]

So, does this only fix problems introduced by older PCS2 builds, or can we use this new build to fix POFs with faulty collision detection produced by the 3DS Max exporter ?

[Kazan]

you have to recompile the old ones

and PCS2 has always recompiled the 3DS max exporter's models.. it doesn't recognize that exporter as "valid" (ie it won't cache BSP from it)

[Col. Fishguts]

By recompiling you mean via COB in TS ?

Using COB means no smooth groups, which is the main reason I use the 3DS max exporter.

[Kazan]

no.. when PCS2 opens a POF it decompiles the BSP into PCS2's internal format, PMF.

While it's opening the POF it checks to see if it recognizes the compiler that generated the POF as valid (last version of PCS1, latest PCS2 compiler, or [V]'s compiler) if it recognizes the compiler it "caches" the BSP data, otherwise it discards it and recompiles the BSP on save.