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.
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.

FSLabs A320

Has anyone tried any custom inputs for the MCP-PRO with the newly released A320 from FSLabs yet?

Comments

  • Hi,

    I have not had any success in getting any buttons or knobs in any of the FSLabs A320 to work in GIT.

    Supposedly someone on the FSLabs forum reckons he got the beacon light to turn on and off by setting FSUIPC custom control number 66587 with params 72477 (on) and 72476 (off).

    I think I did this correctly in GIT but it didnt seem to work.
    I used detective to capture what LVars and Events were invoked when i clicked on that switch, and tried to replicate via a Bespoke Env but that didnt work either.


    Regards
    David
  • edited February 2017
    If a developer uses nonstandard ways to implement their controls it is hard to do , it may not be solvable unless they stuck inside the fsx or p3d SDK. Those number you posted above look like mouse clicks so I would run detective and change one thing you are trying to figure out etc and look in the "detected " section . This will give you clues. In my experience with mouse clicks send the command as a 0 and a diff numbered mouse click with a 0 for on and off. Many times these mouse clicks will not show up until you have had detective running and looking for them so that they are selectable,
    Steve McNitt
Sign In or Register to comment.