[Spicious]

I thought you wanted <name>-trans to be the transparent parts of the subobject <name>.

[Vasudan Admiral]

...oh. Yeah I totally missed that. Well having just retested it, it looks like it works perfectly. Awesome!

[Spicious]

Cool. Let me know when a complete format for glowpoint helpers has been decided or if you find any problems. I'll try to get the documentation updated sometime soonish.

Is there anything else that needs doing apart from updating the options and probably adding support for matrices for rotations and translations?

[Vasudan Admiral]

What do you mean by the matricies? Where would that happen/what would it do?

Anyway, in a day or so I'll be ready to give the converter a poly-monster test. I'll let you know how it goes.

[Spicious]

Matrices are just another way to specify rotations, translations and reflections. I believe it was used somewhere in one of the 3ds samples. It wouldn't add anything new, just possibly wider support. For some reason it was decided that lots of options for specifying rotations/translations/reflections would be a good idea.

[Vasudan Admiral]

I mean I understand matricies and matrix operations, but I can't see what they would do in a DAE -> POF situation. You might be seeing the way DAE supports storing animations/physics.

[Spicious]

It's one of the "transformation_elements" like rotate, translate and scale. The blender exporter doesn't seem to use it and so I haven't implemented interpretation of it.

[DaBrain]

There might be something wrong with the UV mapping...

Bomber04 (MVP version) seems to have broken UVs.
I've exported it as DAE from PCS2 and imported it in MAX.


That's the right version, the one on the left is from Lith, which can open POFs and export them as OBJs. (Kills lods hand helpers though...)



And this is the difference in the UV layout:

[Spicious]

It's getting vertically flipped?
Is this happening when opening with other programs and is it happening on import?

A new version should flip the V part on import and export now.

[DaBrain]

PCS2 seems to load the DAE, it exported before, fine.

It's only flipped in MAX.

[Spicious]

PCS2 seems to load the DAE, it exported before, fine.

Of course it does, I've tested that.

[DaBrain]

Well, everything works fine with the new version.

It's correct in MAX and the exported DAE from MAX looks correct in PCS2 too.


However, I just noticed the object properties are missing...
I either get the helpers, or nothing.

[Spicious]

Hmm, try changing the profile attribute in one of the extra fields from "" to "FCOLLADA".

[DaBrain]

Hmm, doesn't seem to help.

Here are the two examples.

PCS2:

Code: [Select]

<node id="helper" name="helper">
<node id="properties" name="properties">
<extra>
<technique profile="FCOLLADA">
<user_properties>$special=subsystem&#13;
$fov=180&#13;
$name=laser turret</user_properties>
</technique>
</extra>
</node>
MAX

Code: [Select]

      <node id="helper6" name="helper" type="NODE">
        <translate>0.027228 -0.158232 2.31009</translate>
        <rotate>0 -0.000545 1 -180</rotate>
        <extra>
          <technique profile="MAX3D">
            <helper>
              <bounding_min>-0.01 -0.01 -0.01</bounding_min>
              <bounding_max>0.01 0.01 0.01</bounding_max>
            </helper>
          </technique>
          <technique profile="FCOLLADA">
            <user_properties>$special=subsystem&#13;
$fov=180&#13;
$name=laser turret</user_properties>
          </technique>
        </extra>
      </node>


Edit: Btw, does the POF format allow a second UV set?

[Spicious]

Try it now, I've moved the extra bit to be a direct child of the node. And helper normals should be pointing the right way again...

Edit: Btw, does the POF format allow a second UV set?

I have no idea, but no seems more likely.

[DaBrain]

Well, it looks like it works now.

At least somewhat. Max doesn't seem to interpret the breaks correct.



Btw the smoothing groups seem to work perfectly now



There is one thing I noticed abou the hierarchy though. I don't know how this looks for the Blender guys here, but for me it's pretty scary, considernig that this is just a bomber...




Edit: Well, actually a bit different.

[missilebank01]
-[firepoint01]
-[firepoint02]
-[firepoint03]

[Spicious]

At least somewhat. Max doesn't seem to interpret the breaks correct.

Blame inconsistent ends of lines of different operating systems.

Btw the smoothing groups seem to work perfectly now

Is this different to before?

Edit: Well, actually a bit different.

[missilebank01]
-[firepoint01]
-[firepoint02]
-[firepoint03]

That's the sort of approach I would have gone with for everything. Thrusters and paths have sort of migrated over to that way. I guess gunpoints and dockpoints probably will when I get time.

[DaBrain]

The last time I really tested for smoothing groups, it didn't work, but that has already been a quite a while ago... some days... don't ask... I don't realyl remember how many...

[chief1983]

Spicious, perhaps you could run the file through a replace on \r\n to just \n, or vice versa, so it's always in a consistent state?  From the looks of that screenshot, Max needs a carriage return and a new line, and there's probably just a new line.

[KewlToyZ]

as a meantime "fix", TrueSpace 7.51 supports collada, however, i'm stilly trying to make it work.

i am experimenting on how to get the hierarchy through from cinema 4D to truespace, and no fish for now.

neways, i've tried exporting fbx from cinema then importing back in, the hierarchy sticks correctly, but truespace doesnt do fbx. okay. so find a fbx to dae converter (autodesks fbx converter is the one i'm using) and it converts the fbx to dae with no hierarchy loss, tested with a viewer app, however, getting it back to fbx doesnt work for some reason. will do some more research why truespace doesnt read the collada file made by the converter.

[edit#1]aaand for some silly reason, 7.51 apparently only exports dae, doesnt import it... yayness... will get back to this as soon as i find another solution.
[edit#2] ts 7.51 doesnt import collada file generated by itself either.... hmmm... perhaps the old vrml file format might be of use XD
will test.
[edit#3]tried exporting to wrl, it conserves the hierarchy, but smoothing seems... a bit odd. probably doesnt conserve it really well...

however, for anyone having woes with hierarchy exporting, the wrl format seems the most... well, usable one. ts 3.2 should be able to open it no problem too, so use it till we get proper collada into pcs2




aaaand my woes with the hell that is truespaces hierarchy are oooooveeeeer XD

hierarchy comparison from the two proggies.


minor differences, the names are preserved and the ordering is a bit different, but it works.

(those noticing me using the ts 3.2 trueview plugin with ts7.51 are getting shot in the balls. truespace lacks good native hierarchy editors.)

also, should i post this under freespace modding forum? the temporary solution for hierarchy transfer?)

I'm getting my full version of Rhino 4.0 this week and it does save to fbx, 3ds, 3dm, well many formats but not collada.
I'll have to take a look at the Autodesk fbx converter and see if that works.
If I can have a ready conversion from Rhino into PCS2 I'm going to be really happy if it is just fbx I need to use.
I just want anything except MAX to work with files. I'm surprised more modelers arent using Rhino, especially the Students?