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.
Blanking Displays in Change of Pitch Mode
Steve,
Building on the first iteration of the aircraft config files for Zibo's B737, I'm adding the features to blank the v/s and ias displays. I've created 2 bespoke variables, one for each display. (I've attached the xml files that I've created to this point). Basically when the bespoke variables are zero, the display should blank. That's the theory.
In practice, changing the pitch mode reveals inconsistent results.
I have created a start event which was primarily to capture the change of modes when I haven't pressed anything on the MCP (ie. v/s ==> alt hld). The event uses the switch, case, endswitch task to test the exposed datarefs from Zibo to see if the displays are illuminated and sets the bespoke variable to zero or specific dataref depending whether it should be displayed. (laminar/B738/autopilot/show_ias and laminar/B738/autopilot/vvi_dial_show). The start event also sets the MCP up initially after the battery is switched on. I'm assuming, based on the user guide, and I've setup a loop within the start event, that the start event continually loops and will set the bespoke variable irrespective of anything else happening in the sim.
To set the scenario.
1. Climbing, the MCP shows IAS displayed, LNAV on, LVL-CHG on and N1 on. Everything fine.
2. Press VNAV. IAS display blanks, V/S display blanks (already was), vnav on, lvl-chg off. Everything fine. And in actual fact, everytime I turn VNAV on, it works perfectly.
3. Press V/S. IAS remains blank (should redisplay IAS), V/S displayed correctly, VNAV off and V/S on. No matter how many times I switch from VNAV to V/S and back and forth, the IAS doesn't display. The Zibo datarefs are assigned correctly.
This is just one example of what it's doing.
I don't know whether this is a timing thing for each of the inputs for the MCP, although I've put sleeps into the tasks to see if that makes a difference, and I may be doing something that's completely wrong. I'm not sure how changing a bespoke variable triggers GIT to determine what other inputs from the same device may be affected.
I'm hoping you may shed some light.
Thanks.
David
Building on the first iteration of the aircraft config files for Zibo's B737, I'm adding the features to blank the v/s and ias displays. I've created 2 bespoke variables, one for each display. (I've attached the xml files that I've created to this point). Basically when the bespoke variables are zero, the display should blank. That's the theory.
In practice, changing the pitch mode reveals inconsistent results.
I have created a start event which was primarily to capture the change of modes when I haven't pressed anything on the MCP (ie. v/s ==> alt hld). The event uses the switch, case, endswitch task to test the exposed datarefs from Zibo to see if the displays are illuminated and sets the bespoke variable to zero or specific dataref depending whether it should be displayed. (laminar/B738/autopilot/show_ias and laminar/B738/autopilot/vvi_dial_show). The start event also sets the MCP up initially after the battery is switched on. I'm assuming, based on the user guide, and I've setup a loop within the start event, that the start event continually loops and will set the bespoke variable irrespective of anything else happening in the sim.
To set the scenario.
1. Climbing, the MCP shows IAS displayed, LNAV on, LVL-CHG on and N1 on. Everything fine.
2. Press VNAV. IAS display blanks, V/S display blanks (already was), vnav on, lvl-chg off. Everything fine. And in actual fact, everytime I turn VNAV on, it works perfectly.
3. Press V/S. IAS remains blank (should redisplay IAS), V/S displayed correctly, VNAV off and V/S on. No matter how many times I switch from VNAV to V/S and back and forth, the IAS doesn't display. The Zibo datarefs are assigned correctly.
This is just one example of what it's doing.
I don't know whether this is a timing thing for each of the inputs for the MCP, although I've put sleeps into the tasks to see if that makes a difference, and I may be doing something that's completely wrong. I'm not sure how changing a bespoke variable triggers GIT to determine what other inputs from the same device may be affected.
I'm hoping you may shed some light.
Thanks.
David
Comments
Everything does look OK, so its either a bug in GIT or laminar/B738/autopilot/show_ias is not changing to 0 or 1. I'll do some testing and come back to you.
Best wishes
Steve
I haven't forgotten about the issue you have identified. I'm bogged down in getting a major upgrade to GIT out the door this week, and then I will look at this issue and add the upgrade to GIT X-Plane.
Best wishes
Steve
Thanks for the update. Whenever you get the chance is good enough for me. I've received my 2 new USB 2.0 power hubs so it will give me chance to see if they make a difference for the GF-166 devices on separate hub devices.
IAS display is the only issue but it's not stopping me from flying. This is a great tool and much appreciated.
David
I believe I have found the bug. Basically, data is only ever written if its changed and because the IAS and VS speeds hadn't changed, the displays do not update even though GIT had detected the displays needed updating because of the BLANK action.
I have altered the code and it appears to be working as expected now. I'll aim to get the update out this week.
Best wishes
Steve
David