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.
21st November: A new version of the GoFlight Interface Tool for FS2020 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.
Learning the hard way
Hi Steve. I was always under the impression that things were saved on exiting GIT. But there are some exceptions to this and I’m finding out the hard way.
I have the Carenado PC12 for VFR flying and wanted to assign battery, alternators etc. to T8 switches. When I created bespoke events I was under the mistaken idea these would be saved when I exited GIT. But today, on wondering why none of the switches would work I discovered there were no events associated with the switches.
More investigation reveals bespoke events have to be exported otherwise they’re lost on exit. I’m getting there but the hard way. I guess you remember things more when you go through the frustration of losing work. But maybe a gentle reminder on exiting GIT that unsaved work will be lost would be helpful.
I have the Carenado PC12 for VFR flying and wanted to assign battery, alternators etc. to T8 switches. When I created bespoke events I was under the mistaken idea these would be saved when I exited GIT. But today, on wondering why none of the switches would work I discovered there were no events associated with the switches.
More investigation reveals bespoke events have to be exported otherwise they’re lost on exit. I’m getting there but the hard way. I guess you remember things more when you go through the frustration of losing work. But maybe a gentle reminder on exiting GIT that unsaved work will be lost would be helpful.
Cheers,
Ray (Cheshire, England)
Ray (Cheshire, England)
Comments
Best wishes
Steve
PS. If you have changed livery since making the Bespoke Events, the aircraft name will have changed, so you need to change the aircraft short name in settings to pick up all variations.
I’ll do this tomorrow and let you know the result. One question. If there is an Export function what does that do differently to just creating events and then exiting? The xml was updated when I exported the settings but if I didn’t and just exited GIT P that xml time stamp wasn’t updated.
Ray (Cheshire, England)
Ray (Cheshire, England)
Apologies. I created a bespoke event and then closed Detective and GIT. The time stamp on BespokeEvents.xml, BespokeVariables.xml and Settings.xml were updated and looking in BespokeEvents.xml it does contain the newly created event. I also checked the aircraft name and it's just Carenado PC12 so no problems with the livery.
So in theory those events should have been saved but they weren't linked to the switches. That appears to take place in Carenado PC12.xml and when I export the settings they do remain linked to the switches.
Ray (Cheshire, England)
Best wishes
Steve
Ray (Cheshire, England)
Best wishes
Steve
Ray (Cheshire, England)
Could this be a bug or something I have done wrong? I know for sure I created bespoke events for the fuel valves in the Xtreme Prototypes Lear 25. I have used them on previous flights. But if you look at this screenshot you can see they exist in the XP_Gates_Learjet_25_v3_Retrofitted.xml. But look at the list of available events and they don't appear. Why?
How does GIT know which file to load and from where? Do they have to be in a particular folder? Maybe that's the problem.
Ray (Cheshire, England)
Control ID="0" ACTIONType="EventCmd" ACTION="ONOFF" LIGHTType="SimVar" LIGHT="GENERAL_ENG_FUEL_VALVE1" LIGHTACTIONType="LightCmd" LIGHTACTION="OFF" LIGHTVALUEType="Float" LIGHTVALUE="0" ACTION_OFFType="EventCmd" ACTION_OFF="ONOFF" Control ID="1" ACTIONType="EventCmd" ACTION="ONOFF" LIGHTType="SimVar" LIGHT="GENERAL_ENG_FUEL_VALVE2" LIGHTACTIONType="LightCmd" LIGHTACTION="OFF" LIGHTVALUEType="Float" LIGHTVALUE="0" ACTION_OFFType="EventCmd" ACTION_OFF="ONOFF"
All xml formatting had to be removed otherwise it doesn't show.
Ray (Cheshire, England)
Ray (Cheshire, England)
The aircraft name does match. That's the first thing I check for. Things seem okay now Steve so I'll just see how it goes.
Ray (Cheshire, England)