Back to Browse
User Content
MobiFlight Profiles

Winwing "PAP3" & "PFP 3N" Profile for FlightFactor 757

A MobiFlight profile to control the FlightFactor 757 autopilot using your Winwing PAP-3 panel and interact with the CDU via the Winwing PFP 3N. It supports key inputs and display outputs in X-Plane, offering a more hardware-integrated experience for FlightFactor 757 users.

5.0 / 5
453 downloads
Favorite Subscribe
Screenshot 1

Description

Winwing "PAP3" & "PFP 3N" Profile for FlightFactor 757 - BETA Version

Requirements:
Winwing PAP3 advanced features via FlyWithLUA-Script:
  • CORSE L/R in AUTO & MAN mode
  • F/D Master lights
Features Winwing PFP 3N:
  • Full key input
  • Display & announciator lights support via
    • A) MobiFlight companion app "CDU 757 Tray.exe" or
    • B) auto-loaded .py-file in your MobiFlight Installation
What about the FlightFactor 767?
  • I don't have the B767, but since the airplane shares the same DataRefs, it is very likely this profile, as well as the .exe to feed the CDU will work with the B767 as well
  • Until I get feedback about the compatibility, it is not stated officialy compatible here. Give it a try and report back please, if you own this bird as well.
Installation MobiFlight Profile:
  • Update MobiFlight to latest BETA Version via Menu: "Extras > Settings > General | Beta Versions" and tick checkbox "✅ Yes, I would like to receive beta version updates" and restart MobiFlight
  • Load "FlightFactor_B757.mfproj"
  • Assign orphanded hardware devices at first startup, by selecting a device from the list, then select your hardware from the dropdown-list below and klick button "Assign"
  • Repeat with your remaining hardware. Note: DO NOT assign your single PFP-3N (CDU) to multiple serials (WINWING PFP-3N-CAPTAIN & PFP-3N-CO-PILOT), leave one unasigned in this case
  • When done, klick Button OK
  • Save the profile right away via the Save-Button to remember your device assignment for the next start
  • To run the profile, select "Run" or user "AutoRun" to start the profile when MobiFlight loads automatically
Installation FlyWithLUA script for advanced features:
  • Install FlyWithLUA to "...\X-Plane 12\Resources\plugins"
  • Copy script "ff_mobiflight_bridge.lua" to "...\X-Plane 12\Resources\plugins\FlyWithLua\Scripts"
CDU Installation Method A - "CDU 757 Tray.exe":
  • Copy "CDU 757 Tray.exe" into a folder of your choice, but not into your X-Plane folder
  • Start the "CDU 757 Tray.exe" after you loaded the flight and MobiFlight is running with the profile
  • The Application can be stopped via a "757 CDU"-icon in your system tray by right-clicking and chose "Exit"
CDU Installation Method B - .py file into MobiFlight-Installation:

STEP 1: COPY THE PYTHON SCRIPT

1. Extract file from the zip:
   flightfactor_b757_b767_winwing_cdu.py

2. Open File Explorer and go to the following folder:
   C:\Users\YourUsername\AppData\Local\MobiFlight\MobiFlight Connector\Scripts\Winwing

   Note: If "AppData" is hidden, you can enable "Show hidden files" in Windows Explorer.

3. Copy the .py file into the "Winwing" folder.

STEP 2: EDIT ScriptMappings.json

1. Navigate to:
   C:\Users\YourUsername\AppData\Local\MobiFlight\MobiFlight Connector\Scripts

2. Make a backup of the file:
   ScriptMappings.json

   (Right-click the file > Copy > Paste)

3. Open the original ScriptMappings.json in a text editor (e.g., Notepad).

4. Add the following blocks at the end of the existing mappings:

   {
     "VendorId": "0x4098",
     "ProductIds": [ "WinwingCDUs" ],
     "AircraftIdSnippet": "boeing757",
     "ScriptName": "flightfactor_b757_b767_winwing_cdu.py"
   },
   {
     "VendorId": "0x4098",
     "ProductIds": [ "WinwingCDUs" ],
     "AircraftIdSnippet": "boeing767",
     "ScriptName": "flightfactor_b757_b767_winwing_cdu.py"
   }

IMPORTANT:

  • Ensure the file still contains valid JSON syntax.
  • Each block must be separated by a comma, except for the last one.
  • The full content should be wrapped in square brackets [ ... ].

Tip: You can use a free tool like https://jsonlint.com to check if your JSON is valid.

Optional installation of BoeingCDU Font:

Font file for legal reasons not provided in mod files. You have to look it up yourself on the web, if you want it.

  • Open SimAppPro
  • Go to tab "Game Peripheral Display", select your "PFP 3N" on Device and select "Font Management"
  • Click Button "Import Font" and select "BoeingCDU-Bold.ttf"
  • Select it if not auto-selected and klick "Apply"-Button in the bottom right
  • Close SimAppPro again
Usage
  • Start MobiFlight, load the profile FlightFactor_B757.mfproj and select "Run" if "AutoStart" is not active
  • Load your flight with the FlightFactor Boeing 757
  • Only when used installation method A, Start "CDU 757 Tray.exe"
  • Happy flying
🚧TEC-LOG:
  • CDU showing solid blocks 🔲 instead of empty 🔳 blocks for entries like ORIGIN and DEST
    • Open SimAppPro, go to tab "Game Peripheral Display", select your "PFP 3N" on Device and select "Font Management". Change selected font from your current one to a diffrent one and click "Apply"-Button in the bottom right. The front should show up on a grid on your device. Now change back to your desired font and klick "Apply"-Button again. CLOSE SimAppPro afterwards. If no change detected, repead
    • It also may be nessesary to repeat this step your next flight again 😒
    • Note: If fragments of SimAppPro font grid preview are still present on the top and bottom of the screen, simpy change to a diffrent CDU page to refesh the screen. 
  • In SPD INTV mode, IAS and MACH label not matching diplayed speed unit in some occations
    • In SPD INTV mode, toggling between IAS and MACH and canceling SPD INTV while IAS is active, instead of MACH, re-engaging SPD INTV mode may show IAS label when MACH-number is shown and MACH label when IAS speed is on the display
    • Solution: Leave SPD INTV with MACH selected or the other way around, depending on the issue (Fix pending, as root of the issue needs to be evaluated (Profile or FlightFactor)
General note about SimAppPro & MobiFlight

You should not use them together, as there is no option to disable a single device in SimAppPro, resulting in MobiFlight and SimAppPro fighting over who has control of your hardware, or double inputs registered, in case SimAppPro supports your simulated Aircraft natively.

Support:

MobiFlight Discord: https://discord.gg/HbuTa3sc
MobiFlight Website: https://www.mobiflight.com

Special thanks to guiche76 from the MobiFlight Discord, for providing the CDU-profile as well as the code to support the CDU display with MobiFlight and his kind permission to share the result with the community 🛫

Disclaimer

This is a non-commercial fan-made modification for X-Plane.

X-Plane is a trademark of Laminar Research.  
Boeing and 757 are trademarks of The Boeing Company.  
FlightFactor is a trademark of FlightFactor Aero.  
Winwing is a trademark of Shenzhen Zhihui Technology Co., Ltd.

This mod is not affiliated with, endorsed by, or associated with Laminar Research, The Boeing Company, FlightFactor, or Winwing.  
All trademarks and product names are the property of their respective owners and are used here for identification purposes only.  
All included content is provided “as-is” without any warranties. Use at your own risk.

Changelog

  • v0.8.3 31. May 2025
    - Added alternative installation method to remove the need for "CDU 757 Tray.exe" by manually adding a python-script to your MobiFlight-Installation
  • v0.8.2 31. May 2025
    - Made "ff_mobiflight_bridge.lua" more robust against a freshly updated aiplane and its need to be re-activated, resulting in DataRefs not be ready until the activation was completed, causing the script to crash (and moved to FlyWithLUA quarantine folder)
  • v0.8.1 13. May 2025
    - Fixed issue where F/D toggled from OFF to ON during MobiFlight profile start, even when the hardware switch was physically in the OFF position
    - Fixed AP DISENGAGE BAR jumping into ENGAGED (DOWN) state when the profile started
    - Significantly more acurate COURSE synchronization in VOR/DME AUTO mode between hardware and aircraft systems
    - Added "LCD Test Mode" for PAP3 via ANNUNCIATOR TEST button on the overhead panel

Comments

Add Your Review
User avatar
jaytea24 17. Sep 2025
Thank you.
User avatar
DenizVB313133 16. Aug 2025
yea so everything works perfectly fine accepto for the dep arr button on the fmc i click it and it sends me to the route (rte) page
User avatar
Bluewren 15. Aug 2025
Just some feedback for the FF767...I use the FF767-300ER Pro version with a Winwing PFP4, the latter now supported by Mobiflight 10.5.3.11 I have modifed Karaya2's PFP 3N script to suit my preference for key allocation and some other minor changes...eg. one difference was the PFP 3N has a CALL led and the PFP4 has a DSPY led so this was modified. I have made two scripts, one with the same key allocations as in the PFP 3N script and my own custom one which aligns the functions with the appropriately labeled keys and allocates CLB, CRZ, DES and DIR INTC to the unused ATC, VNAV, FMC COMM and RAD NAV keys. In tests so far both CAPT and FO CDU's are working fine I don't use a PAP3 so I haven't included that in the two scripts and the LUA file is not required. If Karaya2 is happy for the modified scripts to be posted I will put them on the site. Thanks Karaya2 for you work on this and I would appreciate if you can let me know your thoughts if it is possible my modded scripts could be made available with the appropriate acknowledgement of that work. Many Thanks Ian
User avatar
SkyCaptainA320 13. Jul 2025
Thanks for this alot! Just a few items to note regarding the 767. Flight Director - no animation Auto throttle switch- no animation Heading displays - No numbers shown Altitude displays - No numbers shown

Download

Version: 0.8.3
Size: 12.94 MB
Uploaded: 01. Jun 2025

Author

Karaya2

Joined Dec 2020
View Profile

Contributors

No contributors listed.

Requirements

  • • X-Plane 12 or later

Information

Release Date 13. May 2025
Downloads 453
Rating 5.0
Category User Content / MobiFlight Profiles