Sometimes the wizard fixes the Heirarchy… sometimes it doesn’t… it depends on what YOU did. andnbsp;IE; Children, clones, scripts… etc…
I always go back to my heirarchy and check my work and I also andnbsp;always andquot;renameandquot; objects so I remember what they are and why I made them. andnbsp;By doing this… I andnbsp;make sure I meet the MSTS guidelines for objects before I export to the SIM.
I did some road signs made up of only two objects (the pole and the sign). The sign itself was two merged cubes (transparencies too on all but one side). On most of the road signs, only the pole was showing in the sim. What it turned out to be was the way the heirarchy was set, for some reason the sign didn’t show. I’m bringing this up to understand how important the heirarchy is. Normally I just create object after object in a model and then let the script do its thing. Am I bad for doing this? There is a disclaimer that pops up. I thought heirarchies would only be important for something that included animation (though I don’t know why). I’m sure this has been talked about this before or maybe not, but why does the heirarchy affect the appearance of a model when transparencies are included? This might also help to explain why when I did some trees I had to export the tree twice. The first time only the .sd file was written, the second time it would do the .s file (only after I refreshed the model by using new and then reloading the model). andnbsp;Thanks!
RG
You must be logged in to reply in this thread.
