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.

Bespoke events changed - in the background XP-11

Hi Steve,

I have programmed the 757-200 and did my own bespoke events, and assigned the events to my Go-flight modules, somehow not sure but my entire set up has just changed the bespoke events. ie I program for example:_b757_elec_bat_pwr_off, and similarly the on event. When I restart my PC the name is the same but the actual event coding has changed. This is happening through all events and modules, one day the Mcp will work perfectly, then the actual events are changed and things that worked before is now recoded to something else.

Example included in the screen shot, This as programmed as landing light Centre on, now the 1-sim/jettison has over written my previous programmed event, even the light data has been changed.

How can I prevent this as now I need to do 14 goflight units again, and this happens across all my aircraft.

Thanks
Andre

Comments

  • edited August 2017
    Are the device numbers changing, so the assignments shift?
  • Hi not sure how to check device numbers change, but its not the assignment to the GF unit that is changing.

    1. I create and name a bespoke event, _B757_lights.... where you see on the detective the coding 1-sim/jettison... that is what is changing it used to be anim/button14
    2. I assign it to the button
    3. It works, when I restart my machine the actual coding of the event changes, whilst it keeps the name of the event it then also changes the light data on GFT. on the GFT you can see the B757 switch event that did not change just the coding for the event itself.
    4. I never programed any event to be 1-sim/jettison....

    thanks
  • Correct the config and quit GIT, then zip up the contents of Documents\GoFlight Interface Tool and attach here. Tell me what aircraft you are using.

    Thx
    Steve
  • Ok I will as soon as I can in the next few days, Thanks
  • edited September 2017
    Hi Steve, Please ignore this one
    Attached my current version reprogrammed, Boeing 757-200V2017 professional is the aircraft from Flight factor
  • Hi Steve, Newly updated
    Attached my current version reprogrammed, Boeing 757-200V2017 professional is the aircraft from Flight factor
  • OK, thanks. I will take a look sometime this week.

    Best wishes
    Steve
  • Hi,

    Just went to test and realised you have not included the Bespoke Events. You will need to export those via Detective and add them here.

    Thx
    Steve
  • Scrap that, you have included the file. But I cannot see 1-sim/jettison... or anim/button14 in the file!?
  • OK. I found anim/14/button on the battery power Bespoke Events and they loaded OK and reloaded OK. So no problem found.

    It could be either your config file is corrupt or you are using another aircraft that matches the aircraft name of the FF and its screwing up the config.

    If you zip up Documents\GoFlight Interface Tool and attach here, I can try with your exact configuration.

    Best wishes
    Steve
Sign In or Register to comment.