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.
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
-
The old way doesn't work in 64 bit for an unknown reason, so my old profile had to be redone. I started experimenting and found that the fake LVARS did work though. The two are not compatible and cannot be mixed together at all. Mouse events still work with both versions except I still haven't mapped them all out yet. My…
-
Steve did some testing on his end, looks like a Majestic issue or code change causing problems. I was going to post on their forum for a bug report but forgot. Ill ask over there when I get home from work.
-
They are hard coded into git, so no need to do write / read codes anymore, he basically aliased those into LVARS that you can directly access in the detective and they match the list provided by Majestic.
-
edit: I wonder if you could make a script in LUA that would take a keyboard input - that would be cool but I don't know if it can be done. You would just need a short delay between sending each digit.
-
the dataref you want to write to is xpndr/dig only send it one number at a time with a short pause in between, once you've reached the last digit, it will start replacing again from left to right. The default x-plane datarefs , although they do get written to , are secondary. in other words modifying xpndr/dig will set the…
-
new beta, partial EFIS , new blanking routine.
-
flakster , when I run into that situation and acceleration doesn't seem to work , sometimes it's just as easy to find the commands that rotate the knob left/right and use those instead of hitting the dataref directly. Then you will be using any acceleration routine that Laminar or the airplane developer put in by default…
-
I remember when I made my profile I considered putting that in. There is a way to do it if i remember correctly. You will have to go hunting with the detective because that is not the only dataref you need to work with. Need to reload that aircraft again and take a peek. It would require several if statements and some…
-
I only have P3dv4 installed anymore , no way to test
-
Ran into a snag with the EFIS stuff lots of it not working as expected. Some of the Fake Lvars are firing the wrong buttons and mouse clicks aren't working right for some of the buttons. I'll ask Steve to look at it: For instance I tried EFISdata_->EFCP_controls2.button_WXTERR_pressed is pushing the FUEL SYS button instead…
-
It's not working on my end either nor are the fake Lvars EFISdata_->EFCP_controls1.button_WXTERR_pressed or EFISdata_->EFCP_controls1.button_FORMAT_pressed
-
New version with push/pull as discussed above, had to add a bit of logic so that it will not fire the quick push before the long push(pull). Some display blanking ( works but not quite right yet) Both FD and AT switches now working with indicator lights. Currently using the CWS buttons for the push/ pull feature of the VS…
-
Bill. Almost everything that I use is in the profile, what additional buttons and switches do you want to see included? Post a list of what you would like and I'll put them in.
-
Got sidetracked with the FF757 and FFA320. Haven't done much on this but I'm off the week of Christmas so hope to finish it then.
-
How would you guys like to see the push/pull functionality of Airbus knobs handled? At the moment I'm just using the push. I've considered a few ideas such as a quick push would be the normal push function and and push and hold would be the pull. Possibly could use VNAV/LNAV buttons for managed modes too. Also the VS is a…
-
Maybe when they release it for P3D V4.1 :)
-
I just noticed an issue. if you use "modern EFIS" setting in the aircraft my EFIS config doesn't work properly( I made if based on the default setting) I'll have to make a 2nd EFIS profile for the "Modern" setting as well. I knew this but totally forgot about it over the past years. Easy fix.
-
Start GIT, the sim and load a default aircraft. In GIT there is a tab for each device. Pick the Mcppro tab. In that tab there is a dropdown. Set that to enabled, then click the default fs button. Not all devices have the default fs button.
-
Ignore the exception received. When working with NGX , you can't use detective , it's hard coded. after you loaded a default aircraft did you try to load a default profile for the MCPPro by hitting the default FS button? Otherwise there is no profile and nothing will happen.
-
File
-
New Version - This one should work with all previous versions of the 757 and the new 757 V2 extended etc. The name has been shortened to work with all the variants.
-
I found the problem. GIT is not detecting some datarefs that it did before and since they are not listed in datarefs.txt the program deletes all the code from the offending bespoke event. a workaround is manually adding these datarefs to datarefs.txt and then delete/reimport again.
-
Steve: The import is failing and leaving some BE's blank that I used in the EFIS. If I delete all BE's the reimport them the aircraft works fine for that session only. Once restart X-plane/GIT it errors out and deletes bespoke events again.
-
GIT doesn't like something. Now it won't import properly on my system with a shortened name either. Going to have to troubleshoot with Steve on this further when I have more time. Heading out for the day now.
-
try using this. Working here. Use import wizard.
-
Try loading the 300 then import the 200 profile again using the wizard.
-
I actually upgraded as well and it worked . Load the-200 shorten the name click no on both questions.
-
Yes, since the aircraft name is slightly different what you need to do is shorten it's name in the profile so it will work with both models. so instead of 757-200v2017 , shorten the name to just 757. There are instructions on how to do it in the GIT documents here on this site.
-
Some buttons and switches require a left and right click, some just a left click will cycle the switch. Depends on how the programmer set it up
-
Copy that bepoke event , rename to apu off or whatever and then edit it to a right click instead of a left. Then assign that to your off position for your switch.