Avatar

dr1980

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.

dr1980

Comments

  • Thanks for all of this information. I'm wondering if anyone here is planning to create a profile with the push/pull functionality for public use? I started playing around with this and realized how rusty I am at using Detective...before I invest a bunch of time potentially duplicating efforts I wanted to see if anyone else…
  • I’m curious how you’re building that profile? I built one for the P3D version but the detective tools etc don’t seem to be working in the MSFS version so I couldn’t start digging into the MSFS version. I’ve found that using a default profile some things work but as you’ve noted altitude select firmly does not work.
  • Thank you!
  • Thanks for that Steve, I never would have guessed that one correctly!
  • Works great here Steve, thank you. I appreciate having my basic MCP PRO controls back especially given the default aircraft G1000 seems to be missing the altitude select knob.
  • I finally had a few hours to dig into this and troubleshoot and finally realized the one thing that was preventing GFIT from working...I had my MCP PRO plugged into a USB hub. Once I plugged it directly into a USB port on my computer all is working well now. Dave
  • Thanks Steve, it's strange that this issue is happening, I did not have this issue before I updated to the P3Dv5 version of GFIT. Could something have changed to cause this issue? I just use the regular windows firewall, so I'm scratching my head as to why I would be having this issue but seem to be alone in that. I can…
  • Thanks Steve, I'm a bit confused by this, all of my flight simming software and GFIT are stored locally on my computer, no networking involved, so what networking comms could be blocked? Or am I completely misunderstanding this?
  • No luck unfortunately, log below: 19:52:33 GoFlight Connection Starting..... 19:52:33 SimConnect Connection Starting..... 19:52:33 SimConnect Message Processing Started 19:52:33 GoFlight Connection Started 19:52:33 SimConnect Connection Started 19:52:33 Aircraft Connection Starting..... 19:52:34 SimConnect: Event Received:…
  • Thanks Steve, I do have this entry present: I'll try adding an exclusion from my virus scanner and firewall.
  • Hi Steve, looks like I spoke too soon. I've had some follow on flights where the MCP stops responding after a period of time. On one flight, it was gradual - first the displays stopped updating but the aircraft was still receiving the inputs for a while before that stopped too. This does seem to be specific to the Q400 and…
  • Thanks Steve, I hadn’t realized the issue with power management for USB hubs so i have disabled that and plugged my MCP PRO into a power USB 2 hub and it looks to be working better now, thanks!
  • Hello, I'm trying to use the FJS732 file. When I attempt to use the wizard to install it I get a crash with no error message. I tried a manual install but I don't seem to have the first .xml file that I need to install using the detective before activating the files for each piece of hardware. Activating only the hardware…
  • I prefer the knob push.
    in QW 787 Comment by dr1980 June 2018
  • Thanks for this Steve, happy to test whenever you think it's ready.
    in QW 787 Comment by dr1980 June 2018
  • An update on this, I installed the 64 bit version of GFIT today and this profile is now working for the entire flight.
  • Hello, I finally got around trying this again, waiting until p3d is loaded to start gfit as suggested above. I had the same result as before: the first time i run it I can use my goflight devices on the ground and a few minutes into flight, then they stop responding. When i shut down gfit (has to be done through task…
  • Thanks, that's odd on the first one as I loaded the Q400 from the opening scenario page. I'll try waiting until the Q400 is loaded before loading GFIT.
  • I tried re-installing the Q400 tonight. I've also been having issues with FS2Crew for the Q400 - the first officer keeps saying "1000 to go, alt sel" at inappropriate times, the flight attendant keeps saying hello when I haven't contacted them, FO calls out V2 when I'm no where near V2 and a host of other oddities - so I…
  • 32 bit here
  • Sorry, when I said setup I meant to set up the aircraft for departure. I also start GIT fresh every time I start up p3d and for each individual flight (I can see now how my post last night was a bit ambiguous!) I decided to do a flight in another aircraft tonight (PMDG 777) to see if the problem would materialize with a…
  • Thanks for doing this profile. I'm having an issue where after takeoff my MCPPRO and EFIS stop working. On the ground I can use both without issues to set things up, but on multiple flights after takeoff the displays on the MCPPRO become frozen and the inputs do not register. Anyone else experience this?
  • Thanks for your work on this, the MCPPRO is working well. Looking forward to seeing the EFIS update.
  • Ok, as I do some more digging it looks like this is actually real world behaviour...oh the things you learn when using flightsim hardware :) I hope everyone enjoyed watching my educational journey through these three posts lol
  • Looks like this happens with the 747 and 777, but not the 737NGX.
  • Glad to hear it Steve, I was with Rob about to press the sell button on my MCP-PRO otherwise! :) Thanks for your work on this.
    in Prepar3d v4? Comment by dr1980 June 2017
  • I decided to test my hypothesis tonight by going into my dll.xml fiel and disabling the tacpack file "Modules\VRS_TacPack\VRS_TacPack.dll". Based on a 15-minute test, this seems to have fixed the issue (the issue usually cropped up after only a few minutes previously). I'm going to do some longer flights tomorrow to…