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

  • > @avelaz said: > @Slayer, > > Thanks for your response. > By any chance you have that excel file? > Do you remember why you created the START Bespoke Event? > > Thanks! Start handles a bunch of things like VS blanking and on off states since they are tied to other things than just an on or off states of a switch.
    in QW 787 Comment by Slayer May 2020
  • Been busy with RL have barely touched my GF gear in the past year and a half. To answer your question: There was no sim builders document available when I started working on this. I used the detective and started seeing what events were used when I pushed certain buttons etc and compiled them into a spreadsheet. Needless…
    in QW 787 Comment by Slayer May 2020
  • Use the download from December mjc8q400
  • I've got a version on my setup as well but I hadn't released it. I'll see if it still works on P3Dv4 and X64 because there has been quite a few updates to that aircraft.
  • I never get that warning either so I don't think that is an issue. Do you have any other aircraft that GIT works with? Are you for sure using the latest x64 version of GIT?
  • Another "beta". I'm not going to do the full thing with radios as I don't use them anymore but this version has a few more fixes. Some buttons light up when activated, EFIS range etc works , YD and AP lights don't work properly yet but nearly everything else does. Please don't pester Steve from Pollypot about this as it's…
  • Hmm I just updated the aircraft and put in the connector again I downloaded 1.16 from github and my screens are fine but on the bad side I forgot X-updater erases everything so I lost whatever was done between what is posted here and what I had :( Someone else had the problem of green screens too but can't remember the fix…
  • WIP Here preliminary ( alpha) some lights not working properly and a few little glitches , IAS blanking on this aircraft is a real hassle the way they coded it so I abandoned that for now but the blanking is working on VS displays. Ignore the course indicators for now as I was using it for debuging some things. EFIS is…
    in QW 787 Comment by Slayer June 2018
  • Grr... just lost a bunch of work because I didn't export after programming and GIT crashed and deleted all my BE's I made for the EFIS...I'll post something when I have time to remake it..
    in QW 787 Comment by Slayer June 2018
  • This aircraft is probably one of the more frustrating ones I've worked on in a while, even with the patch some stuff will just not work properly no matter what I do. Mainly it is the button lights that are holding me up so I'll probably just disable the ones that I can't get right and release a profile that is functional…
    in QW 787 Comment by Slayer June 2018
  • Got it working by switching the variable then exiting/restarting GIT...weird. What I can't still figure out is what the IAS_MACH_BLANK flag uses to determine to show airspeed or mach?
  • Some differences between MCP's on this aircraft. Would you rather see the heading select as a knob push or the hdg sel button? I prefer the HDG sel button on the goflight to represent the HOLD as it seems to make more sense as there are not enough buttons and it would work closer to the real thing. Also thinking to use the…
    in QW 787 Comment by Slayer June 2018
  • Only doing the MCP and left side EFIS, it's kind of a pain as I'm finding it's coded a LOT like the Milviz 732 and that was a hard one to do also. I'll put it in this thread for some testing if you guys want. I'm at about 80% done on MCP today but haven't done any real testing to see how well it works. Their mouseclicks…
    in QW 787 Comment by Slayer May 2018
  • Working on a profile for it B)
    in QW 787 Comment by Slayer May 2018
  • Don't think you can put trim on a rotary in the Airbus since its FBW trim inputs get sent to the computer(digital), the trim in the real thing is momentary switches not an axis like a Cessna where it is directly connected to the flight surface(analog).
  • Acceleration is not working with rotate set using stock Xplane datarefs. A little bit better if I put the sliders for the MCP near zero but seems like it worked better before. Actally they may be built in commands. Hard to tell..
  • if you do it the manual way need to open detective first and import the bespoke events first. Also need to restart GIT after that because there is a start event in there.
  • Most of the MisterX6 airports are using autogate KBOS, KLAX etc. They all use autogate and include a plugin within the scenery folder.
  • I just remembered something with IXEG. Had conflict problem with GIT and autogate plugin (that is sometimes included in free airports,so clearing plugins folder will not fix because it loads from scenery). Can you please post a copy of your log.txt from xplane.
  • Yes I recently reformated my HD bit not my xplane hdd so I had to import it again but I didn't use the wizzard.This profile uses a start event so the first time you import it I believe you need to restart GIT so it works properly. I think you might have to manually copy over datarefs.txt and commands.txt to the aircraft…
  • naser do you have xplane 10 or 11 or do you have both installed?
  • that aircraft will not work without Gizmo unfortunately. I had updated my IXEG too but npt having a Gizmo problem. We had a similar issue when I first made this profile. have you loaded the IXEG without git to make sure its activated?
  • Try right clicking the zip file for the profile and go to properties on his PC and see if there is a message about " This file came from another computer and has been blocked" and click the unblock button..
  • I can confirm that the IXEG is working still in XP 11.11 Almost every time I see that GFDEVHWTYPE_ error message it is mostly due to a failed import, corrupted file or an aircraft got updated and it can't find the dataref anymore. This sounds like a windows permissions or Defender issue. Is he running under an admin acount…
  • Good to hear. Been busy with other things so I haven't had time to work on this a lot lately.
  • Nope, no stock datarefs. Need to use a plugin from a guy named Mokney over at the .org and create all your own datarefs, then create a GIT profile based on that. the A320 was originally made as a trainer for real pilots and is being adapted to X-plane so it has its own program code outside x-plane. Maybe in final release…
  • On the first attempt it shows aircraft switched again after the Q400 loaded. That's why nothing would work. Not sure on 2nd attempt. Try starting GIT after you load up the Q400 and also maybe try running as admin if you don't already.
  • Maybe to short of a delay in start. Are you guys using 64 bit GIT or 32?
  • According to the latest spreadsheet those two buttons are just bytes. Send it a 1 to push the button then the aircraft resets it back to 0 automatically. There is quite a bit more info in that spreadsheet (including values its looking for)but the last update was December 2016
  • In my experience its best to restart the software before you setup for a new flight