Most of the commonly reported issues and questions are answered in the Frequently Asked Questions (FAQ) option under the Support menu of this website.
*** PLEASE NOTE ***
Your forum account is not the same as the account used in the shop. They are completely separate accounts.
Your forum account is not the same as the account used in the shop. They are completely separate accounts.
1st December: A new version of the GoFlight Interface Tool for MSFS is now available.
12th November: A new version of the GoFlight Interface Tool for X-Plane is now available.
6th June: A new version of Virtual Flight Sim Hardware is now available (huge update)
21st November: A new version of the GoFlight Interface Tool for FSX/FSXSE/P3D is now available.
MCPpro for AXE
As the title states I am looking to see if anyone has made up any Bespoke commands for the Airbus X extended. If not I can try and then put them up for use..
Terry
Terry
Answers
Hi Terry,
I've got a fair amount of stuff working for the AXE on the older GF-MCP (not the MCP-Pro, but it's probably comparable and might be a useful starting point for conversion). Currently altitude, heading, IAS and vertical speed selection are all working from the rotaries, and the displays show levels, headings, speeds, etc correctly (in terms of the right numbers).
Most of the (sensibly-assignable) buttons work reasonably correctly, but I'm currently having a few difficulties handling the 'push/pull' nature of the Airbus; obviously, the lack of pull switches on the MCPs makes this tricky! I've managed to make the 'HOLD' buttons work as push-pull toggles (one push sets the AXE to 'managed dot mode' and another press sets it to 'selected no-dot mode') but there are times, if you press them in very quick succession, where the button-lamp doesn't match the mode (I'm trying to use 'lamp on=managed mode'). I think the problem is to do with the fact that that AXE's push-pull buttons use a short timer which resets the button back to its rest position after its been pushed or pulled, and if you happen to press the MCP button again within that time, the variable that denotes the managed/selected mode is not stable, hence the light is mismatched (at least until the next time you press it, when it usually syncs again).
I'm also having a bit of trouble getting the basic 'AP1 ON' wired up to the A/P CMD switch on the MCP; for some reason it's not as easy as it looks! Last, I've not yet addressed the DISENGAGE bar, but I expect it's the same problem.
The other thing I've not fully sorted out is how to make the displays show dashes (----) when the respective item is in managed mode, but this isn't the end of the world. I'm intending to resolve that once I've got the pushbuttons syncing reliably with the current mode, because an out-of-sync dashed-display will have far worse ramifications than an out-of-sync button-lamp!
Finally, I'm still working on the 'IAS/MACH' toggle and associated display - this will probably come later, if I'm honest, because it'll require some thought. My first attempts at it are simply not responding at all, so I'm still hunting for the right LVAR trigger or event.
But despite the above shortcomings, it is 'workable' already. You can use the rotaries and readouts for most 'everyday' tasks, and it certainly makes flying the bus a tad easier than using the mouse. To be fair, this is why some of the 'fripparies' haven't yet been done... I'm too busy flying it and using it, to remember to finish development!
It's my intention, once I'm finished, to make the files available to Stephen for his use and distribution if he thinks they're up to the job, but I'm also happy to share them now if you think they might be of any use to you with your MCP-PRO work.
Regards
Neil