• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FSXA FSX: Still name-sensitive!?

Heretic

Resource contributor
Messages
6,830
Country
germany
I've got prop disk models that change visibility based on prop pitch (a thin disk and a thick disk). Both disks are children to a spinner that is visibility tagged and were made from the default _slow (thin) and _blurred (thick) disks.

The code was easy and sound (no bracket errors, really!), the mesh was simple and error-free. But no matter what I did, I could not get the thin disks to show up.

Then I changed their names from the old "prop0_slow" to anything else and now they show up like they are supposed to.


I thought that name-sensitivity for parts got left behind after FS9, but hey...
 
An object using the "prop0_slow" <Visibility> tag only displays very briefly, as the actual XML conditional script only makes the part visible from 6.25% to 12.5% prop rpm.

Did you write custom XML script for your two prop disks? If so, what is it?

For my latest project, I've written custom XML scripts that will allow me to define the visibility and animation conditions in a separate XML "gauge" so that I don't have to keep exporting/compiling the model constantly while I tinker with the conditions...
Code:
  <PartInfo>
    <Name>KA350i_Prop0_blurred</Name>
    <Visibility>
      <Parameter>
        <Code>
          (L:Prop0_blurred_vis,enum)
        </Code>
      </Parameter>
    </Visibility>
    <AnimLength>100</AnimLength>
    <Animation>
      <Parameter>
        <Code>
          (L:Prop0_blurred,enum)
        </Code>
      </Parameter>
    </Animation>
  </PartInfo>
 
  <PartInfo>
    <Name>KA350i_Prop0_slow</Name>
    <Visibility>
      <Parameter>
        <Code>
          (L:Prop0_slow_vis,enum)
        </Code>
      </Parameter>
    </Visibility>
    <AnimLength>100</AnimLength>
    <Animation>
      <Parameter>
        <Code>
          (L:Prop0_slow,enum)
        </Code>
      </Parameter>
    </Animation>
  </PartInfo>
 
  <PartInfo>
    <Name>KA350i_Prop0_still</Name>
    <Visibility>
      <Parameter>
        <Code>
          (L:Prop0_still_vis,enum) !
        </Code>
      </Parameter>
    </Visibility>
    <AnimLength>100</AnimLength>
    <Animation>
      <Parameter>
        <Code>
          (L:Prop0_still,enum)
        </Code>
      </Parameter>
    </Animation>
  </PartInfo>
 
Last edited:
Can you have multiple objects using the same name with visibility tagging? I know with a throttle lever with a mouse zone you can't have duplicate throttles using the same name as the mouse zone will only work with the first instance.

Can you have visibility tagged objects children of other visibility tagged objects?

Stretching my memory but I think I had a problem with a GPS unit. The display was visibility tagged (to control on/off and self illuminnation) and the whole GPS was visibility tagged (so the user could switch it out if wanted). The display visibility tag wouldn't work at all and I think I determined the problem being it was a child of another visibility tagged object that was the problem (ie the whole GPS).

@bill. I like the way you've thought outside the box there to come up with a neat method of working. But why not use a single L var to store the prop vis state? eg 0 = still, 1 = slow, 2 = blurred. Saves on L vars and saves on writing to L vars (a very minor point I must admit).
 
Can you have multiple objects using the same name with visibility tagging? I know with a throttle lever with a mouse zone you can't have duplicate throttles using the same name as the mouse zone will only work with the first instance.
Thats only fsds, afaik it doesn't happen in max's. you can edit the admin file or just change the name of the animation, so multiple copys of lever_throttle0 renamed to rear_gogo front_gogo the names have to be unique
 
An object using the "prop0_slow" <Visibility> tag only displays very briefly, as the actual XML conditional script only makes the part visible from 6.25% to 12.5% prop rpm.

The object was only named "prop0_slow" and not tagged at all! The visibility switching was done by the prop spinner, the parent part. And the spinner always showed up, but the disk wouldn't unless I renamed it to anything but "prop0_slow".
 
@bill. I like the way you've thought outside the box there to come up with a neat method of working. But why not use a single L var to store the prop vis state? eg 0 = still, 1 = slow, 2 = blurred. Saves on L vars and saves on writing to L vars (a very minor point I must admit).
I use separate L:vars for the visibility because I might (in fact I do!) wish to 'blend' them such that they "overlap" a bit rather than simply switch instantaneously. At least this way leaves me the most flexibility to 'experiment'.

@Heretic: I suspect that certain FS9 "part names" remain "reserved" because of the backwards compatibility issue. At least that is what your experiential evidence is suggesting.
 
@Heretic: I suspect that certain FS9 "part names" remain "reserved" because of the backwards compatibility issue. At least that is what your experiential evidence is suggesting.

That would make for a nice little experiment. Give a part a FS9-alike name, but do not tag it and see what happens in FSX. It would be pretty ironic if the "FSX is new and different, so tag EVERYTHING" mantra conveyed for FSX wasn't really necessary at all. :D
 
Back
Top