SayIntentions.AI

Quote from jpx

Hi,

Is it any way to connect Aerofly with market ATC app like SayIntensions.AI ?

Thanks in advance,

The owners of it made it compatable with the Microsoft flight sims not Aerofly it’s not like you can stick in a Jackhammer into a small bolt

SayIntentions can work with any flight sim that can output telemetry

We need to check the API specifications, thanks for sharing!

Hi Armitage , take a look at the video!

Here there are the specifications:

And these are the input variables, a lot more than what we can get from the UDP stream. I think it would be requires an AFS4 DLL to get the information, or better the devs could provide us a way we could get it

https://portal.sayintentions.ai/simapi/v1/input_variables.txt

Will do some further research.

Well, this looks like the DLL is the only way to go. But this seems to require IPACS to supply a example source code.

Or we would need an improved UDP output, which in turn would be converted to the required API files. But this also requires the support of IPACS.

Maybe we can try a simple version with the UDP adapter of yours, Jugac64 ? But obviously without all parameters the integration would be lacking.

If the DLL or UDP approach would be possible, the actual implementation appears to be rather simple. Writing and reading JSON files is trivial nowadays.

This also touches some information only known to AFS, like the magnetic declination (for which Aerifly has its own model), and aircraft capabilities.

Yesterday I asked in the Discord channel what the minimum input requirements are to successfully integrate with the system.

They told me that the "minimum required" can vary quite a bit depending on which features you're willing to give up. For example, if you don’t need the COM2 radios to work, then there’s no need to send COM2 frequency data. Zulu time isn’t strictly necessary either—it's mostly used so controllers can say “good morning” or “good evening” appropriately. Even wind speed and direction can be omitted if you're fine with the system just using METAR data, even if that information might be outdated or inaccurate.

They also pointed out that there are 25 required variables and 13 optional ones, and there’s documentation explaining what happens if you leave out the optional ones. Lastly, if any of the required variables are causing issues, they're open to discussing possible workarounds.

They updated the input list to display what input is required:

https://portal.sayintentions.ai/simapi/v1/input_variables.txt

I hope IPACS can help us with this, it would be very easy to do this integration if we can get the required variables

Just want to add that SayIntentions may be the most advanced AI ATC platform in the market, it would be awesome we could use it with Aerofly FS4. Most of us that do flight simulation in PC/MAC use all the flight sims, so having a SayIntentions subscription is not strange, since we can use it in all the sims (like the Navigraph subscription).

Excellent work, Jugac64 . This was my main question. Knowing the required from the optional variables will speed up the integration.

@IPACS : Is there any way to get a working DLL example to get us started? Sayintenions.ai would get our ATC wishes from zero to hero with a limited investment.

Awesome!!!

Today I was working with Brian from SayIntentions Discord channel, and he helped me with this. With Claude 3.7, I modified the UDP apps to fullfill the required integration specifications.

With the DLL, a developer could do a very complete integration, I hope Armitage takes the mission!

Here you can see the Python code of the new plugin:

Aerofly FS4 basic integration with SayIntentions.AI via UDP Foreflight streaming data

Aerofly FS4 basic integration with SayIntentions.AI via UDP Foreflight streaming data - aerofly-sayintentions-adapter-v4.py

gist.github.com

And here you can see it working. Brian told me that it was working with SayIntentions app, but I still don't know how to use it, so I will have to study it.

But most important, we now have some basic integration with our beloved Aerofly FS4. When I really see it working and I can talk with ATC, I will publish an EXE file.

As soon as the example DLL is available, Claude and I will take a look. So long I will give your python script a try when I find the time, Jugac64 . Thank you for your efforts.

If you continue on this path, you could integrate all your UDP ideas into one single app, so your moving map could come with some checkboxes to activate Shirley and Sayintentions.ai. The one and only UDP Middleware.

Fantastic project!
Just one question, Is there a technical possibility to port it on other platforms?

I think I have read something about UDP handling on MacOS causing issues.

I can support with some small coding and beta testing.

I do not know if there is something similar to DLLs on Mac OSX and Linux. But if this is the case, the world is ours! (Well, but for our mobile friends)

Anyhow, I will make the source code of everything I will be building public, for others to learn and improve.

As soon as we can build DLLs, we can built any type of export API, be it a file writer / reader, UDP server / client, web socket, or even stuff like ACARS clients or clients to rebroadcast simulation parameters to some internet service.

Thank you Armitage and SageMage ! We are close to have ATC for Aerofly FS4.

I will try to add buttons to the interface so we can change the radios from there, and other required interactions that SayIntentions may need.

Yesterday I watched some SayIntentions videos and tried to use it.

It seems that one of the most important interactions is selecting the radio in SayIntentions app, depending on your flight stage (tower, etc). Trying it in another simulator, I saw that when you select the radio in the app, it changed to selected radio in the sim.

So this is very important to be included in the DLL.

I think we can add this interaction in the UDP app for now, and SayIntentions will think that AFS4 is changing the radios as it expects.

It is very easy to setup some keystrokes to change the radio, just if we want to match the ATC selected radio with the display radio in the airplane:

Quote from Jugac64

Yesterday I watched some SayIntentions videos and tried to use it.

It seems that one of the most important interactions is selecting the radio in SayIntentions app, depending on your flight stage (tower, etc). Trying it in another simulator, I saw that when you select the radio in the app, it changed to selected radio in the sim.

So this is very important to be included in the DLL.

I think we can add this interaction in the UDP app for now, and SayIntentions will think that AFS4 is changing the radios as it expects.

this is extremely impressive. Would SayIntentions work in VR as well or just desktop?

Quote from Armitage

If you continue on this path, you could integrate all your UDP ideas into one single app, so your moving map could come with some checkboxes to activate Shirley and Sayintentions.ai. The bug and friendly UDP Middleware.

Thanks Armitage , good idea! I will reserve the name just in case I try to do it

Hi Armitage , if it is possible can you recheck the inputs and outputs variables lists, and comment if you have some suggestions about them? Some of them I will convert them in buttons, some values must be estimated, etc. the idea is to provide all the required information to the input json file. For example, the aircrafts type must be provided, and this could be a list selector to choose before starting.