[Scooby_Doo]

One more question... how are multiple thruster banks named?    I've got: thrusters->thruster01-01 but that doesn't seem to work.

[Spicious]

That should work. The names of the individual glows don't matter; only the thrusters name matters. I've changed the export naming to better reflect this but since this is non-critical, it can wait until a bigger reason for a new build.

[Scooby_Doo]

So should it be thrusters->thruster, thrusters->thruster?  When dealing with more than one thruster group (i.e. different engines)

[Spicious]

If you've got several thruster groups, each group corresponds to one "thrusters" (this could really use a better name). If you want these thruster groups linked to engine subsystems, they should be children of the subsystem's helper node.
So something like

• thrusters
  • thruster
  • thruster
• thrusters
  • thruster
  • thruster
  • thruster
• subsystemEngine01
  • helper
    • thrusters
      • thruster
      • thruster
      • thruster
• subsystemEngine02
  • helper
    • thrusters
      • thruster
      • thruster
• detail0
  • Engine03
    • helper
      • thrusters
        • thruster
        • thruster

[Scooby_Doo]

Hmmmm  having: detail0->subsystem->helper->thrusters->thruster gives me a "uv not found. How very boring"


edit: actually i think it might be something else that crept into it.

[Spicious]

Is your subsystem a physical subsystem?

[Scooby_Doo]

Is your subsystem a physical subsystem?

Tore apart the entire heirarchy structure and rebuilt it, the problem seemed to go away.

[Akalabeth Angel]

Okay I'm noticing a problem. I took a cargo pod, added basically a box around it made out of 6 distinct walls. I gave these walls their own texture. In Maya, I have the walls with their texture, parented to the cargo box with its FS2 texture. I export as .dae, but when I load it up in PCS2 the walls no longer have thier own texture, instead they have the same texture as the cargo box.

[attachment deleted by necromancer]

[Spicious]

Why couldn't maya play nice and use the same naming everywhere? It was actually defaulting to the first texture in the texture list for everything. It should be fixed now.

[Scooby_Doo]

Question for those with experience in Max linking and hierarchy...

I've got detail0 pivot point centered at (0,0,0) it's been x-reseted and collapsed.
I've got helper and glowbank centered at (0,0,0) and it's also been x-reseted and collapsed.
Finally I've got many glowbank0X-0X positioned in the correct spot, x-reseted and collapsed.

Everythings linked correct.  Detail0->helper->glowbank->glowbank0x-0x.  Everything looks good in max, but in PCS2 the glowpoints are not in the correct position anymore. 

[Akalabeth Angel]

Why couldn't maya play nice and use the same naming everywhere? It was actually defaulting to the first texture in the texture list for everything. It should be fixed now.

   Sweet, works now thanks

[Scooby_Doo]

Fixed it... the glowbanks moved on me without me realizing it.

BTW is there any chance of numberized glowpoints?  It's kinda hard to make things like landing/take off lights when it's basically a game of "guess which ones".

[Spicious]

Fixed it... the glowbanks moved on me without me realizing it.

Try a new build and tell me if they're still in the right places.

BTW is there any chance of numberized glowpoints?  It's kinda hard to make things like landing/take off lights when it's basically a game of "guess which ones".

It shouldn't be a problem, but we still have to decide on a format for storing on/off times and the like for glowbanks. So far no one seems to have had much interest.

[Scooby_Doo]

Also I just learned something... don't delete those -normal/-glow/-shine textures from the texture list otherwise your entire model will get messed up.

[Kazan]

Is PCS2 cross platform?

99% - just need to get it to compile under linux - should just be a few tweaks EXCEPT all the major distros install the unicode wxwidgets and i've been compiling for non-unicode under windows

i'll probably go through the effort to move to unicode when i make the effort to allow compiling for 32 and 64 bit targets.

[Kazan]

If that's the goal, we'll definitely want to do DAE <-> PMF.

got DAE format specs?

as you've seen by now from the source it's fairly easy to integrate new file formats (which is why i created PMF - to be an internal format easy to convert to, then only have to PMF->POF and not worry about the PO shiat ever again)

[Galemp]

Where have you been? Check his signature for the build and this wiki page for all the other resources.

[chief1983]

I just went over that in another thread, that's how he ended up here.  But yeah, I forgot to mention the latest build is in Spicious' sig.

[Spicious]

Code diff is attached. Enjoy the mess.

[attachment deleted by admin]

[fletcher]

You mention a linux build, any chance of a OSX build aswell?

That'd be pretty sweet