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.

X-Plane FlightFactor 757 V2 EFIS + MCPPro + GF 166

SlayerSlayer
in GoFlight Interface Tool - User Provided Bespoke Events
This is for the new V2 version of the Flightfactor 757 -  please don't attempt to mix with the old one.
Steve McNitt

Comments

  • trevgtrevg
    Thanks Steve, be a couple of days before I can try it, lot of cleaning up after our large Earthquake

  • SlayerSlayer
    Oh man I forgot you live in NZ. Hopefully you and yours suffered no major damage. Just saw the post from another person I know there on Facebook but I believe he lives on the south island.
    Steve McNitt
  • pauleleepaulelee
    Hi I have this working well with the 752 but not the 753 any suggestions to get it working with that one?

    Many Thanks
    Paul
  • SlayerSlayer
    Yes, since the aircraft name is slightly different what you need to do is shorten it's name in the profile so it will work with both models. so instead of 757-200v2017 , shorten the name to just 757. There are instructions on how to do it in the GIT documents here on this site.
    Steve McNitt
  • pauleleepaulelee
    Hi Steve
    Thanks for your reply
    I have had a look for the document you mention but cannot seem to find it
    I have shortened the name of the zip to 757 but still no joy but obviously there is more to do

    Thanks in advance

    Paul
  • admin_ppsadmin_pps
    Hi Paul,

    Load up the aircraft and GIT. Go to the Settings tab in GIT and shorten the name there, remembering to click OK.

    Best wishes
    Steve
  • SlayerSlayer
    I actually upgraded as well and it worked . Load the-200 shorten the name click no on both questions.
    Steve McNitt
  • pauleleepaulelee
    Hi Guys
    Thank you for your help
    I do as you suggest and shorten the aircraft name to just 757
    I click OK then no twice
    But it does not save and when reloading the GIT it defaults back to both 757-200 and 300
    It does work very well in the 200 but not the 300
    I am sure I must be missing something simple
    If you require any further information please just ask

    Many Thanks
    Paul
  • SlayerSlayer
    Try loading the 300 then import the 200 profile again using the wizard.
    Steve McNitt
  • pauleleepaulelee
    Hi just Tried that
    I now only have Zero's on the MCP and it does not interact with the aircraft
    Thank you for your support

    Paul
  • SlayerSlayer
    try using this. Working here. Use import wizard.
    Steve McNitt
  • SlayerSlayer
    GIT doesn't like something. Now it won't import properly on my system with a shortened name either. Going to have to troubleshoot with Steve on this further when I have more time.

    Heading out for the day now.
    Steve McNitt
  • SlayerSlayer
    Steve: The import is failing and leaving some BE's blank that I used in the EFIS. If I delete all BE's the reimport them the aircraft works fine for that session only. Once restart X-plane/GIT it errors out and deletes bespoke events again.
    Steve McNitt
  • pauleleepaulelee
    Hi Guys will stop struggling with the 300 till you guys have had chance to have a look at it

    Cheers

    Paul
  • SlayerSlayer
    I found the problem. GIT is not detecting some datarefs that it did before and since they are not listed in datarefs.txt the program deletes all the code from the offending bespoke event.

    a workaround is manually adding these datarefs to datarefs.txt and then delete/reimport again.
    Steve McNitt
  • SlayerSlayer
    edited December 2017
    New Version - This one should work with all previous versions of the 757 and the new 757 V2 extended etc.

    The name has been shortened to work with all the variants.

    Steve McNitt
  • SlayerSlayer
    File
    Steve McNitt
  • jonflyjonfly
    The profile before this last one worked well today with the extended v2 200 - thank you Slayer!
  • SlayerSlayer
    I just noticed an issue. if you use "modern EFIS" setting in the aircraft my EFIS config doesn't work properly( I made if based on the default setting) I'll have to make a 2nd EFIS profile for the "Modern" setting as well. I knew this but totally forgot about it over the past years. Easy fix.
    Steve McNitt
  • Dutchdc3Dutchdc3
    edited January 2022
    I know this is an old thread, but by using it I keep all FF757 related issues centralized, zo please forgive me.

    I am using the latest GIT for my MCPPro, EFIS, 2x GF-166 and a GF46.

    When I have the FF757-200 v2 loaded the sim crashes when doing anything in GIT. Whether it is attempting to import a profile, or just restarting GIT to get the MCPPro to work. Been working on this for a few weeks now.

    I have no problems with GIT when using any other aircraft in X-Plane 11, like the Zibo 737-800X, the Rotate MD80 and the LevelUp 737NG's
  • admin_ppsadmin_pps
    Do not have Update On Flight Loop ticked, if so untick it. Also it may be related to enabling Vulkan & Metal.

    Best wishes
    Steve
  • Dutchdc3Dutchdc3
    I do use Vulkan, but will have a look at the Update On Flight loop

    Thx for your reply
Sign In or Register to comment.

© Vanilla Keystone Theme 2025