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.
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.
The case of the disappearing LVAR & EVENT
Hi,
I'm trying to use DETECTIVE to write a function that will interface with FSDreamTeam's GSX.
The function will detect when GSX has completed loading CARGO, and will then simulate the rampies closing the cargo doors (instead of me having to do it via the FMC (Airbus).
I managed to pick up a number of LVARS and events, and noticed GSX wrote changes to the following LVARS:
FSDT_GSX_BOARDING_STATE
FSDT_GSX_DEBOARDING_STATE
FSDT_GSX_CATERING_STATE
FSDT_GSX_DEPARTURE_STATE
I wrote my routine, and was about to test it when I forgot to save my config, before hitting the reset button in GIT, meaning I had lost my code updates.
So, I set up the sim and GIT ready to repeat the process.
This time, Detective did not seem to pick up any FSDT LVARS at all and therefore I was not able to recode my routine.
Ive reset my sim and GSX, but for some reason I cant get Detective to pick up those GSX LVARS again.
Is there something GSX is doing, or something Detective is missing that is resulting in me detecting those GSX LVARS on random occasions?
I'm trying to use DETECTIVE to write a function that will interface with FSDreamTeam's GSX.
The function will detect when GSX has completed loading CARGO, and will then simulate the rampies closing the cargo doors (instead of me having to do it via the FMC (Airbus).
I managed to pick up a number of LVARS and events, and noticed GSX wrote changes to the following LVARS:
FSDT_GSX_BOARDING_STATE
FSDT_GSX_DEBOARDING_STATE
FSDT_GSX_CATERING_STATE
FSDT_GSX_DEPARTURE_STATE
I wrote my routine, and was about to test it when I forgot to save my config, before hitting the reset button in GIT, meaning I had lost my code updates.
So, I set up the sim and GIT ready to repeat the process.
This time, Detective did not seem to pick up any FSDT LVARS at all and therefore I was not able to recode my routine.
Ive reset my sim and GSX, but for some reason I cant get Detective to pick up those GSX LVARS again.
Is there something GSX is doing, or something Detective is missing that is resulting in me detecting those GSX LVARS on random occasions?
Regards
David
David
Comments
Hi David,
I suspect that the GSX addon is not creating the LVARS when sim mode is initialised. GIT only searches for LVARS once so if any LVARS are created after that, you won't see them.
Best wishes
Steve
I came to the same conclusion, after experiencing a major issue with GIT (self inflicted).
I managed to program my functions after an upgrade to GSX latest version. The LVARS were available every time I wanted to edit my code.
This worked perfectly - I had added some code in my START macro to monitor the values and act on change.
I also set the MCPPRO Coure LED to display the value I wanted to keep an eye on.
Things went horribly wrong when, it appears that one restart, GSX didint declare its LVARS before the START macro kicked in.
It appears that GIT auto-removed the lines of code in my START macro referring to the GSX LVARS.
This meant that the If tests I was using were removed, which causes GIT to go into a very tight loop, due the the remainder of the code surrounding the GSX tests.
The ref to the GSX LVAR for the MCPPRO also broke that code.
The end result was I had to manually edit the code before restarting GIT to remove the offending tight loop. I also note it looked like it reset all my coding for the MCPPRO as well.
Good thing I had a backup to recover from.
Ill see if I can discuss with FSDT regarding the init time of their LVARS
Regards
David
David