I have dummies in Gmax for a Cyclic stick which the stick is tagged lever_stick_fore_aft and it is linked up to the parent which is a dummy box tagged lever_stick_l_r. In Gmax they move together properly (as do other objects where I have multiple dummies and links). All my objects seem to move correctly in FSX, but the Cyclic stick only moves fore and aft, even though the rotor blades move fore_aft and l_r.Is there something I'm missing ?

1. You cannot animate a "Max/GMax dummy object." You must create a tiny object with geometry, such as a 0.01x0.01 planar. When exporting, all animation is stripped out and discarded if the object has no geometry (which "Dummy" objects lack).2. You must add the Animation to the object via the Animation Manager.

Oh my... Well at least I know how to link things - hmmm....wait...But my Rotor object is linked to Dummies of "foreaft" which is linked to Dummies of "lr" and the Rotor moves correctly in FSX. Let me upload an image as I have the other Dummy I'm having a problem with, setup the same way.In the following you can see the dummies, Gmax links and the Animation Manager settings that all work okay:

Note that the "Dummy" objects to which I'm referring are the ones under the Max/GMax "Helpers" tab. They literally have no geometry whatever...On the other hand, it is not unusual for modelers to create a tiny cube (box) and refer to it as a "dummy" since it has no real function other that being a convenient object on which to Attach things or Animate things.By the way, I hope to God you never have to "Ungroup" your rotor parts for any reason, else you will very likely generate an OBED Scaling Error in your project, which is darn near impossible to get rid of... :(

Yes those are real Helper Dummy boxes with no dimensions around the rotor head.I'd like to know more about the OBED Scaling Error, as I think I might something. In FSX when the preview screen pops up the model is way way in the distance, but it is properly sized on the runway and it flys great.Oh well, on we go...

Yes those are real Helper Dummy boxes with no dimensions around the rotor head.I'd like to know more about the OBED Scaling Error, as I think I might something. In FSX when the preview screen pops up the model is way way in the distance, but it is properly sized on the runway and it flys great.Oh well, on we go...

The OBED Scaling Error is something that simply blocks your export with a nasty popup box, that makes exporting a major PITA. Oh, you'll eventually get your model out, but it's mostly annoying.As for the model's radius, you can reset that with a very handy utility program: RADItor.exehttp://www.fsdeveloper.com/wiki/index.php?title=RADItorI use it quite often to reset the radius, which is what determines the camera distance among other things. :(

RADitor worked perfect - thanks.Any more thoughts on "Yes those are real Helper Dummy boxes with no dimensions around the rotor head."Should I just delete them all and replace with mini objects hidden inside the model ?

If they are currently working, why bother?I would personally stick to using small cubes myself. What I do is create a tiny cube (box) 0.01x0.01x0.01 in size, then convert to Editable Poly. In Edit Poly sub-mode, select the sides and top polys, then delete them, leaving only the bottom face......the pivot point however will remain in the same place (0,0,0), making it a perfect "anchor node" for any other part.When I need another such "dummy," I simply Clone the original and rename it.

Finally figured out the trick here:You can link non-animated objects to animated Dummies that can be linked to other animated Dummies.You can not link an animated object to an animated Dummy, as only the animation of the Dummy will work in FSX.