Avatar

Slayer

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.

Slayer

Comments

  • It is indeed tedious especially when you sometimes don't see what is working
  • Sounds like some kind of conflict with the pitch wheel. I haven't had any other reports of this yet and that function hasn't changed since the first version. Have you double checked that your MCP is set to "compatible addon" within GFconfig? One last ditch thing you could try too for the VS wheel is setting clockwise to:…
  • Steve, Two major releases happening very soon that I want to put this to task on . First the IXEG 737 which will release on Saturday the 23rd and also the freeware X737 is getting the 3D cockpit overhaul and it will be released on May 1. Once you release this be prepared for an influx of X-Plane users.
  • Very strange indeed. Yes, please try a fresh download, this time and try this: Reset the profile for the MCP first to FS default, then go into detective and click the red x to clear out all bespoke events. Then import the new bespoke events and finally import the MCP profile again and see if it is working. 
  • Hi Roger. On the previous version I mistakenly left the speed rotary at the default setting because I hadnt programmed anything to it yet. On the Dash 8 the pitch wheel will set the speed and the vertical speed. I set it up on the MCP Pro to operate like it does in the virtual cockpit. First press the VS button then use…
  • No problem. The biggest issue was the missing Lnav which you kindly pointed out. This is mainly for those who are just using a stock version of what I initially made available or for someone new. If you have spent a bunch of time customising it to your particular hardware then I advise against updating. 
  • If your config is intact and the bespoke events still show up in detective it is likely something else. Had you installed or changed anything other than the profile? I've had Goflight hardware become non responsive before if I let the computer go to standby then wake up, usually a full reboot fixes it. I don't have any…
  • Keep what you have. You would loose your custom stuff like the radios. You've already done most of the things I put in this version
  •  With your APU you have to push the start button twice. You still have to follow the logic of what it does in the VC. As I said think of it as you are in the VC clicking it with your mouse, whatever you have to do there is what you have to send that mouse event, some dials let you use the scroll wheel on your mouse too,…
  • Ok 6 is the number of the mouse event that you see in the detective mousevents. The other number computes to a left single click and a right single click. WHen you pick left or right click or whatever in the dropdown , the code it spits out is that number. in the case of a button most times it's either a momentary…
  • Clearly a case of rtfm. I honestly never knew that 8p
  • Just flip flop the bespoke events for on and off positions
  • Actually I just found Nav source really fast...it's mouse click 6. send it MOUSE_FLAG_LEFTSINGLE and MOUSE_FLAG_RIGHTSINGLE. You need 2 bespokes one for sending it the left and one for the right then assign them to CW and CCW of the rotary and you're all set.
  • Hey Dave, the TOGA button is easy You were on the right track. Here's what I use: MCJ_VAR_WRITE_VALUE = 1MJC_VAR_WRITE_CODE = 27120 While your at it you might want to assign an AP disconnect button too, that one is already in the profile it is named MJC_AFCS_AP_disengage (thats the red button on the yoke) That Nav source…
  • If you don't want to wait just assign the MCPPro LNAV ON position the bespoke even MJC_AFCS_NAV, leave the OFF to nothing(the same keypress toggles between LNAV and WING level in the aircraft). There is no light for it because the button doesn't light up in the real thing it just shows LNAV on the display...
  • I was thinking of assigning the Nav button to the LNAV and BC to VOR/LOC but I seem to have forgotten to do it before I released the profile. AP_NAV_SELECT_SET was just in there because it was default( I didn't set it to _NO_EVENT - which you should do for unused buttons) Edit: the NAV and BC buttons are in the profile, I…
  • Have you ever used teamviewer Bob? I can probably give you a hand if you are struggling with the profile.
  • That's great news. I like X-Plane too but it's just not as good without the hardware. Looking forward to it. 
  • If you have the MCP Pro, I assigned light switches to the 2 FD switches and A/T arm since they had no function in the Dash 8. It might be that we are using the same function twice so it's ignoring the input when you set it up on your switch panel. I'm almost sure that's what the problem is. Go ahead and set those 3…
  • Steve, the Pro works fine, that's what I'm using. I suspect there are more things that are unpublished as that spreadsheet looks like it was made based on the non-pro version but the core between the 2 versions is the same. I can see nearly 1000 (!) mouseclick events that we can hook into using your program...it's just a…
  • You can search the LVARS in detective It's the fastest way to locate something. If you want to know WHAT to send usually with rotary it is 1 or -1 as in the example. You will have to refer to the varlist.xlsx spreadsheet where you look up the names to figure out what are valid values to send (BOOL, INT, etc.) If you let me…
  • Seems like I couldn't find a variable for the light on APP. I just scanned over the spreadsheet provided by them and didn't see it. I could implement it if I knew the variable.
  • Sure there is. You will need to create a bespoke event in the detective and use the sendkey function.
  • They will turn on and off based on the aircraft power. Have you read this? http://www.pollypotsoftware.org.uk/support/user-guide/user-guide-git/19-operating/33-aircraft-power.html Also you may need to shut off the gofilight driver or it may turn on the radios anyways, see this thread a couple below yours:…
  • People could still use the older versions of the software if those are the platforms they use. I would keep a download link active and just make a note that it is EOL and no further development will take place for 1.4 and 2.0
  • Most people forget to import the bespoke events. Once you do that it should work. Once the aircraft is running in the sim, open the detective and import(button on bottom of detective window) the file contained in the zip(mjcQ400.xml) I know it works on pro as that is the last version I created this using.
  • I've seen it have all zeros before. It's because of not being set to compatible addon in GFConfig. Make double sure you have your P3D entries set correctly in options /program locations. Especially if you have 2.5 and 3.1 installed as they are not the same directory.
  • Don't use your Goflight hardware on USB 3.0 ports, use 2.0 ports or get yourself a 2.0 hub. Goflight will tell you as much if you ask over there. They may or may not work. It's a crap shoot.