I spent the weekend learning about attaching animations, visibility and effects to parts, fun stuff even if my family doesn't think so .
From my research, it seems that all Gmax/3DS part animations and visibility features eventually come from Modeldef.xml.
1) I saw the post in another forum by Fr. Bill about the missing taxi_light entry in modeldef.xml. It seems the SDK only includes the general_lights for visibility, which doesn't seem quite complete. Logical thus far to add taxi lights. The SDK documentation on attaching a green nav light to the DC3's flex wing stops short of attaching the tag itself. Since I didn't find a tag that controls nav light visibility (there is one that controls the nav light switch for a VC), I assume I need to go in an create a similar entry for nav lights, beacon, etc, tied to LIGHTS NAV, LIGHTS BEACON, respectively provided they are on moving parts (that precludes the use of the aircraft.cfg to attach lights).
To create new animations/visibility types, is it really just a matter of adding new entries to enhance the default set provided just by ensuring the new entry has a unique ID and name?
2) Moving further in the possibilities, can C: tags be used in modeldef.xml to expand functionality beyond the default "sim variables"?
I'm thinking along the lines: hey, I can model more doors, more lights, refueling boom, none of which are built-in the default feature set.
Sounds too good to be true. This is a sanity check after long hours...
Etienne
From my research, it seems that all Gmax/3DS part animations and visibility features eventually come from Modeldef.xml.
1) I saw the post in another forum by Fr. Bill about the missing taxi_light entry in modeldef.xml. It seems the SDK only includes the general_lights for visibility, which doesn't seem quite complete. Logical thus far to add taxi lights. The SDK documentation on attaching a green nav light to the DC3's flex wing stops short of attaching the tag itself. Since I didn't find a tag that controls nav light visibility (there is one that controls the nav light switch for a VC), I assume I need to go in an create a similar entry for nav lights, beacon, etc, tied to LIGHTS NAV, LIGHTS BEACON, respectively provided they are on moving parts (that precludes the use of the aircraft.cfg to attach lights).
To create new animations/visibility types, is it really just a matter of adding new entries to enhance the default set provided just by ensuring the new entry has a unique ID and name?
2) Moving further in the possibilities, can C: tags be used in modeldef.xml to expand functionality beyond the default "sim variables"?
I'm thinking along the lines: hey, I can model more doors, more lights, refueling boom, none of which are built-in the default feature set.
Sounds too good to be true. This is a sanity check after long hours...
Etienne