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.
Zibo's B737 X-Plane 3.10o Alpha
Hi,
Testing Zibo's new release raised an issue with the map range knob on the GF-EFIS. Zibo is now using new datarefs and has exposed commands to move the map range up and down. I've modified the bespoke events for the B737 which are attached, along with the command.txt file and DREDataref.txt file.
Once Zibo releases a final stable version, I'll update the package in the downloads area.
Thanks.
David
Testing Zibo's new release raised an issue with the map range knob on the GF-EFIS. Zibo is now using new datarefs and has exposed commands to move the map range up and down. I've modified the bespoke events for the B737 which are attached, along with the command.txt file and DREDataref.txt file.
Once Zibo releases a final stable version, I'll update the package in the downloads area.
Thanks.
David
Comments
I am new to these config files. I adapted the previous config file to use my GF-46 to control the transponder.
I don't want to loose my current settings.
Do I need to copy the content of the xml file and overwrite/past it over the EFIS part in my current xml file, or is there an easier way of just updating the efis part, without it affecting the configs of my other modules for use with Zibo's 737 mod?
Btw: is the issue you are referring to related to the EFIS VOR error that I see?
Thank you in advance for your reply.
I'm assuming that you've installed Zibo's 3.10o alpha aircraft, but the steps are the same for all versions. The files may change.
Each of the GoFlight device types (ie MCPPRO, EFIS, GF-46, GF-166 etc) can be exported individually, which can then be imported again at any time. The standard directory is /Document/GoFlight Interface Tool. This is the way to save your settings for your GF-46.
On the downloads page I created a zip file which contains everything you need (for my device types) which includes the xml for each device type and an xml for any bespoke events that I've created to make it work. This can be imported in one go using the Import Wizard on the status page. This is normally the way to set it up initially.
What I've attached in previous posts are changes to specific files that need to be imported and/or moved to the aircraft folder individually.
When you get errors loading device xml, the first thing to check would be if the bespoke events have changed, the commands file has changed or the datarefs have changed.
I've written some bespoke events to handle the map mode and map range (and yes you picked up a bug in the map mode). The attached xml fixes that. Put it in your /documents/GoFlight Interface Tool directory.
The Commands.txt and DREDatarefs.txt must be put in the specific aircraft directory (replace if necessary). Every time you upgrade to a new version of Zibo's aircraft, make sure these files are copied.
Once you've opened up GIT, go into Detective, delete the existing events and import the bespoke events, otherwise you'll get duplicates. If you've created any bespoke events of your own for the GF-46, they won't be affected.
Hope this is not too long winded. Let us know how you get on.
David
I was still using 3.06p, but now switched to 3.10o. That caused X-Plane to crash when loading the plane.
I have that now resolved.
I did export my adjusted device configs, and will work with your attached file after I get back from work later tonight.
It is a steep learning curve, but I am really enjoying this.
The file fixed the EFIS VOR error, but then I found that the heading dial on the MCP was no longer responding. Found the resolving config file in another thread. Now all seems to be fine.
Thanks for all your effort and support.
The learning curve continues while attempting to program for other other airplanes, starting with the default C-172
One thing still outstanding is the V-speed display and IAS/Mach display during VNAV. My units display what the autopilot is selecting but the displays in the sim are blank. I'm obviously using the wrong dataref to display so I'll check it out.
David
I just hope that Zibo's updates don't mess with your config files too much.
I managed to get my GF-46 to work as the transponder in the Zibo Mod, and exported the config file.
I did notice the displays not being blank, but I am enjoying my panels thanks to your work, and Pollypot's GIT.
Still a bit confused about what the bespoke evens and the other one exactly do. And how to get the detective to show just events when pushing a button, or flipping a switch. How to
Are bespoke events like custom actions, like macro's in FSUIPC?
Sorry, didn't want to bug you with my questions, and go off topic. Just so much to learn.
Jon
Am in the middle of updating the profile. I'm adding some features to blank out the IAS and V/S where appropriate but have hit a bit of a snag. The displays don't want to behave when changing pitch mode. Steve is looking at this at the moment so am waiting to hear back from him after he's had a chance to investigate.
It's almost there.
David
I've been flying with the latest Zibo versions now for a while and they're just fantastic. I purchased 2 new powered USB 2.0 hubs and, touch wood, the GF-166's seem to be behaving themselves.
In terms of the profile, I'm only working on the version for the latest Zibo mod (currently 3.20b). The changes are:
- Implemented Aircraft Power - Units will 'come to life' on battery power. Takes about 30 secs to initialise the devices. I look in the log.
- Blank out V/S (Dependant on pitch mode)
- Blank out IAS/Mach (Dependant on pitch mode. This is the one that's problematic at the moment)
Changing to VNAV always works (IAS/Mach and V/S blanked) and the first time you change to another pitch mode it seems to be OK (IAS/Mach is displayed) but subsequent changes between VNAV and other pitch modes (LVL CHG or V/S) the IAS/Mach doesn't display. (Steve's having a look into this).
If you move the rotary the display re-appears.
You're more than welcome to try it out with Zibo's latest version. I've attached a zip file. The Commands.txt and DREDatarefs.txt must be put in the specific aircraft directory. Every time you upgrade to a new version of Zibo's aircraft, make sure these files are copied.
David
Just downloaded, and will give it a try tomorrow
After Steve has provided an update and I've done some testing, I'll ask Steve to upload the new profile onto the download page.
David
Can we clarify the "blow up issue". I have just tested with Davids script and X-Plane 11 and accessed the X-Plane menus OK. What versions of X-Plane are you running? What is reported in the GIT error log when it goes wrong?
Thx
Steve
commands.txt and Datarefs file placed in the aircraft folder, and all other files in the documents/Goflight Interface Tool folder.
Guess will have spend some time figuring this out. Ah, it's part of the learning curve.
David, thank you for providing us these profiles
Sounds like you're really close. I'm assuming you've gone to the MCPPRO tab and tried to import from there. It's probably highlighted the fact that I should do up an installation sheet so you guys aren't guessing on what I've done.
In this release I've added some bespoke events and variables so the best (maybe easiest) way would be to import through the wizard. By checking the box to 'Remove existing Bespoke Events' it will eliminate duplicates and you can select the devices to import.
Hope this helps.
David
Here is what I did:
Imported the profiles for the modules using the wizard.
The GF166 were working, but the one for coms only showed a "5" as a command for the center1 button. I was able to fix that, so the GF166's are both working fine,
The EFIS is not doing anything at all, so I will have a look that tomorrow (it is 11:50PM here right now).
The MCP is only showing zeros on all displays, and no actions on the rotaries.
I was able to import my previous profile for this module, all displays are now showing the correct values, but the rotary for the heading is not working (old bug is back).
The Commands.txt and DREDatarefs.txt files are copied to the aircraf specific folder, and I placed the remaining files in the zip in the "Documents\GoFlight Interface Tools" folder.
No idea what I am missing there.
It's too late to further investigate the issues, but will attack it with a fresh mind in the morning.
Again, thanks for all the support so far.
Go into each device and kill the config (red X). Go into Detective and click the Big Red X in the bottom right corner to kill all Bespoke Events for the aircraft. Go into the aircraft's root directory and delete commands.txt, datarefs.txt and DREDatarefs.txt.
Run the import wizard. If it errors, run it again.
Best wishes
Steve
Only on the left light on the Com GF-166 panel would not come on, but I was able to fix that. All is working fine now, including the EFIS
David, is it correct that the rotary for the EFIS Baro is not programmed?
No the EFIS baro is programmed. The only functionality on the aircraft that can't be done through the GF-EFIS module is the selecting of inHg and millibars. I assign those to other unused buttons.
I use the laminar/B738/pilot/barometer_down & laminar/B738/pilot/barometer_up commands.
After you start GIT open the EFIS tab and select the device, you should see what has been implemented for the Rotary_Baro.
Thanks.
David
Everything is working fine now.
Again, thanks to David and Steve for their support.
I am really enjoying this learning curve.
Btw: A small tutorial of instruction sheet on how to update profiles (what files go where?) would be helpful to newbies like me.
Oh, and before you ask... Yes, I did go through all the tutorials/instructions on the site, but the above part is not covered.
Great news. I'll have a look at creating something for my profile.
When I decided to go over to x-plane I looked around for something to enable my GoFlight devices and I tried other plugins before I literally stumbled across GIT. Best thing I did. Steve's program, from my point of view, is ahead of the pack, and the support that he provides is excellent. (and I'm not just saying that because he's found some bugs for me).
On a side note, for those that are using my profile for V3.10 or greater, there is a lag in the IAS/Mach and V/S displays. What that means is that if you turn the rotary too quickly it will keep increment/decrementing the display even if you stop turning. The way to handle it is to turn the rotary at a slow steady rate. Experiment with it to get the feel for how fast to turn it.
Enjoy and I'll be updating the download when Steve releases the new x-plane version.
Thanks.
David
New version is available now. It should also have fixed all the import issues along with adding Lua support.
Best wishes
Steve
David