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

FSX [SOLVED] Animated VSI shows ~1/2 the value it should

D

Dave_W

Resource contributor
Messages
185
I have a window that displays various performance readings. This is where I see that the gauge is reading the low value.

It uses this:
Code: 
Vertical Speed\t%((A:VERTICAL SPEED, ft/min))%!d!
to show the vertical speed.

My gauge has this code:
Code: 
    <AnimLength>80</AnimLength>
    <Animation>
      <Parameter>
        <Code>(A:VERTICAL SPEED, ft/min) 100 / 40 +</Code>
      </Parameter>
    </Animation>

FWIW here is a picture from Blender showing the keyframes:
keyframes.JPG


Each number has a key.

I'm sure there is something obvious that isn't right, but I've messed around with this for so long that I can't figure it out.
 
This should work -
<Code>(A:VERTICAL SPEED, ft/min) -2000 max 2000 min 50 / 40 +</Code>
From -2000 to +2000 fpm is a range of 4000, therefore 4000 / 80 KFs = 50
Every ten keyframes starting at -2000, fall on the major "ticks".
-2000 = 0
-1500 = 10
-1000 = 20
-500 = 30
0 =40
500 = 50
1000 = 60
1500 = 70
2000 = 80
 
It does!

Thanks a lot Roman.

I would have never dreamed of code like you used. :scratchch
 
You must log in or register to reply here.
Back
Top