OOPs, sorry it's working now. (I rebooted Windows, and now it works much like the 2020 version does). Color me happy.

What specific aircraft?

On 11/27/2024 at 2:40 PM, Lorby_SI said:

The issue in AAO can probably be resolved using Hardware-> Device Blacklist. Move everything on the left into the list on the right with the "Ignore" button that isn't a proper game controller that you are using in AAO. This includes all mice and keyboards, they must be ignored as well.

Can't help you with MSFS though. Since AAO does not alter any files or settings in MSFS I can't see how this could possibly be related?

Hello, thanks freeze is resolve.

On 11/27/2024 at 2:40 PM, Lorby_SI said:

The issue in AAO can probably be resolved using Hardware-> Device Blacklist. Move everything on the left into the list on the right with the "Ignore" button that isn't a proper game controller that you are using in AAO. This includes all mice and keyboards, they must be ignored as well.

Can't help you with MSFS though. Since AAO does not alter any files or settings in MSFS I can't see how this could possibly be related?

Hello, thanks freeze is resolve.

Hello, I’m coming back to this forum to share my experience with a bug related to MSFS2024. Indeed, in order to use AxesAndOHS, I went into the control settings in the simulator to delete some configurations. I tried switching between different profiles of the Cessna 172, and I must have made a change that caused an error.

What happened next was that, by default, the selected C172 was the G1000 cargo version, and if I wanted to select another G1000 version, the game would crash. Since this plane is also the starting one in career mode, my career mode would crash as well. I was stuck, and various updates didn’t fix the issue.

I finally found a solution: deleting the cloud-saved data. I reset to the default configuration and was finally able to select a C172 G1000 version other than the cargo one.

The steps are as follows: in the command prompt, type
shell:appsFolder\Microsoft.Limitless_8wekyb3d8bbwe!App -DeleteCloudSaves.
Be aware that this will erase all your configurations, but at least it resolves the bug.

If anyone else experiences this issue, hopefully, this can help them.

Fly safe and have a great day!

Hi,

I used AAO with MSFS2020 and now I wanted to import .tmpl files to use with MSFS2024.

Where are they stored? I can't find.

I hope I don't have to do all the work again with default planes for example...

Thanks

1 hour ago, MarcinEr said:

Hi,

I used AAO with MSFS2020 and now I wanted to import .tmpl files to use with MSFS2024.

Where are they stored? I can't find.

I hope I don't have to do all the work again with default planes for example...

Thanks

In my experience, the default planes in MSFS2024 are not identical to those in 2020. You will have to rework most of your things anyway.

Templates you will have to export first to .tmpl files in AAO20, then import them in AAO24.

But if you insist, you can copy your entire 2020 database over to AAO 24 using the Tools menu:

1. Make sure that you have the latest version of AAO installed for both 2020 and 2024
2. Create a database backup ZIP file with AAO20
3. Restore this file in AAO24

In my personal view, this is not a good option though. It produces a massive amount of database junk, because the 2024 aircraft are so different that much if it has to be updated anyway. But that is just my opinion, nothing more.

Edited December 29, 20241 yr by Lorby_SI

As for now I can't make X-touch mini (Behringer) to work with AAO...It was so complicated 2 years before.

Any easy tip?

 

2 hours ago, MarcinEr said:

easy

In that case:

2 hours ago, Lorby_SI said:

1. Make sure that you have the latest version of AAO installed for both 2020 and 2024
2. Create a database backup ZIP file with AAO2020 ("Tools->Create Database Backup")
3. Restore this file in AAO2024  ("Tools->Restore Database from Backup")

Adding

4. Pray that not too many things have changed in the MSFS 2024 aircraft

Edited December 29, 20241 yr by Lorby_SI

That worked for me! Thanks a lot 🙂

Hi, just for confirmation: the current G3000 bridge that can be found in your downloads page is just for MSFS2020, isn't it? I'm running MSFS2024 and the new G1000 bridge works fine.

On 12/30/2024 at 10:47 AM, VillaJota said:

Hi, just for confirmation: the current G3000 bridge that can be found in your downloads page is just for MSFS2020, isn't it?

That is correct, the G3000 brigde is for MSFS 2020 only. I'm not entirely sure if it can ever work in MSFS2024, haven't had time to look into this in detail. MSFS has been "locked" for all addon package that try to do something like this. There is a way, but that only works when the developer of the instrument (in this case the G3000) makes it possible - so we are at their mercy regarding bridges and WebFMCs.

Edited January 1, 20251 yr by Lorby_SI

On 12/30/2024 at 10:47 AM, VillaJota said:

Hi, just for confirmation: the current G3000 bridge that can be found in your downloads page is just for MSFS2020, isn't it? I'm running MSFS2024 and the new G1000 bridge works fine.

G3000 bridge has been adapted for MSFS 2024 just now.

First I want to say AxisAndOhs makes my sim life so, so much better. Excellent work! 

Having moved to 2024 from 2020, I'm trying to setup the Streamdeck Standard Avionics Suite with the 172 G1000. The softkey buttons work, the flight planning keys work (Direct, Proc, FPL, etc), anything pressable works and interacts with the in-game g1000 (PFD and MFD). However, no strings seem to be returned to AAO so no strings display for any softkeys on the streamdeck.

Using the Observe Variables in Simulator tool I'm not seeing anything returned for (L:G1000_PFD_SOFTKEY_2, String) (as an example). It's simply (L:G1000_PFD_SOFTKEY_2, String)[] this is the case for all softkey texts: [WINDOWS]

A variable like (L:AaoVoiceRecEngine, String) returns (L:AaoVoiceRecEngine, String): [WINDOWS] but I'm not certain that's actually coming from the sim.

AAO 4.51 b09
Latest zzz-lorbysi-aao-wtg1000 in the community folder

Not sure what else to check or try.

2 hours ago, FujitsuPolycom said:

Latest zzz-lorbysi-aao-wtg1000 in the community folder

Check if it really is the latest. The package had to be rewritten completely, as MSFS2024 is more limited than MSFS2020 was. 

And make sure that you are running AAO "As administrator", same as before. You did install the separate 2024 variant for AAO, right? There is no "update" from AAO 2020 to 2024, they are two separate programs living on your computer in parallel.

For the record: none of the (L:.., String) Variables is coming from the sim, they don't exist in the "real world". They are all AAO internal and in this case coming from the zzz package.

Edited January 9, 20251 yr by Lorby_SI