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.

Loss of some functionality with Q400

JordanVJordanV
edited April 2017 in GoFlight Interface Tool - Technical Support
Hello, I have spent some time setting up various bespoke events (some of my own creation, some from Slayer, etc.) to use for the Q400 in conjunction with my two 166s, two RP48s, a SECM and various joysticks. I got the setup to where I wanted it and completed numerous flights with full functionality over the course of several months. However, in the past few days I have lost the functionality of various buttons and knobs that had previously been working fine. There seems to be no rhyme or reason as to which ones no longer work. Some of the bespoke events I got from Slayer's list work, and some don't. Some I've created work, and some don't. All of the same bespoke events seem to still be loaded, and I have opened up the detective to see if it is actually recognizing my button presses or knob turns of the non functioning items, which it seems to be. Everything looks good from the perspective of the GoFlight Interface Tool screen, however it is seemingly not connecting with the simulator for certain events. I have recently tried to reinstall the SimConnect SDKs to no avail. I have not messed with anything else in the sim to my knowledge between things working before and not working now. Any help would be greatly appreciated. It was fantastic to finally get this thing fully set up, and now I feel like I'm back to step one.

Comments

  • admin_ppsadmin_pps
    Has there been an update to the Q400?
  • JordanVJordanV
    No. To my knowledge I have changed nothing in the sim between it working fine and now not working.
  • dave39dave39
    Twice I have had the occasion with the Q400 where for no apparent reason some of my bespoke events magically change their coding to something made up of fake lvars. The ones that change all change to the same thing. I have absolutely no explanation for it. I learned the hard way to keep a copy of my GFIT Folder. Have a look at the coding and see if anything has changed. I'd be curious to know. Maybe it isn't just me!
  • admin_ppsadmin_pps
    Thanks for that info. Sounds like a bug if Jordan confirms the same issue.
  • dave39dave39
    ... and as luck would have it, it happened again today. This time my EFIS stopped working and when I check detective, the fake lvars have taken over! It has been a couple of months since it last happened and I have not idea why today. Thank god for backups!
  • admin_ppsadmin_pps
    Dave, can you please provide an example of what has changed. It will help me track down the issue. Thx
  • dave39dave39
    Sorry, I have already put my backup into use so I have lost it. Next time it happens (which isn't that often) I will send you a sample. By way of recollection, when I was looking in detective at the Baro knob on the EFIS it had fake lvars referring to the HSI and the same two lines of fake lvar code was in other EFIS knobs as well.
  • JordanVJordanV
    edited April 2017
    Thank you to both of you for your responses! Luckily I remembered that I had exported my bespoke events once I had gotten them set up to my liking and was able to import the whole batch and just switch the malfunctioning events to the duplicates from my save. Here is an example of what changed between the two. For turning on the antiskid switch, for instance, my original lines were: MJC_VAR_WRITE_VALUE = 1 MJC_VAR_WRITE_CODE = 96582 The corrupted versions that no longer worked had been changed to: AFCS_->outputs.AP_engaged_right_l = 1 AFCS_->outputs.AP_enaged_left_lt = 96582 This seems to have been the pattern for almost everything that was malfunctioning. I hope this helps with the fix. Thanks again to both of you. I'm now back up and running.
  • JordanVJordanV
    Well, I decided to try restarting FSX after resetting all of the malfunctioning bespoke events to make sure everything was good. When I booted up GoFlight Interface Tool I was encountered with multiple error messages saying e.g. "Failed to Load Configuration Data for Device GFDEVHWTYPE_GFSECM" I tried resetting a few events and restarting the sim and Tool again, but was faced with the same error messages for the devices on which I had reset the events. I also tried exporting and importing on the various devices to no avail. Any ideas what's happening?
  • admin_ppsadmin_pps
    If you have the configs saved for each device, I would wipe each devices config and the Bespoke Events, then import the Bespoke Events, followed by each device config.
  • dave39dave39
    I think you had the same problem I had by the looks of what your bespokes events got changed to.
Sign In or Register to comment.

© Vanilla Keystone Theme 2025