Scratch what I posted before, got it working, but now the turret isn't moving around, it remains static while the hp_fire seems to follow the movement, here's the relevant error:
Here's it's hierarchy in XSI: I spent the whole day trying to get this to work, no success yet, so I am desperately seeking help.

I do not know why, But I have those same errors (different node names) on the stuntank you made for me. Even though I am useing the Same odf you sent me, and I had gotten it to work, then I changed a couple odf aimer values, the it stoped working. Changing them back had no effect. No idea what going on.

Hm, that indeed is a problem :s

ive never really had luck with aimers, but are you sure that aimer_x should be under aimer_y?
and also, why is hp_active just sitting down there without connections to anything.

In every tut it is set up like this, and hp_active needs to be there, which is outside of the aimers, because else it would move and slide around when you use the turret.

Do you have a .option file for your turret with something like this as it's contents

-keep aimer_y aimer_x barrel1 barrel2 hp_fire1 hp_fire2

If not create one and put that as it's contents. This prevents VM from merging it in with all the other model bits.

FragMe! wrote:Do you have a .option file for your turret with something like this as it's contents

-keep aimer_y aimer_x barrel1 barrel2 hp_fire1 hp_fire2

If not create one and put that as it's contents. This prevents VM from merging it in with all the other model bits.

He always sends me a .option with those lines in it, so I assume he did for his turret. The tank model has the .option that was sent to me.

I will check mine
edit- contents I added the scale line...

@FragMe!: I used to have one, but it seems like I forgot to change it every time I changed it in xsi... I set it up like the autoturret with only one aimer (aimer_gun) since then I didn't change the contents of the msh.option...

Consider mine solved. Thanks!