Behringer -> AAO -> G1000 NXI

• Clicking FLC in FS2020 generates 0 (>K:AP_SPD_VAR_SET) according to Event Simulator Monitor
• I tried several variants of this, both directly and via script, and could not get this to work. 

I have successfully implemented two dozens other commands, most work even if some only with Html-commands.

Any idea?

 

Edited February 8, 20224 yr by dmenne
Corrected font

version 2.25, b14

Assigned Axis, Curve (Example: Elevator trim)

When you make the curve more convex, at a certain point the program crashes reproducibly

Edited February 15, 20224 yr by dmenne
typo

On 2/8/2022 at 7:56 PM, dmenne said:

Behringer -> AAO -> G1000 NXI

• Clicking FLC in FS2020 generates 0 (>K:AP_SPD_VAR_SET) according to Event Simulator Monitor
• I tried several variants of this, both directly and via script, and could not get this to work. 

I have successfully implemented two dozens other commands, most work even if some only with Html-commands.

Any idea?

 

No idea what the FLC trigger is on the NXI, but the event that you see is obviously only part of what is happening in the background. The logic that is running after you press the button will do many things, and sending that event is only one of them. You need to find the actual initial trigger (HVar or BVar?)

1 hour ago, dmenne said:

version 2.25, b14

Assigned Axis, Curve (Example: Elevator trim)

When you make the curve more convex, at a certain point the program crashes reproducibly

That is true. Very weird. Happens only for some events or axis, not for all of them, so it might be an old issue actually.

I will put it on the list for the 2.26

Edited February 15, 20224 yr by Lorby_SI

1 hour ago, dmenne said:

version 2.25, b14

Assigned Axis, Curve (Example: Elevator trim)

When you make the curve more convex, at a certain point the program crashes reproducibly

Will be fixed in 2.26

I seem to have a problem with elevator trim controls.

Assigned through the default sim interface it works fine

In AAO, use of ELEV_TRIM_UP and DN assigned to joystick buttons doesn't cause any movement in elevator trim in the sim, though AAO does recognise the joystick buttons have been depressed

14 minutes ago, kevinfirth said:

I seem to have a problem with elevator trim controls.

Assigned through the default sim interface it works fine

In AAO, use of ELEV_TRIM_UP and DN assigned to joystick buttons doesn't cause any movement in elevator trim in the sim, though AAO does recognise the joystick buttons have been depressed

What simulator and aircraft? Repeat enabled?

1 hour ago, Lorby_SI said:

What simulator and aircraft? Repeat enabled?

MSFS, sorry can’t name the aircraft, it’s in beta.  Developer confirms Elevator trim is using Asobo required templates.  Yes repeat enabled

20 minutes ago, kevinfirth said:

MSFS, sorry can’t name the aircraft, it’s in beta.  Developer confirms Elevator trim is using Asobo required templates.  Yes repeat enabled

What I need to know is, if it happens with all aircraft or only a specific one. There have been no other reports, and I can't test it at the moment, just gathering information.

"Asobo required templates" says nothing. That could be default events, but it could be BVars too. 

6 minutes ago, Lorby_SI said:

What I need to know is, if it happens with all aircraft or only a specific one. There have been no other reports, and I can't test it at the moment, just gathering information.

"Asobo required templates" says nothing. That could be default events, but it could be BVars too. 

Ok thanks Oliver, will check that and get back to you 👍

59 minutes ago, Lorby_SI said:

What I need to know is, if it happens with all aircraft or only a specific one. There have been no other reports, and I can't test it at the moment, just gathering information.

"Asobo required templates" says nothing. That could be default events, but it could be BVars too. 

Oliver,

It is using ASOBO_TRIM elevator default templates.. werever Asobo uses for handling the event that is what happens on this aircraft trim control.. the trim works with normal joiystic, keyboard and axix assigments.

It is my upcoming air-plane for MSFS btw :)

S.

3 hours ago, Lorby_SI said:

What I need to know is, if it happens with all aircraft or only a specific one. There have been no other reports, and I can't test it at the moment, just gathering information.

"Asobo required templates" says nothing. That could be default events, but it could be BVars too. 

All working ok now, not sure what was going on there!  Thankyou @simbol@Lorby_SI

Edited February 16, 20224 yr by kevinfirth

Noticing with the Saitek radio plugin i cannot change ADF frequencies in MSFS Bendix/King KR87 TSO (e.g. PMDG DC-6) or Twin Otter MSFS Bendix/King KR-87 anymore.The frequencies are display on the hardware but MSFS with the MSFS Bendix/King KR87 not accepting the hardware setted frequencies.

"Saitek panels are enabled" and WEB API Working as streamdeck and other functions with saitek radio panel are working with no problem.

Thanks for an advice how to fix, as it worked before.

 

8 hours ago, Andi68 said:

Noticing with the Saitek radio plugin

What is a "Saitek radio plugin" ? What does "as it worked before" mean, before what exactly? What did you use "before" and what changed that to "after"?

By default AAO uses the default simulator events to change frequencies. But there is no rule that those have to affect the actual instrument in the aircraft, the developers can do whatever they want in that regard.

Latest AAO update MSFS
Aerosoft CRJ
In the past all that I have done is update.  No issues with template being used

Today after update, MFG Crosswind pedals are recognized by AAO, the slider moves but no rudder or front wheel movement at all.  Had to remap the brakes and those started working.  The only way to fix the rudder was revert to last revision.  There appears to be changes to the options when selecting an axis now.  Not sure if that has anything to do with it.  However, for now back to v 2.22 b43 is the only way to get the rudder.