53 minutes ago, Guitou1111 said:

Would it be possible to continue by adding a bridge and profile of native Gtn650 used in some aircraft of MSFS2024?

What would that "bridge" do? It is not possible to stream the contents of the screen, you would have to use CAPTURETOFIP for that (like in the AAO WebFMCs Vol2, there is an example with the 530)

Edited February 16Feb 16 by Lorby_SI

Hi Lorby,

I just updated to v 4.57 and now my web FIPS and desktop FIPs stay empty,

has something changed?

This is with Touch Mini, 4.56 works ok with same settings.

thanks

Edited Sunday at 12:31 PM2 days by pegeka

1 hour ago, pegeka said:

has something changed?

A lot of things have changed. Can you explain a bit more what problem you are seeing and how this can be tested? What "FIPs" are we talking about exactly? What is a "Touch Mini"?

Edited Sunday at 01:17 PM2 days by Lorby_SI

I use Behringer xtouch mini as an interface / input device to operate msfs.

https://flightsim.to/addon/38162/x-touch-mini-gauge-for-use-with-aao-axis-and-ohs

I use the option to show the gauge for the xtouch mini that are implemented in your software to show the function

of the different buttons on mij screen or on my ipad via web connection.

Now with the latest update I do see the gauges, but they stay empty, where normally every button shows it's function.

Since the new update, 4.57 b21 I Cannot import any profiles to use with streamdeck either if i change a function in the plane it shows i have changed it on my streamdeck but when i want to use the streamdeck to apply a change nothing happens, its like there is no communication from the streamdeck to the plane any chance of providing a version where its possible to revert back?

Edited Sunday at 03:19 PM2 days by Crazyfool
Updated version

8 minutes ago, pegeka said:

I use Behringer xtouch mini as an interface / input device to operate msfs.

https://flightsim.to/addon/38162/x-touch-mini-gauge-for-use-with-aao-axis-and-ohs

I use the option to show the gauge for the xtouch mini that are implemented in your software to show the function

of the different buttons on mij screen or on my ipad via web connection.

Now with the latest update I do see the gauges, but they stay empty, where normally every button shows it's function.

I'm sorry, but "Lorby" didn't make that gauge and I don't know much about it.

I will forward your report to the actual author, who is also a tester for AAO. The thing is that he did test his gauge with the 4.58 just recently and we made sure that it worked...

Just now, Crazyfool said:

Since the new update, Cannot import any profiles to use with streamdeck either if i change a function in the plane it shows i have changed it on my streamdeck but when i want to use the streamdeck to apply a change nothing happens, its like there is no communication from the streamdeck to the plane any chance of providing a version where its possible to revert back?

Which part of the "profiles" would that be specifically? AAO has nothing to do with the import process into the Elgato software - are we talking about the scripts? What does "cannot import" mean exactly? Are you getting an error message? Are you importing new assets or updating existing ones?

Here is what is known at the moment: since the beginning of the scripting engine in AAO, it was forbidden to use the "-" character in script group names (and also in script names and in LVar names). Apparently, some authors seem to have ignored that rule - because the new AAO version now enforces this rule, and that causes scripts with invalid names to stop working.

Is that the case here? We are thinking about releasing a 4.58 which will allow those scripts again, but I need to know if we are talking about the same problem here.

Edited Sunday at 03:26 PM2 days by Lorby_SI

It is when I try to manage/add an automated script in the app it does not load/respond to my request.

Maybe there is a bottleneck?

These scripts do have a "-" in the name so maybe that's the culprit....

Edited Sunday at 03:29 PM2 days by pegeka

1 minute ago, Lorby_SI said:

What part of the "profiles" would that be specifically? AAO has nothing to do with the import process into the Elgato software - are we talking about the scripts? What does "cannot import" mean exactly? Are you getting an error message? Are you importing new assets or updating existing ones?

Here is what is known at the moment: since the beginning of the scripting engine in AAO, it was forbidden to use the "-" character in script group names (and also in script names and in LVar names). Apparently, some authors seem to have ignored that rule - because the new AAO version now enforces this rule, and that causes scripts with invalid names to stop working.

Is that the case here? We are thinking about releasing a 4.58 which will allow those scripts again, but I need to know if we are talking about the same problem here.

appreciate the quick response, SO i had to do a fresh install of the sim and as you can imagine profiles due to fresh pc, I imported scripts for some of the aircraft that i fly regularly but long haulers like the a380 a340 etc i hadnt, upon doing the a340 i realised that the import script want saving and when i tried to import the script again i didnt get the usual overwrite scripts popup.

so This might indeed be a vs- issue as the only profiles that i generally use are guenseli but the ini a340 only has one from another user whom uses _

On a last note if and when u do release teh 4.58 version whats the lead time in Say just flight updateing thier store page/ customer section as that is my purchjase store.

Just now, Crazyfool said:

appreciate the quick response, SO i had to do a fresh install of the sim and as you can imagine profiles due to fresh pc, I imported scripts for some of the aircraft that i fly regularly but long haulers like the a380 a340 etc i hadnt, upon doing the a340 i realised that the import script want saving and when i tried to import the script again i didnt get the usual overwrite scripts popup.

so This might indeed be a vs- issue as the only profiles that i generally use are guenseli but the ini a340 only has one from another user whom uses _

On a last note if and when u do release teh 4.58 version whats the lead time in Say just flight updateing thier store page/ customer section as that is my purchjase store.

Is it only the A340 that isn't working then? Script group called "AS_A340-600", made by "Chris_PU"? Guenseli said that he hasn't been using the "-" for a while, so his scripts should be working.

JustFlight is pretty quick these days - at least during normal office hours. They don't deploy software on weekends or at night (they are based in Engand I think).

Edited Sunday at 03:50 PM2 days by Lorby_SI

19 minutes ago, pegeka said:

It is when I try to manage/add an automated script in the app it does not load/respond to my request.

Maybe there is a bottleneck?

These scripts do have a "-" in the name so maybe that's the culprit....

I think you pointed me in the right direction, I seems to work ok now after some renaming of scripts :)

Thanks for your quick response!

And thanks again for a great tool I use everytime I 'fly' :)

Just now, pegeka said:

I think you pointed me in the right direction, I seems to work ok now after some renaming of scripts :)

Thanks for your quick response!

And thanks again for a great tool I use everytime I 'fly' :)

So those were your scripts? Not part of the gauge sources? Is there something that Funatic should be doing?

Ì made it official now:

"Bug" notice about AAO 4.57 not executing certain scripts - AxisAndOhs Support - The AVSIM Community

Edited Sunday at 03:53 PM2 days by Lorby_SI

Yes I made a script group for my 'INI' files, just for my own use, with a wrong name convention.

I've never published any scripts.

4 hours ago, pegeka said:

I think you pointed me in the right direction, I seems to work ok now after some renaming of scripts :)

Thanks for your quick response!

And thanks again for a great tool I use everytime I 'fly' :)

Hi Pegeka,

did I get it right - everything with XTouch gauge is working now?

I did understand that the init scripts did have - in the scripts group name - in that case they will not have fired and the gauge would not initialize.

Please let me know if there is something I have to look into or if everything is just fine now.

Thank you!

12 hours ago, Funatic said:

did I get it right - everything with XTouch gauge is working now?

I did understand that the init scripts did have - in the scripts group name - in that case they will not have fired and the gauge would not initialize.

Hi Funatic,

Yes everything is working now, fault was on my side in naming the script group with a -,

after replacing the - with _ all went smooth sailing again :)

Thanks for response en thanks for great interface with XTouch gauge, daily user here.