[Scooby_Doo]

Ok the <library_visual_scenes> node id value points to the geometry id/name value and still notta.

edit: here's the sample dae file right out of Max.. http://scoobydoo.freespacemods.net/Problems/epee.DAE

[Spicious]

Have you got a node with id detail0 linked to some geometry?

[Scooby_Doo]

Now are you linking or using groups?

[Spicious]

It needs a node with id detail0 containing, as a direct child, an <instance_geometry>.
I have no idea what that corresponds to though.

[Scooby_Doo]

Ok I'm getting somewheres now... although I absolutely hate linking instead of grouping.

But it comes up with this error "Unsupported rotation found. Go have a cry " LOL
It's the second child object that seems to be causing it
node info:

Code: [Select]

        <node id="Box09" name="Box09" type="NODE">
          <translate>66.3911 36.0552 -57.3595</translate>
          <rotate>0.694746 0.694747 -0.186157 -158.909</rotate>
          <scale>0.464667 0.46467 0.464667</scale>
          <instance_geometry url="#Box09-mesh">
            <bind_material>
              <technique_common>
                <instance_material symbol="Standard_3" target="#Standard_3">
                  <bind_vertex_input semantic="CHANNEL1" input_semantic="TEXCOORD" input_set="1"/>
                </instance_material>
              </technique_common>
            </bind_material>
          </instance_geometry>
        </node>

Edit: i think i see where the problem with grouping and this importer is,  a group node doesn't have a geometry entry.

[Spicious]

Well, look at the rotation axis. It's just nasty. This was on the "ignore it until someone notices" list.
Is the model showing up at all now?

[Scooby_Doo]

Yes, btw is that a quadrion angle set?

edit: btw the angle for it in Max is (-150, 0, 90), the scaling looks good (46.468) and i dunno about the translation.

[Spicious]

Dunno. It's rotation axis followed by the rotation angle.

[Topgun]

how do you set this up for export? I can't figure it out.
I am using blender.

[Vasudan Admiral]

Grab a POF and export it to DAE (for starters maybe do it without helpers). Import that into blender and have a look at the naming conventions there.

If that's not what you're after, what are you currently trying? I'll try and guide you through it from the blender side of things.

[Topgun]

ok, I got it now. thanks.
but why are the path empties so HUGE? do they need to be so gigantic?

[Vasudan Admiral]

Their dimensions represent each path points radius, so yeah they do.

[Galemp]

What's the status on insignia polies?

[Spicious]

Pretty much waiting for someone to suggest a format (or ask about them).

[Galemp]

Ah. Well, the way it's been done in the past is to have an object consisting of the planes the insignia is to appear on (properly UV'd, of course) named 'insignia'. I can't help you any more than that. I don't know what POF chunk it's in, or any of that stuff.

[Spicious]

The issue regarding insignia is about storing the LOD. The rest is just a triangulated mesh with uv. It should save and load insignia now but it assumes it's for LOD 0. I didn't think anyone else bothered with them anyway...

It should be able to cope with all rotations now and the other rotation issue that no one brought up should be fixed too.

[Galemp]

I bother with them, I just don't do fighters very often.

[Scooby_Doo]

I've decided to write a little app that'll give you easier/shorter naming conventions.  All you'll need to do is run it through it then open the result with PCS2.

[pecenipicek]

just an update on the Cinema4D front, release 11 is coming out in september, with full collada support, so around that time i'll be able to contribute to the testing part.

[chief1983]

Scooby, perhaps that could be integrated into the Collada support, making the extra step unnecessary?