• 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 Gauges to trigger playing sounds

You've missed my very first statement. This needs to be fixed:
Code:
 1 (">>G:Var1) (L:Stabilizer, degree) -2.5 ">>
                    1 (">>L:PushedSound,number)
                        if{
                            (L:Stabilizer, degree) 0.05 - (">>L:Stabilizer, degree)
                          }

At the moment, you're evaluating something, write something to another variable and have some code that is executed after an evaluation. I really do not think that this is the correct order.
Fix this and see if it helps with the looping sound.
 
Fix this and see if it helps
Will this work:

XML:
                (M:Event) 'LeftSingle' scmp 0 ==

                (L:Stabilizer, degree) (L:Stabilizer_Old, degree) != &&

                if{

                    1 (>G:Var1) (L:Stabilizer, degree) -2.5 &gt

                                           

                        if{ 1 (>L:PushedSound,number)

                            (L:Stabilizer, degree) 0.05 + (>L:Stabilizer, degree)

                            (L:Stabilizer, degree) (>L:Stabilizer_Old, degree)

                          }

                  }
 
There's some P3D4 issue now with the crew xml gauge I am trying to fix. The problem is when I switch to external views the crew stops working, no more announcements made and the switch & button sounds of the 2D panel are gone.

Also the crew gauge does not work now or glitching in the default Mooney Bravo I used to test it with.

I suspect there could be a registry issue with P3D4 since I made an installer for my updates that added some keys to HKEY_CURRENT_USER but just to get the path for my further updates.

Any thoughts, greatly appreciated.
 
Looks like SOLVED! I compared the P3D4 path key with mine added to HCR and found that mine goes without '\' in the end. Added the backslash and now somehow it looks like fixed! :stirthepo
 
It has occurred again. No button / switch sound except one knob. The trick with the backslash did not help.

It happened probably after I killed S-1-5-21-1112941502-2766888855-3757027976-1000 folder from the registry.

Did not try re-installing P3D4 yet.

Any solutions would be highly appreciated.
 
From on very old avsim thread. Don't remenber the author!

Code:
With a little educated guessing, I found the answer to my
question: "How to trap Shifted/Controlled keystrokes in
XML"

I discovered, that instead of using:

<On Key="Z">...</On>

FS also accepts

<On Key="90">...</On>

  with '90' being the Windows keycode for the 'Z' key.

Now, since keycodes are ranging from 0-255, I wondered how MS
would internally store the value for shift/control sequences.
I took an educated guess, by adding multiples of 256 to the
keycode; and behold: IT WORKED !!

Iow:

- <On Key="90">...</On>  traps  "Z"

- <On Key="346">...</On> traps  "Shift-Z"           256 + 90 = 346

- <On Key="602">...</On> traps  "Control-Z"         512 + 90 = 602

- <On Key="858">...</On> traps  "Shift-Control-Z"   768 + 90 = 858

FYI: A list of all Windows keycodes can o.a. be found in
Peter Dowson's FSUIPC Userguide. An extract of that info is
attached to this post..

---------------------------------------------------------------------------------------------------

<!-- Crtl plus Key Left arrow 512 plus 37 -->
    <On Key="549">
       (&gt;K:VOR1_OBI_DEC,degree)
    </On>

<!-- Crtl plus Key Right arrow 512 plus 39-->
    <On Key="551">
     (&gt;K:VOR1_OBI_INC,degree)
    </On>
 
Will it work this way:


XML:
<Element>
<Position X="" Y=""/>
<Select>
    <Value>(L:SEATBELTSSIGNSWITCH,bool)</Value>
    <Case Value="0">
        <Image Name="Switch_OFF.bmp"/>
    </Case>
    <Case Value="1">
        <Image Name="Switch_ON.bmp"/>
    </Case>
</Select>
</Element>

   <Mouse>   

<!-- Ctrl+ Z -->
<On Key="602">(&gt;L:SEATBELTSSIGNSWITCH,bool)</On>
<!-- Ctrl+ Z -->

        <Area Left="" Top="" Width="" Height="">   
         <Tooltip></Tooltip>
                <Cursor Type="Hand"/>
            <Click>
                (L:SEATBELTSSIGNSWITCH,bool)
    
                if{
                    0 (&gt;L:SEATBELTSSIGNSWITCH,bool)
                    1 (&gt;L:Sound1,number)
                  }
    
                els{
                     1 (&gt;L:SEATBELTSSIGNSWITCH,bool)
                     1 (&gt;L:Sound1,number)
                   }
    
        </Click>
        </Area>   

   </Mouse>
 
Back
Top