Thanks for your answer, maybe there is no link, it is likely.
For the latency I will make a comparison with MSFS2020 that I still have.
I will give you feedback
Have a nice day

Greetings,

The MSFS: G1000 Bridge variables are not being seen by my Streamdeck with FS2024. Are you able to confirm if; 1.  if there is a work around 2. patchable  or 3. A restrictions of the new sim?

10 hours ago, Pngmikel said:

3. A restrictions of the new sim?

All existing bridge packages are only for MSFS 2020. They do not work with MSFS 2024.

The reason is the lock on the core file system that is in place in MSFS 2024, the packages can no longer function. Plus, there are new versions of some of the instruments, for example the G1000 and G3000. 

Of the WebFMCs, only those that don't have a Community package will work (=PMDG, iFly, TFDi, Aerosoft, MadDog).

I am experimenting with other solutions, but... the one that works is very invasive and frowned upon by the developer community, and the official solution (Plugin) simply doesn't work for me.

Edit: I've marked the assets on the download page as "MSFS 2020 only". On flightsim.to they should only have the 2020 compatibilty tag anyway.

Edited November 28, 20241 yr by Lorby_SI

On 11/27/2024 at 11:23 PM, Pngmikel said:

Greetings,

The MSFS: G1000 Bridge variables are not being seen by my Streamdeck with FS2024. Are you able to confirm if; 1.  if there is a work around 2. patchable  or 3. A restrictions of the new sim?

Here is a replacement for the Community package of the G1000 bridge. I've tested it successfully with MSFS 2024 and 2020 too.

(snip)

I've updated the G1000 package on the axisandohs.com website. There are two separate downloads now, one for FS20, the other for FS24

 

Edited November 29, 20241 yr by Lorby_SI

Working perfectly, much appreciated.

If you go the task scheduler route, you can then add this to your EXE.xml for autostarting with elevated permissions:

<Launch.Addon>
    <Name>AAO task</Name>
    <Disabled>False</Disabled>
    <Path>C:\Windows\System32\schtasks.exe</Path>
    <CommandLine>/run /TN "AAO"</CommandLine>
  </Launch.Addon>

Replace "AAO" with whatever you named your task....I made one for 2020 and a second one for 2024 name "AAO2024"

I’m having real trouble with Bvars/IEs with the Stream Deck plug in. No matter what I try they just don’t seem to fire? Regular K, L etc events are firing fine. I’m using the behaviour dialog in the sim dev mode, and the var names I’m using seem to work in Mobiflight, and if I use them directly in AAO. I’m completely baffled. Anyone had a similar issue they’ve resolved?

Edited December 1, 20241 yr by StevenKB

16 minutes ago, StevenKB said:

I’m having real trouble with Bvars/IEs with the Stream Deck plug in. No matter what I try they just don’t seem to fire? Regular K, L etc events are firing fine. I’m using the behaviour dialog in the sim dev mode, and the var names I’m using seem to work in Mobiflight, and if I use them directly in AAO. I’m completely baffled. Anyone had a similar issue they’ve resolved?

Which simulator? MSFS 2020 or 2024? Also, BVars and IEs are similar, but not the same. They are operated by different mechanisms in AAO. Which one is it?

There are two items in version 4.50 that could be related:

1. BVars don't work in in the MSFS2024 variant of AAO. That has been the case from the beginning. A work around has been found now, and it will be released with version 4.51

2. IEs apparently stopped working in the MSFS 2020 variant of AAO. The weird thing is, that this seems to be a problem for some, but not for others. In any case, the logic will be reworked in 4.51 so it works consistently across simulators.

 

Edited December 1, 20241 yr by Lorby_SI

Sorry, yeah, the sim version would help!

Running MSFS 2024, AAO 4.5.0 and the latest version of the sd plugin. Been using the same IEs I’ve used successfully in AAO itself. I’ve worked around for now by making buttons in the SD profile and mapping them to IEs in AAO itself. 
 

Im a bit woolly around the differences between IEs and Bvars so sorry for the confusion. 

7 minutes ago, StevenKB said:

Sorry, yeah, the sim version would help!

Running MSFS 2024, AAO 4.5.0 and the latest version of the sd plugin. Been using the same IEs I’ve used successfully in AAO itself. I’ve worked around for now by making buttons in the SD profile and mapping them to IEs in AAO itself. 
 

Im a bit woolly around the differences between IEs and Bvars so sorry for the confusion. 

Just to make sure: your post was about the BVars not working with AAO in MSFS 2024?

That is correct, and should be noted somewhere at the beginning of this thread.

Normally you should be able to convert all BVars to IEs, since both are related. There may be instances though, where the BVar is the preferred solution. For example when you need INC and DEC, but the IE doesn't have that. I just had a case like this (heading bug on the 737 max), and that is why BVars will be back in AAO version 4.51.

There is also a work arond for version 4.50, in case you desperately need them:  prepend every script that uses BVars with (SIMPROC)

(SIMPROC) 1 (>B:FCC_HEADING_SEL_Inc)

(SIMPROC) 1 (>B:FCC_HEADING_SEL_Dec)

Edited December 1, 20241 yr by Lorby_SI

I can’t get IEs or Bvars working through the SD plugin, but IEs work fine from the AAO app itself. 
 

Basically, it’s all good in AAO, I’m just having a pain with the Stream Deck

12 minutes ago, StevenKB said:

I can’t get IEs or Bvars working through the SD plugin, but IEs work fine from the AAO app itself. 

BVars don't work yet, that is correct. The will work again in 4.51 

But IEs don't have an excuse - as far as I'm aware they should be working. Some of the StreamDeck profile authors are also AAO testers, and they didn't report anything of this sort. Can you give me a specific example? 

Be mindful that IEs are named differently in MSFS 2024. They are all upper case now.

Edited December 1, 20241 yr by Lorby_SI

Hah! Well there you go! IEs working from the SD, I must have been mixing them up with Bvars

Thank you muchly

I found it easier for me to just create scripts for the IE variables, then reference them in SD and AAO binding....they seemed problematic when trying to bind then directly to controls

I have a problem with AAO 2024 version. Nothing at all works. Lets say I add an axis to aileron or rudder. None of those two surfaces move in the sim.

NOTE: I have used AAO 2020 without any serious issue at all for years now.

NOTE 2: When I jump into a plane in 2024, AAO displays the plane name, so AAO has connected to MSFS2024.

I think I have made a simple mistake somehow, forgot some little thing?