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

model disappears when editing visibility in mcx, help?

tgibson said:
For the fuel tank question there are two things you’ll need to do. The first is to reduce the size of the numbers. This is done by reducing the Y= value. Once you have the numbers small enough, you use the position statement for each element to put the numbers where you want them. Currently, they are all located at 0,0, the upper left corner. The displayed numbers need to be moved until they’re in their correct locations.
Click to expand...
makes sense! what can i use as a reference to where to put the numbers?
 
For the last question first, the position X and Y numbers are usually the pixel values in the background image.
 
For the first question about the example code, why not use the entry for a decision height knob already in the default P3D modeldef.xml file? Just animate the knob rotation with 360 key frames and apply this tag to it.

XML: 
  <PartInfo>
    <Name>knob_decision_height</Name>
    <Animation>
      <Parameter>
        <Sim>
          <Variable>DECISION HEIGHT</Variable>
          <Units>feet</Units>
          <Scale>0.1</Scale>
        </Sim>
      </Parameter>
    </Animation>
    <MouseRect>
      <Cursor>Hand</Cursor>
      <HelpID>HELPID_CONCORDE_RADIO_ALTIMETER_KNOB</HelpID>
      <TooltipID>TOOLTIPTEXT_RADIO_ALTIMETER_DH_FEET</TooltipID>
      <MouseFlags>LeftSingle+LeftDrag+Wheel</MouseFlags>
      <CallbackJumpDragging>
        <XMovement>
          <Delta>3</Delta>
          <EventIdInc>INCREASE_DECISION_HEIGHT</EventIdInc>
          <EventIdDec>DECREASE_DECISION_HEIGHT</EventIdDec>
        </XMovement>
      </CallbackJumpDragging>
    </MouseRect>
  </PartInfo>

Hope this helps,
 
Last edited:
tgibson said:
For the first question about the example code, why not use the entry for a decision height knob already in the default P3D modeldef.xml file? Just animate the knob rotation with 360 key frames and apply this tag to it.

XML: 
  <PartInfo>
    <Name>knob_decision_height</Name>
    <Animation>
      <Parameter>
        <Sim>
          <Variable>DECISION HEIGHT</Variable>
          <Units>feet</Units>
          <Scale>0.1</Scale>
        </Sim>
      </Parameter>
    </Animation>
    <MouseRect>
      <Cursor>Hand</Cursor>
      <HelpID>HELPID_CONCORDE_RADIO_ALTIMETER_KNOB</HelpID>
      <TooltipID>TOOLTIPTEXT_RADIO_ALTIMETER_DH_FEET</TooltipID>
      <MouseFlags>LeftSingle+LeftDrag+Wheel</MouseFlags>
      <CallbackJumpDragging>
        <XMovement>
          <Delta>3</Delta>
          <EventIdInc>INCREASE_DECISION_HEIGHT</EventIdInc>
          <EventIdDec>DECREASE_DECISION_HEIGHT</EventIdDec>
        </XMovement>
      </CallbackJumpDragging>
    </MouseRect>
  </PartInfo>

Hope this helps,
Click to expand...

understandable, what if the 360 keyframes make P3D lag? also, i have issues still with the flap indicator light and the INS, could mapping be the issue?

1748662959464.png


1748663065966.png


code for flap indicator:

<Gauge Name="FlapsIndicator" Version="1.0">

<Element>
<Select>
<Value>(A:FLAPS HANDLE INDEX, number)</Value>
<Case Value="0">
<Image Name="flapsup.bmp"/> <!-- Flaps & Slats UP -->
</Case>
<Case Value="1">
<Image Name="flapsmid.bmp"/> <!-- Flaps PARTIAL extension -->
</Case>
<Case Value="2">
<Image Name="flapsdown.bmp"/> <!-- Flaps FULL down -->
</Case>
</Select>
</Element>

<Element>
<Select>
<Value>
(A:ELECTRICAL MASTER BATTERY, bool) 1 ==
</Value>
</Select>
</Element>

<Mouse>
<Tooltip>Flaps Indicator Toggle</Tooltip>
<Cursor Type="Hand"/>
<Click>
(A:FLAPS HANDLE INDEX, number) 0 == if{ (>K:FLAPS_DOWN) } else{ (>K:FLAPS_UP) }
</Click>
</Mouse>

</Gauge>

INS code, could i substitute something else for this? if so, what could be substituted?:
<Gauge Name="A300ins1" Version="1.0">

<Element>
<Select>
<Value>(A:CIRCUIT GENERAL PANEL ON, bool)</Value>
<Case Value="0">
<Image Name="insdispl.bmp"/>
</Case>

<Case Value="1">
<Image Name="insdispl.bmp"/>
</Case>
</Select>
</Element>

<Element>
<Select>
<Value>
(A:ELECTRICAL MASTER BATTERY, bool) 0 == if{ 1 (>L:ADR1, bool) } else{ 0 (>L:ADR1, bool) }
</Value>
</Select>
</Element>

<Element>
<Position X="0" Y="0"/>
<Text
X="90"
Y="40"
Length="35"
Bright="Yes"
Font="Quartz"
Color="yellow"
Adjust="Center"
VerticalAdjust="Center"
Multiline="No"
Fixed="No">
<String>%( (A:GPS GROUND TRUE TRACK, degrees) abs )%!3d!</String>
</Text>
</Element>
 
tgibson said:
For the first question about the example code, why not use the entry for a decision height knob already in the default P3D modeldef.xml file? Just animate the knob rotation with 360 key frames and apply this tag to it.

XML: 
  <PartInfo>
    <Name>knob_decision_height</Name>
    <Animation>
      <Parameter>
        <Sim>
          <Variable>DECISION HEIGHT</Variable>
          <Units>feet</Units>
          <Scale>0.1</Scale>
        </Sim>
      </Parameter>
    </Animation>
    <MouseRect>
      <Cursor>Hand</Cursor>
      <HelpID>HELPID_CONCORDE_RADIO_ALTIMETER_KNOB</HelpID>
      <TooltipID>TOOLTIPTEXT_RADIO_ALTIMETER_DH_FEET</TooltipID>
      <MouseFlags>LeftSingle+LeftDrag+Wheel</MouseFlags>
      <CallbackJumpDragging>
        <XMovement>
          <Delta>3</Delta>
          <EventIdInc>INCREASE_DECISION_HEIGHT</EventIdInc>
          <EventIdDec>DECREASE_DECISION_HEIGHT</EventIdDec>
        </XMovement>
      </CallbackJumpDragging>
    </MouseRect>
  </PartInfo>

Hope this helps,
Click to expand...

i was able to get the INS to show, all i have to do is configure the numbers to fit like in the fuel tank display gauge? something shows but as a yellow blip :

1748676020584.png
 
A306capt9 said:
understandable, what if the 360 keyframes make P3D lag? also, i have issues still with the flap indicator light and the INS, could mapping be the issue?

View attachment 96696

View attachment 96697

code for flap indicator:

<Gauge Name="FlapsIndicator" Version="1.0">

<Element>
<Select>
<Value>(A:FLAPS HANDLE INDEX, number)</Value>
<Case Value="0">
<Image Name="flapsup.bmp"/> <!-- Flaps & Slats UP -->
</Case>
<Case Value="1">
<Image Name="flapsmid.bmp"/> <!-- Flaps PARTIAL extension -->
</Case>
<Case Value="2">
<Image Name="flapsdown.bmp"/> <!-- Flaps FULL down -->
</Case>
</Select>
</Element>

<Element>
<Select>
<Value>
(A:ELECTRICAL MASTER BATTERY, bool) 1 ==
</Value>
</Select>
</Element>

<Mouse>
<Tooltip>Flaps Indicator Toggle</Tooltip>
<Cursor Type="Hand"/>
<Click>
(A:FLAPS HANDLE INDEX, number) 0 == if{ (>K:FLAPS_DOWN) } else{ (>K:FLAPS_UP) }
</Click>
</Mouse>

</Gauge>

INS code, could i substitute something else for this? if so, what could be substituted?:
<Gauge Name="A300ins1" Version="1.0">

<Element>
<Select>
<Value>(A:CIRCUIT GENERAL PANEL ON, bool)</Value>
<Case Value="0">
<Image Name="insdispl.bmp"/>
</Case>

<Case Value="1">
<Image Name="insdispl.bmp"/>
</Case>
</Select>
</Element>

<Element>
<Select>
<Value>
(A:ELECTRICAL MASTER BATTERY, bool) 0 == if{ 1 (>L:ADR1, bool) } else{ 0 (>L:ADR1, bool) }
</Value>
</Select>
</Element>

<Element>
<Position X="0" Y="0"/>
<Text
X="90"
Y="40"
Length="35"
Bright="Yes"
Font="Quartz"
Color="yellow"
Adjust="Center"
VerticalAdjust="Center"
Multiline="No"
Fixed="No">
<String>%( (A:GPS GROUND TRUE TRACK, degrees) abs )%!3d!</String>
</Text>
</Element>
Click to expand...

also, the flap indicators turn black when i extend it, indicators mimic the flap handle instead of it changing to extended from flaps up:
1748676937955.png


1748676994391.png


flaps down:

1748677067224.png


then it turns black at another press:

1748677098157.png


same thing happens at flaps mid:
1748677541917.png

flap code, what could be the problem?:

<Gauge Name="FlapsIndicator" Version="1.0">

<Element>
<Select>
<Value>(A:FLAPS HANDLE INDEX, number)</Value>
<Case Value="0">
<Image Name="flapsup.bmp"/> <!-- Flaps & Slats UP -->
</Case>
<Case Value="1">
<Image Name="flapsmid.bmp"/> <!-- Flaps PARTIAL extension -->
</Case>
<Case Value="2">
<Image Name="flapsdown.bmp"/> <!-- Flaps FULL down -->
</Case>
</Select>
</Element>

<Element>
<Select>
<Value>
(A:ELECTRICAL MASTER BATTERY, bool) 1 ==
</Value>
</Select>
</Element>

<Mouse>
<Tooltip>Flaps Indicator Toggle</Tooltip>
<Cursor Type="Hand"/>
<Click>
(A:FLAPS HANDLE INDEX, number) 0 == if{ (>K:FLAPS_DOWN) } else{ (>K:FLAPS_UP) }
</Click>
</Mouse>

</Gauge>
 
If you don’t want to use 360 key frames, copy that entry, paste it back in, rename it to something different, give it a different GUID,and change the number of key frames to what you want. Don’t forget to copy and paste the single line at the beginning of the file and rename it as well.
 
For the INS display try increasing the X= and/or the length= statements. And yes, adjust the Y= value to get the size number you need.
 
For the flaps, how many flap down key presses (or joystick button presses) does it take to extend the flaps completely? If more than three, then you have to take that into account in your case statements. Each time you press the flaps down button once, the index will increase by one. If you don’t include a case for that value, you will see nothing.
 
tgibson said:
If you don’t want to use 360 key frames, copy that entry, paste it back in, rename it to something different, give it a different GUID,and change the number of key frames to what you want. Don’t forget to copy and paste the single line at the beginning of the file and rename it as well.
Click to expand...
valid, i will do that
 
tgibson said:
For the flaps, how many flap down key presses (or joystick button presses) does it take to extend the flaps completely? If more than three, then you have to take that into account in your case statements. Each time you press the flaps down button once, the index will increase by one. If you don’t include a case for that value, you will see nothing.
Click to expand...

I think about three, which case value should i put? the zero (up) then there is one(slats 15) two, (slats 30) 2 notches on slats , and then for the trailing edge flaps 0, then (slats only) then flaps 15, 20, and 40, about 4 notches of flap. could it be a 4th case value then?
 
Yes, each flap setting must be taken into account. If you start at flaps up, how many key presses or button presses does it take to bring the flaps down to full extension? That’s the number that you have to take into account in the case statements.
 
You must log in or register to reply here.
Back
Top