• 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.

Argh! It happend again! :(

n4gix

n4gix

Resource contributor
Messages
11,674
Country
unitedstates
I cannot believe this! It happened to me again...

...that I spent over a full week trying to figure out why my bloody radar altimeter needle refused to budge off the lower stop.

I knew the needle and animation was okay, 'cause when I assigned it to the airspeed needle's script it rotated just fine. Is the GUID 'poisoned' for some reason? Nope. Was it a duplicate? Nope.

Finally, late this afternoon while working on something else entirely, I spotted the problem. I'll bet everyone will spot the stupid mistake within mere moments. :rotfl:
Code: 
  <!-- RADAR ALTIMETER -->
  <Animation name="B300_Radar_Alt_Needle" guid="a226768c-f82d-44e6-bba6-d88dfbc179cd" typeParam2="KA300_Radar_Alt_Needle" length="200" type="Sim" typeParam="AutoPlay" />

  <PartInfo>
    <Name>B300_Radar_Alt_Needle</Name>
    <AnimLength>200</AnimLength>
    <Animation>
      <Parameter>
        <Code>
          (L:B300_RadarAlt,enum)
        </Code>
      </Parameter>
    </Animation>
  </PartInfo>
 
The name does not match in the GUID entry! I find that i sometimes copy the name from my code and when i paste it into a new GUID entry and i some how copy the > symbol since the font is so small and then i wonder why it's not working!:banghead:
 
Last edited:
Yup...classic "B300-KA300" mismatch. Gets 'em every time :laughing:
I never did anything like that before...:eek:
 
What is particularly infuriating is that there was never a valid reason for this rediculous 'system' to begin with! ACES made the claim that the entry for typeParam2= was created for "backward compability," but that fails the sanity test since it would only be required for purposes of bringing forward a port of an FS2002 model for heaven's sake! Who would do such a silly thing to begin with?

So, the name= entry is required for the "AnimationManager" in GMax/Max, but the typeParam2= is used only by the XToMDL.exe compiler! :banghead:
 
Oh man.... All those days lost over that one mistake. Glad you found it Bill.

(blood pressure returns to normal. Sleep returns).
 
When editing various files like this, I often fall prey to what I like to call "Copy-Paste Russian Roulette" I think I am saving time using copy-paste rather than type in from scratch…and then something like this happens. :confused:

Glad you caught it!:)
 
You must log in or register to reply here.
Back
Top