Emile
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.
Emile
Comments
-
Indeed, because GF website was offline for more than a week I thought they were gone completely. Good to see them back again. I also cannot explain why the Samsung drivers would mess up things (I connected the phone only for a short time and saw the problem with the GF displays the next day, after starting the computer…
-
To follow-up on my own question: After a very long evening I figured out what happened but I still don't understand. The day before I connected a Samsung phone to my computer and that installed some Samsung drivers. Apparently these messed up the GF displays because when I reverted to a restore point everything worked fine…
-
Hi, it works on the device, but to see the actual active configuration would help in creating and debugging the commands. -Emile.
-
... after writing this I realized I could do better: calculate the number of required clicks (-3..3) depending on current knob position. That gets rid of the flickering effect of my previous solution. -Emile.
-
I see, thanks. I'm also using the detective a lot. One thing I noticed: in the mjc8q400.xml file I looked at the logic for handling the NavSource-button (starting line 1436). I was wondering about the strange numbers like -0.75 and such. What I think is the case is that the button uses -1 for one click to the left and +1…
-
Hi, I would be more interested in documentation or help on certain Q400 functions since I decided to switch to Lua programming for the Q400, because the Q400 requires quite some advanced actions and I need Lua anyway to program my CPFlight MCP. The mjc8q400.xml you sent provides excellent information. Did you find those…
-
Thanks a lot, this was the information I needed to get going! I got the transponder mode working now. The delay between pressing and releasing the button must be at least 1000 msec to change the mode. For others reading this: the current transponder mode can be read with code 42187 (Nav_->atcTransponders[0].mode 0 -> STBY…
-
Press and hold a button for the "FORMAT" button works fine (using EFISdata_->EFCP_controls1.button_FORMAT_pressed) but I can't find the LSK8 button name on the ARCDU. And then, because I want to map this to a T8 toggle switch, I would need to get the Transponder mode from the sim to see if toggling the switch should indeed…
-
Works like a charm! Thanks a lot! -Emile.
-
That's it. *blush* -Emile.
-
Thanks Steve, it works fine! However, I do get errors when starting GIT2.1.13.0 but I'll start a new topic for that. -Emile.
-
Thanks! -Emile.
-
Thanks for the investigation, but I do not agree with your findings. I did some more experiments and found that the problem is not related to the COM functions at all. If I set the Light Data and Actions to show e.g. the NAV_SOUND1 or 2 activation, it only shows the NAV_SOUND1 activation, even if I switch to config2. So I…
-
Indeed, that variable can be used too. However, the problem remains: there is no difference in light behavior between config1 and config2. Am I right in assuming that the input selector BUTTON_LEFT1 makes the Light Data and Light Action fields refer to the left LED in config1? -Emile. To summarize, my bindings are…
-
Thanks for the clarification, that makes sense. -Emile.
-
Yes, that solved the problem. Wow, I'm impressed with your quick response. Best regards, Emile.
-
The windows update could very well be the problem indeed. I remember that I got an update too. I'm not 100% sure that was the breaking point but might be. Thanks! -Emile.
-
No, I did not install any aircraft, only working with the aircraft that are part of P3D. Not installed any other scenery either.