djxmdjxm

I reposted in the better thread. Ignore this one.

Great, just downloaded it! I can't seem to get the SimBrief integration going. --------------------------- mce.exe --------------------------- Invalid Simbrief ID number. You may not be logged into your account or no flight plan exists. --------------------------- OK --------------------------- I have it active in all my other add-ons. Isn't it the 5-digit code (e.g. pilot id)?

Great, that's looks promising. Looking forward to seeing it!

Hi Gerald, Simbrief info I'd like to be able to fetch from my PM: Block Fuel Est. Zero Fuel weight (ZFW) (optionally: TOW and LAW) Est. #PAX, Est. Cargo (t), est. payload (t) AVG wind component Cost Index planned gate departure time planned (initial) cruise flight level (if no steps) I might come up with more as soon as I find some time to fly again. I haven't had time for months 😕 Thanks for reading!

Wonderful - let me know - will test

Hi Gerald, do you have any updates regaring the reusability of existing A320 implementation for Fenxi A320? Would love to have my PM back soon! 🙂 Thanks!

Perfect! a lot of the work for Fs-Labs, Aerosoft, and or Toliss might be reusable here...

The elephant in the room is the Fenix A320. Would love to see support - I am switching now from FBW. Thanks for your ongoing upgrades!

Okay, WASM is disabled by default in FSUIPC. After enabling it explicitly in the FSUIPC UI ECAM pages work now. Great! However, the autobrake functions still do not work.

Thanks for the update. I assume the file should sit here: "..\Community\fsuipc-lvar-module\modules\FSUIPC7_WASM.wasm". Correct? BTW, do I have to explicitly "ENABLE WASM" in FSUIPC? The FSUIPC UI menu offers the option "Add-ons" > "WASM" > "Enable".

Maybe this A32NX FSUIPC template file can help: a32nx/flybywire-aircraft-a320-neo.evt at master · flybywiresim/a32nx · GitHub (it was referenced on this page: FlyByWire A32NX API - FlyByWire Simulations Documentation)

The following document by FBW describes all the accessible functions: Flight Deck A32NX API - FlyByWire Simulations Documentation also the "custom LVARs" (many others are to be accessed via simConnect). However, they have names (e.G. "A32NX_AUTOBRAKES_ARMED_MODE_SET") that I cannot find in the A320.hvar file supplied with the MCE patch. Do I need to add the A32NX function names here? Can I map them somewhere within MCE? Haven't found THAT file yet. Let me know if I can help you with something here. Thanks!

Thanks. I actually did update the lvar files when installing your patch in the first place. I'll have a look at them.

Here my test results. Thanks for your efforts! Landing lights: "on" --> on "off" --> retract "retract" --> retract I guess, that's fine. Taxi lights: Work just fine Nav lights (Mode 1 apparently not yet supported by FBW): "on" --> 2 "2" --> 2 "off" --> off Works! Emergency lights: Work just fine Wipers: "on" --> fast "fast" --> fast "slow" --> fast "off" --> off That's fine. This might get more interesting as soon as MSFS supports physical wiper effects. ECAM: Requesting pages has worked once three weeks ago. But never again. I always get a positive response fom FO but action is not performed. Autobrake: Positive response from FO - but no action.

Thanks, will test later this week! I think I do own the full-fledged version.

Hi again, just a hopefully simple request: WHEN running a voxscript flow. WHEN there is an unrecognised command. AS IS: MCE shows error message in top left corner of the screen that a command was not recognised. Requests: MCE shows error message in top left corner of the screen that a command was not recognised. AND it shows which exact command was not recognised. For some reason I can say "set parking brake" - but I can not use it in a voxscript. "engage parking brake" seems to work though. That makes identifying the culprit command a little tedious sometimes. Thanks for looking into it. Or most probably you already have a working solution.

Thanks a lot! Will implement your input. Regarding item 1) I normally just load one airplane during an msfs session. So the ECAM button issue might have some other cause.

Hi again. Some more observations regarding the FBW A32NX (still experimental): 1) The ECAM pushbuttons only worked for once where my PM was able to to cycle happily through the pages. The other times PM confirms but nothing happens regardless of what button press you request. 2) The flight control check seems to ignore rudder (I have separated tiller and rudder) 3) The Airbus specific callouts work wonderfully and I'm on my way to getting it pretty accurate. Thanks for supporting the aircraft that well, 4) Question: Is it possible for the PM to announce "ALT *"? 5) Question: Is there a way to get the Airbus split checklist logic into MCE ('down to the line' vs 'below the line'). I have currently built separate lists (e. g. 'before takeoff down to the line check' and 'before takeoff below the line check'). Is there any way to get it closer to real Airbus phraseology? 6) Suggestion: Instead of having my PM nagging endlessly during a checklist item would it be possible for the PM to challenge ONCE and then afterwards just let it go? 7) Last question: Is there a switch in the config to get rid of Mark, Paul, Rob, and all the other ramp managers? I use Pushback toolbar and I am happy with those voices. Thanks again and thanks for some feedback! Best regards Christopher

Hi everyone, thanks to FS++ for this great piece of work that I now could get to work decently with MSFS (a reinstall with both main install and patch helped to detect the correct aircraft). I have noticed a few few glitches with the Flybywire A32NX (experimental build (!)): The following switches do not work for me: "retract landing lights" doesn't switch "nose switch to takeoff" (T.O.) - not recognized - cannot switch to takeoff setting at all dome light dim / brt / off - does not do anything emergency exit lights is reversed (ON is OFF | OFF is ON) NAV & LOGO lights settings "2", "1" and "OFF" (turning OFF doesn't work) WIPER is reversed (FAST is SLOW | SLOW is FAST) If this is normal with the experimental build then ignore me. But it actually works quite well. I'm running MCE on v2.9.61 Thanks for looking into it!

In MSFS the CJ4 with the Working Title mod is currently one of the most advanced and flyable aircraft. It's also pretty stable now. I would love to see it supported as much as possible. Thanks generally for your work!

Hi all, I still have this problem (tested on TBM930). When I say "set altimeter to 3012" my FO just scrolls all the way down to 2900 with the obvious implications to altitude. Does anyone else have this problem? Thanks!

(MSFS2020 1.9.5, MCE latest x.x.80, Asobo TBM930 unmodded) When asking FO to set the altimeter he/she just sets it to the lowest possible value - I think it's 2900.