at least two carenados: Piper and Ovation
OK, thanks. Too bad, the C172 classic is encrypted, and I donât have the Carenados.
The Arrows from Justflight also use the 530.
but this tipp from simracetube worked for me
SDK docs was updated with new SimVars, for example camera controls
Could be possible to do some cool stuff with it. Havenât tested yet if they actually work though.
Thanks for the link. Reading is working:
(A:CAMERA·VIEW·TYPE·AND·INDEX·MAX:4,·Number)·(>L:TEST)
Setting works with SIMPROC:
First:
SIMPROC:2·(>A:CAMERA·VIEW·TYPE·AND·INDEX:0,·Number)
This selects CAMERA_VIEW_TYPE_AND_INDEX 2
And then:
SIMPROC:1·(>A:CAMERA·VIEW·TYPE·AND·INDEX:1,·Number)
This selects the second Camera in this type.
I was using the latest version of AAO last night. Usually any changes seem to be saved at the time of making them. I usually do several scripts before saving the template and exporting it.
Anyway AAO just shutdown (paid version). About 20 scripts were lost and the template had reverted to a much earlier version.
Seems good practice to save the template and export it regularly as a backup.
I have all events as an RPN script so that I can set any toggle to a short (ON) or long (OFF) push. At the same time set the light on the x-touch mini to the correct status.
After the crash some of the scripts were kept but not as RPN scripts they just appeared in the list of assigned buttons. ie
Toggle-lights rather than C172 toggle-lights with a linked RPN script in the C172 group.
These are the error codes, I think.
25/10/2021 20:15:07.478 : SH: Exception received: 3 from send id 4612 errloc 1
25/10/2021 20:15:07.478 : SH: Exception received: 7 from send id 4613 errloc 2
No. They are saved when you shut down the app. The database file can be quite large, and forcing the user to wait for a bit every time he makes a change didnât seem like a good idea.
If you are creating scripts, it is probably a good strategy to save the database manually every now and then (Tools menu). Just in case you manage to create a critical error that shoots down the app.
No, sorry, that has nothing to do with anything. These are forced exceptions that AAO creates on purpose (which is why they happen at exactly the same timestamp).
OK, thanks. Looks like this will be a larger update of the MSFS part for AAO 2.22.
Too bad that they didnât bring back the 6DOF methods in the SimConnect API, but it is great step in the right direction IMHO.
That is because AAO doesnât know them yet.
What you can do is to import them as custom variables from a CSV file.
For example, I used Notepad++ to create a file \Documents\camvarstest.csv with this content:
A,CAMERA VIEW TYPE AND INDEX:0,Enum
A,CAMERA VIEW TYPE AND INDEX:1,Number
A,CAMERA REQUEST ACTION,Enum
A,CAMERA STATE,Enum
A,CAMERA SUBSTATE,Enum
A,CAMERA VIEW TYPE AND INDEX MAX:index,Number
A,GAMEPLAY CAMERA FOCUS,Number
Then I went to âScripting->Import events and variables from fileâ and loaded them to a new group âCameraNewâ. Then writing works without SIMPROC.
1 Like
Thanks for such a quick and detailed reply. Good advice to save the database. Will check that out next time Iâm on. I have been exporting templates as backups today.
This is an amazing tool. So easy to use.
Hi,
So Iâve been looking for a solution for the landing and taxi light mappings for the FBW A32NX. The Simconnect events are unusual for this because the lights have 3-way switches. I came across some steps that FBW published, instructing to do the followingâŠ
For the left landing lightâŠ
Set LIGHT_LANDING_2 to 0 (Sets switch to ON)
Set LANDING_2_RETRACTED to 0 (extends the landing light)
Delay of 8-10 seconds to simulate the time it takes to extend the lights)
Set CIRCUIT SWITCH ON:18 to 1 (turns on the actual light)
There are similar steps for the right landing light, and some additional ones for the nose light using CIRCUIT SWITCH ON
Does anyone know if or how this can be accomplished in AAO, or if there is a script somewhere that I can import. As you can probably tell, my experience in writing scripts is next to none. Thanks!
I tried, but it doesnât work with the T16000M.
Any other idea.
I found an issue with the following script
âTESTâ·(>WINVAR:AAOTEST)
When running this in repeat mode, every second in my test, I cannot scroll in the explorer. It always goes to the top.
Iâm using such a script to set a winvar to a bitmask which then is used by a small external programm to set the LEDs of the honeycomb bravo.
AAO is hardware agnostic. Something must be interfering in the simulator itself.
Iâm sorry, but there is nothing I can do. This code is calling native Windows functionality, there is not a bit that I could do differently.
Isnât that possible with the AAO HID bridge too? I donât really know, I am just asking.
1 Like
OK, so far it only happens with the explorer, didnât notice it anywhere else.
As with the Bravo LEDs, yeah it probably would be possible with the bridge.
I just wanted to do a little exercise with the HidLibrary 
I have 2 Behringer X-touch Mini MIDI controllers connected to my sim. They are identical. Sometimes AAO discovers both of them, sometimes just one, sometimes it even discovers them the other way round.
Is there a way to reliably discover each of the controllers?
And use just one of them when flying a simpler plane?
How AAO discovers and identifies such identical devices? Via the order of connecting the controllers? Or must the controlles be consistently connected always to the same USB port each?
Windows (or your MIDI driver or management software) assigns a numerical ID to them, and that is what AAO reads. AAO doesnât actually care about what device it is or how it is connected, it relies only on that ID. How or why a device gets a specific ID is out of my control. MIDI is a message based protocol to transmit musical notes. It doesnât contain any device information.
If your computer keeps changing those IDs, maybe it would be possible to use a MIDI Mapper software of some kind instead, and route the XTs through that. So all messages are coming to AAO with the same ID (= the MIDI ID of the mapper software). Then you could set the XTs up to send on different channels.
I was refferencing to an other post about the ASCRJ 700 spoilers not working. AAO works very well, and I use it with Streamdeck. profiles.
But I can make work the spoilers with my T16000.