JJBZ53

Yes "in the sim" is what I guessed as well. Dead Axis is Helicopter cyclic(2) and collective. Also throttle. Just wondered if anyone else sees this. I will move the Axis controls to Sim control page to see if different.

Using 4.10.b51 with MSFS2020. In recent weeks I see an issue after I return to the main menu and start a new flight and sometimes when restart a flight. The mapped axis still move on the AAO app, but not in the sim. Buttons are working OK, just axis are dead in the sim. Restarting the app does not fix. The only way to fix is to exit MSFS from main menu and start again. The problem is never seen on the first flight. It does not happen on every second flight. But often enough to be time-waste. Mostly I am flying helicopters recently. Seen this issue using several different helicopter models/makers. Nothing unusual about the axis mapping. The axis are on VKB joystick and Honeycomb Bravo. There are no other simconnect applications running. I have generally removed lorbysi-content-fippanel as I do not use its features. I could test some fixed wings again if you think it would provide data. Jeff

In the watch simulator events window I sometimes see numeric #code for recently-added events. Would it be possible to update this window to show text these newer events? For example, for (>K:HELICOPTER_THROTTLE_SET) the viewer shows (>K:#67529). The event is of course available in the event search, only the viewer is not up to date. Is the numeric code defined by Microsoft in a list somewhere or by AAO in internal simconnect event mapping call?

When watching simconnect events on default airplanes without WASM, all the events mapped from the sim controls page or the external AAO mapping buttons are shown. But on some creator airplanes like Arrow, not all control-generated events appear in the Events window. My theory is these particular events are taken over by WASM code, replaced, and rendered invisible to both the AAO window and Sim core. 1. Do you know if this is likely explanation for the disappearing events? 2. If simconnect event types and data can be modified by WASM, does the sim, or AAO, make sure that the AAO listener always sees the changes made by WASM - the AAO is at the end of the event client list after WASM? Thanks again for AAO. I use the debug windows for hours almost every day to see inside the sim.

@gboz The sim default AXIS events do not work on this airplane. The event code is in the xml but the scaling is broken. Instead I left the axis range to be default -16384 to 16384 and called this script from the Honeycomb axis. There are two types of aircraft with Turbo and non differentiated by the creator variable. Turbo range is 0 to 100, non-turbo is 0 to 16384 (L:Bonanza-MixtureAll)·16384·+·2·/·s0·(L:BKSQ_Turbocharged,·bool)· if{·l0·163.84·/·(>L:BKSQ_MixtureLeverPosition_1,·percent)·}· els{·l0·(>K:MIXTURE1_SET)·}

you are correct. i am such a long time user, i only see what i expect, not what is new. i will use this

When flying, if you hit escape, one of the options is RESTART. I had a guess that the problem was caused by moving controls during restart but I just did 5 tests and and did not reproduce. This is occasional lockup event requiring sim exit but I have not found procedure to reproduce. The USB device is still connected and works fine in the axis windows. Disconnect/reconnect has never fixed. Exit/run AAO does not fix. That is why I think the hang is in sim core or connector. The next time it occurs I will check the log.

It would help me a lot if the variables in the simvar watch window were saved when AAO is closed and the list were restored the next time AAO is opened. A checkbox or option could control this behavior.

For the past month or so I have noticed controls mapped with AAO not working after flight restart. Typical is axis. AAO is connected and the axis moves in the AAO windows but not in the plane. Nothing fixes except exit sim and restart. Exit AAO is not enough when stuck. This is restart to runway and I have a habit of placing the controls in the default state (parking brake, throttle, etc) while sim is restarting. No sense zooming down the runway before I am ready. So I have a hunch that AAO is sending sim events for my movements while flight is reloading and the communication is getting error and not recovered. Probably on the sim side or the connector in community. If I remember, I will close AAO before restart flight but I wondered if AAO can recognize the state "restart in progress"? Maybe not because the airplane does not change.

Scripts do not run when assigned to the Honeycomb Alpha switch. But when assigned to a Button-Box switch they work correctly. Maybe something about the context when Alpha switch change is detected?

Works correctly with the script editing 'Test' button but not when the script is assigned to a button. I removed the in-game mappings for this device just to be sure, but not working.

Never mind - works without the () enclosing thanks

Would this be the correct syntax? No example in the manual. (SIMPROC:)·4·(>A:BUS·LOOKUP·INDEX,·Number)·(A:BUS·CONNECTION·ON:3,·Bool)·0·==·if{·3·4·(>K:2:ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE)·} It always toggles and debug does not change.

If I have most device switch and axis items in the In-Game control menu but want to remap a couple switches to a AAO script is it OK to share the device between In-game control map and AAO? Obviously I would not use these AAO-assigned switches in the in-game control mapping.

I am looking to map Avionics 1 and 2 on Milviz Porter. the behavior dialog has no direct SIM Events listed only has 3 4 (>K:2:ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE) I copied this rpn to a script and script works - does toggle. But I want to use the 2-position switch on the Alpha yoke. Also in Behavior Window, the tooltip TT_VALUE shows 4·(>A:BUS·LOOKUP·INDEX,·Number)·(A:BUS·CONNECTION·ON:3,·Bool)·if{·'On' } els{ 'Off'} And the modern tooltip correctly shows on or off. But when I copy this into script the A:BUS CONNECTION always returns 0. Does AAO correctly support indexed SIM variables? Is the syntax not the same as SIM? The is the script for the 'on' switch 4·(>A:BUS·LOOKUP·INDEX,·Number)·(WAIT:500)·(A:BUS·CONNECTION·ON:3,·Bool)·if{·quit·}·els{·1·(>K:Porter-Avionics1_toggle)} using my script with above. The debug view on test script always shows 0 after WAIT I also tried adding 1 == before the if{