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

FS2004 Kollsman Gauge adjustment knob

Messages
1,068
Country
us-northcarolina
I have a panel with an altimeter and the kollsman gauge window in it in an aircraft but pressure is only adjustable by pressing the B key which is not realistic. I want to be able to "turn a knob" to adjust it but don't know how to write the code. The knob is on the gauge but it does nothing. I can use an invisible gauge, (black square bitmap I can name) it doesn't have to rotate just have + or - click spots and I can position it over the knob. Can I have someone help me write this in XML. The gauges in FS9 are all .gau so I can't open them to see what was done in even the default Cessna Altimeter. I looked here in the forum but could not find any thread. Help please?
 
This should do it, replace the Xs Ys with location values and evaluate.

Code:
<Mouse>
      <Area Left="0" Right="X" Top="0" Bottom="Y">
         <Cursor Type="DownArrow" />
             <Click>(&gt;K:KOHLSMAN_DEC)</Click>
       </Area>
      <Area Left="X + 1" Right="X x 2" Top="0" Bottom="Y">
           <Cursor Type="UpArrow" />
               <Click>(&gt;K:KOHLSMAN_INC)</Click>
    </Area>
</Mouse>

Roman
 
Kollsman almost works

Thank you first of all for your help. I pasted this into the gauge copy below and it works but only increases there is no - "hand" to decrease the kollsman gauge. Please add to what I am sure I am missing. Thanks again.

<Gauge Name="kollsman" Version="1.0">
<Image Name="kollsman.bmp"/>
<Mouse>
<Area Left="0" Right="X" Top="0" Bottom="Y">
<Cursor Type="DownArrow" />
<Click>(&gt;K:KOHLSMAN_DEC)</Click>
</Area>
<Area Left="X + 1" Right="X x 2" Top="0" Bottom="Y">
<Cursor Type="UpArrow" />
<Click>(&gt;K:KOHLSMAN_INC)</Click>
</Area>
</Mouse>
</Gauge>

BTW I get "hand" cursors with "+" in them no matter where in the gauge I put the mouse and no "-" hands not up or down arrows.
 
If the bitmap was, for example 30 x 30 pixels one would write it as such -
Left side = down, right side = up.

Roman

Code:
<Mouse>
      <Area Left="0" Right="15" Top="0" Bottom="30">
         <Cursor Type="DownArrow" />
             <Click>(&gt;K:KOHLSMAN_DEC)</Click>
       </Area>
      <Area Left="16" Right="30" Top="0" Bottom="30">
           <Cursor Type="UpArrow" />
               <Click>(&gt;K:KOHLSMAN_INC)</Click>
    </Area>
</Mouse>
 
Honestly, I find it far, far simpler to define mouse areas using x,y,h,w coordinates, since they all use pixel units:

Code:
<Area Top="x" Left="y" Height="h" Width="w"/>

Supposing I had a knob that's 40 pixels in diameter.

Left half would be:
Code:
<Area Top="0" Left="0" Height="40" Width="20"/>
and the right half would be:
Code:
<Area Top="0" Left="20" Height="40" Width="20"/>
 
Thank you

Thanks for all your help, it works perfectly. I will study what you wrote so that I can learn more about XML.

Richard
 
Back
Top