[Galemp]

Exporting what? It shouldn't be doing that. Post the offending POF.

[Scooby_Doo]

I was just trying to figure out how turrets work... but is this how their suppose to be laid out?

PCS2 completely crashes when trying to import that, right about when it says loading textures.  If I remove the helpers node, it complains that it can't find the geometry for the firepoints.
If I detach the turret01 object itself and rename it to detail0 and export it, it compiles correctly, so the mesh should be ok.

[Spicious]

That looks correct.

[DaBrain]

Wait... the "helpers" node is either new, or that's what crashing PCS2.

Never used or needed it so far. My firepoints are all directly connected to detail0.

[Spicious]

They've been around for a while now.

Never used or needed it so far. My firepoints are all directly connected to detail0.

Have they worked and when did you last update?

[Scooby_Doo]

Wait... the "helpers" node is either new, or that's what crashing PCS2.

Never used or needed it so far. My firepoints are all directly connected to detail0.

Could you please send me a sample model containing a turret please?

[Scooby_Doo]

Actually this problem occurs not with just this turret mesh, but any old test turret causes it to crash. 

[DaBrain]

They've been around for a while now.

Never used or needed it so far. My firepoints are all directly connected to detail0.

Have they worked and when did you last update?

I didn't try it yet. I'll do so and report what happened.


Edit:
I just imported a DAE from PCS2 in MAX.
It creates helper nodes for every mesh with a property now, which is useless, since the info is stored in the custom properties of the mesh.


Edit2: Ok, I get "Instance geometry not found for firepoint(*some number*)"
Then PCS2 crashes.

[Vasudan Admiral]

Buggy bombardment I'm afraid - the axis mirroring checkbox seems to invert all face normals all over the model.

[Scooby_Doo]

They've been around for a while now.

Never used or needed it so far. My firepoints are all directly connected to detail0.

Have they worked and when did you last update?

I didn't try it yet. I'll do so and report what happened.


Edit:
I just imported a DAE from PCS2 in MAX.
It creates helper nodes for every mesh with a property now, which is useless, since the info is stored in the custom properties of the mesh.


Edit2: Ok, I get "Instance geometry not found for firepoint(*some number*)"
Then PCS2 crashes.

Yup thats what's happening here.  Does it crash about the time "Load Textures" occurs?

[DaBrain]

No, I don't get an error message, just a crash.

[Scooby_Doo]

No, I don't get an error message, just a crash.

Same here...
Starting Load....
Loading Textures...
CRASH

[Spicious]

Buggy bombardment I'm afraid - the axis mirroring checkbox seems to invert all face normals all over the model.

You're meant to use an even number of them at a time.

[Vasudan Admiral]

lol, ah righto then. Makes sense when you think about it.

[Scooby_Doo]

Ya, the latest build works!  Although I still have to have the model rotated 180 degrees front/back, the turret issue is gone.

Edit: Opps i see the axis flipping now. 

Double Edit: Question, how are turret fire point rotation origins handled?  I hope your not assuming the turret barrels are in the center of the base.

[Scooby_Doo]

Ok another problem...

I create a simple box, apply textures to it, reset the x-form, collapse and attach this as a subobject to the main hull. Tell pcs that it's a subsystem.  Load the model in the game, no collision detection occurs, you can fly right through it.

Edit: more test, similar result.  Last one I could hit part of the box, but the rest would pass through.

[DaBrain]

Short sidenote about X-Form Reset:

Any rotation or scaling applied to the obect (not the polygons!) will be reset to 0° or 100%.

So you only need to use it, when you've edited the object. Changes within the editable poly do not require it.

Also, you can only it for meshes that are not withing a heirachy(!).

[Scooby_Doo]

Also if you move the object you need to reset, otherwise pcs2 will complain about unable to find mesh instance.

Edit: oh ya, and it's often wise to collapse the stack first, sometimes it messes things up bigtime and theres no undo.

Still have no clue why hit detection is wonky.


double Edit: Some more info, if I put the subsystem at (0,0,0), the center of the detail0 the hit detection works perfectly.  When I start moving the object away from the detail0 it starts becoming more and more problematic.  It looks like the subobjects isn't extending the main hitbox collision.   

[Vasudan Admiral]

AFAIK, the detail0 bounding box is not extended to encompass subobjects in POFs - and the collision detection is often skipped altogether when the centre of those subobjects is outside or nearly outside that bounding box. You can manually expand the bounding box by strategically placed teeny tiny triangles that have almost no area. (Map them to a black part of the main texture, or they may flare up in game once in a while).

This problem was causing the new Iceni's big turret subobjects to ghost, as they were above the bounding box.

[Spicious]

Are bounding boxes supposed to extend around child geometry?