Im new to AnO, so im sure im doing some thing very wrong, but I cannot get a mapping to the fenix a320 fcu working (also tried the iniBuilds and similar issue)

note: says, im connected and throttle axis is working via AnO

so im trying to use

B:FNX320_INPUT_KNOB_PUSHPULL_E_FCU_ALTITUDE_KNOB_Inc

and nothing happends

I've tried B var, and also using RPN

1 (>B:FNX320_INPUT_KNOB_PUSHPULL_E_FCU_ALTITUDE_KNOB_Inc)

still nothing...

I even created a scripted and tried to run the same RPN, still nothing...

the odd thing is, if I use the same RPN in PilotsDeck , it works.
though, even there oddly, it doesn't work as a bvar? (pretty sure it used too?!)

other things work e.g. parking brake... but none of these bvars (which are being detected) for the FCU.
I thought i might be the fenix (not sure why), but i tried the same thing (different bvars obviously), on the msfs24 inibuilds variant, same thing...

Im using latest release of MSFS24 and demo version of AnO (as testing before purchase)
bug in MSFS24? or something odd with simconnct?

I tried, so many things, and I cannot think what Ive missed...
(ive used lvars / bvars /rpn etc before in things like PD, but its been a while ;))

thanks for any pointers.

ps. read LVARs also fails, saying unable to connect, even though sim is connected.

ps. read LVARs also fails, saying unable to connect, even though sim is connected.

ok, seems this is only if I start flight - if I do when sim is first started it works fine - so I guess sim connect is ok.

(only) LVar collection and BVars rely on the AAO Community package "lorbysi-content-hooks". Make sure that the package is present and active in your Community folder.

Instead of BVars try using their parent, the IEs. Check the "MSFS IEs" tab on the AAO event selection dialog. BVars are the "bindings" of an IE, which in most cases can be used directly by supplying the correct value (with IEs it is not just 1 or 0, it can be anything).

Edited August 2Aug 2 by Lorby_SI

thanks for your help.. yeah, it was all correct...

but it appears I had something really odd going on with FSUIPC 7.. perhaps an old version?

I updated FSUIPC, and it all started working...
then I decided, well , I don't really need FSUIPC, an uninstalled it - and it continued to work...

thanks for your prompt help, its looking really good...
been integrating not on the A320, but also writing some flowpro scripts, and then connecting those up via AAO too :)
great stuff !