[pecenipicek]

spicious, was there something wonky with my dae exports since i cant get em to import into pcs2, since i always get the "detail0 not found" error?

[Spicious]

Your exporter seems to use its own system for labelling node ids. I've changed the importer so it will use node names to decide things for everything except transparent bits of subobjects. This should make 3ds users happier too.

[Vasudan Admiral]

Are bounding boxes supposed to extend around child geometry?

Not automatically, no - it's up to the modeller to ensure the main bounding box encompasses all the subobjects. Large bounding boxes without the geometry to back them up is kinda asking for trouble.

[pecenipicek]

kk, thanks spicious.

[Scooby_Doo]

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.

Ya, thanks VA, I spent a couple of days trying to figure this out.  Would never have realized it was the engines fault.

[Scooby_Doo]

How exactly are lod levels done? I've got detail00, detail01, detail02.  When I load the model into pcs detail01 appears to be the default one (i.e. no cockpit is showing up), only when I click on detail00 do i get it.  In game, only one lod is ever displayed.

Same with glowpoints, I've got glowbank01 and glowbank02.  Each have glowbank01-01.... children.

Also the -glow/-normal/-shine maps are loaded as part of the texture.  They don't need to be included.

[Spicious]

The lod naming scheme for some reason is detail0, detail1 etc.

For glowpoints it looks like they should be linked to subobjects.

Any texture names in the texture list are carried over when importing.

[Scooby_Doo]

The lod naming scheme for some reason is detail0, detail1 etc.

For glowpoints it looks like they should be linked to subobjects.

Any texture names in the texture list are carried over when importing.

Ohhhh 0, 1, 2.....
So the glowpoints should be childed to detail0?

The textures isn't an issue, just delete them in pcs 

[Water]

The lod naming scheme for some reason is detail0, detail1 etc.

Heh I get the impression that it picks a lod or debris and switches it at random.

[Spicious]

So the glowpoints should be childed to detail0?

Yes, attach the glowbanks to its helper child.

Heh I get the impression that it picks a lod or debris and switches it at random.

If lods and debris are ending up pointing to the wrong subobjects, let me know. The system for matching them up changed recently and probably hasn't been thoroughly tested.

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

I can probably fix this at some point.

[Water]

If lods and debris are ending up pointing to the wrong subobjects, let me know. The system for matching them up changed recently and probably hasn't been thoroughly tested.

PCS2 - Standard and collada
1 detail0
2 detail3
3 detail1
4 detail2

1 debris03
2 debris02
3 debris01
4 debris04

Edit: Sorry that was for cob. For collada only the debris is out of order, a non issue.

[DaBrain]

Is it alright that all objects have helpers attached to them?

It really blows up the hierarchy.

[Spicious]

Edit: Sorry that was for cob. For collada only the debris is out of order, a non issue.

Oh, that's sort of intentional. The ordering of quite a few things is undefined with the change to name based recognition. Notable exceptions that I can think of now are lods, gunbanks and eyepoints.

Is it alright that all objects have helpers attached to them?

It really blows up the hierarchy.

What?

[Scooby_Doo]

Also on the numbering, how is glowpoints done?

I've done glowbank01, glowbank02   and glowbank1, glowbank2 but it'll only read glowbank2.

[Spicious]

It should process any node with a name that starts with glowbank.

[Scooby_Doo]

Ok that helps, but is there a way to have glow groups?  (more than just one)

[Spicious]

Aren't glowbanks groups?

[Scooby_Doo]

You can have more than one group.  For example group A displays when group B is dark and alternating.

[Spicious]

Yes, I call them glowbanks. Glowbanks contain glowpoints. There shouldn't be any problems with multiple glowbanks.

[Scooby_Doo]

Yes, I call them glowbanks. Glowbanks contain glowpoints. There shouldn't be any problems with multiple glowbanks.

How should they be setup?

• detail0
  
  • helper
    
    • glowbank
      
      • glowbank01-01
      • glowbank01-02
      • glowbank02-01