robains
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.
robains
Comments
-
Hi Steve, I did notice GFWindows8Fixer, but was hesitant to run that on Windows 10 ... probably should be part of the GF 2.26.x installer. Cheers, Rob.
-
Win10 is still "Beta" as far as I'm concerned, I've endured a lot of Win10 issues over these past few months ... don't know why I thought it would be any different at Redmond. Here's the deal with disabling Power Management, after you go thru Device Manager and do a properties on ALL your "Input Devices" and HUBs and…
-
No issues with GIT AND V3.2. See my other thread on MESM issue with GF 2.26.1 and Steve's latest GIT. Unrelated to GIT and P3D, but also found resolution to older GF modules under Win10 (like 166A units working but no display) ... this process solved it: http://forums.x-plane.org/index.php?showtopic=71640&p=774354…
-
Let me know what you find out Steve ... it's odd that my power cycle issue also stopped when I disconnected the MESM. The MESM does seem to show up just fine in GFConfig, but for now I'll keep it disconnected so my other GF modules don't power cycle continuously. If you have any line to GF, would love to get their thoughts…
-
Will do, give them a call on Monday, email with GF seems to get lost. Cheers, Rob.
-
Opps, didn't see this until now ... late ... but will test out 2.1.19.4 Cheers, Rob.
-
HI Steve, Wow, thank you!! Downloaded ... will test out. Just finished building my uSimPit ... all good except one of my RP-48's is stuck in a continuous power cycle (tried different USB hubs/ports still stuck in power cycle) ... I just added a new RP-48, my 5th unit and now my oldest RP-48 (black) no longer works. Is…
-
Hey Steve, 1. Interesting, so it sounds like the serialize to xml references in your code (assume you use System.Xml.Serializer) is operating differently on my system ... this could be a clue to not being able to use latest GFDev with GIT. 2. If I enable Panel Serialization in P3D V3.x, save a flight, exit P3D, load P3D,…
-
UPDATE to Issue1: In further testing, it looks like the XML files exported from GIT have no CR/LF which seems to be the cause of the error message. If I edit the files using Ultra Edit and convert it to XML with CR/LF and save, then the GIT import works. Cheers, Rob.
-
Curious also, having some issues under Win10 and GIT is removing entries, definitely does NOT like Captain Sim aircraft. Cheers, Rob.
-
Before you toss it ... I'm connecting to a separate USB 2.0 PCIe card ... are you connecting directly to the motherboard? Cheers, Rob.
-
No issues with any GF modules (including 2X GF-46) in my Win10 install ... they are actually working better under Win10 than they were in Win7 (in Win7 they would tend to power cycle, that doesn't happen in Win10). Couple of things to check: 1. Try GF 2.25.2 drivers (using with GIT 2.1.18.2)2. Powered HUB run from a USB…
-
So far the issue is specific to Saitek Throttle Quadrants ONLY (my other Saitek Yoke and Rudder Pedals work fine) - I suspect because I have two of them and Win10 gets confused so just picks the first it polls as #1 and the other as #2. I've heard of SPAD, will take a look. Cheers, Rob.
-
Hmmm ... that's a loaded question. Benefits:1. LM are developing on Win10 boxes2. Microsoft care more about Win10 than Win7 (think Windows updates)3. DX12 (not much using that API yet, a few early access) will be big benefit for future graphics based apps4. The User Interface is really very much like Win7 now with a few…
-
SOLVED: Probably should stop posting updates ... but in case anyone reads this and makes the same Win10 mistake I did ... Source of the problem was checking "Run as administrator" in the "All users settings". This is fine, however when I click on the "Change settings for all users" I had also checked "Run this program as…
-
UPDATE: The problem returned again GFDevP3D will not load when P3D starts, permissions are set ... this one has me baffled and why is it not consistent? And now I'm running into issues with my Saitek throttle quadrants, my two USB Throttle Quadrants keep showing up with different names each time I reboot Win10 ... causing…
-
Cool, thank you ... on my migration to Win10 I had accidentally forgot to copy all my GIT files over to my backup drive so they got wiped out ... I have another backup from Nov 2015 but it's missing all the recent Q400 mouse event stuff you helped me with. Oh well, start over. Cheers, Rob.
-
Thanks Steve, I probably just got distracted when testing all the versions to see what works and doesn't and forgot my next step on return. It would be nice if GF could provide some drivers that work with GIT and/or visa versa. But just curious what GF change for the 2.26.1 drivers that makes them P3D V3 compatible?…
-
UPDATE: Resolved GFDevP3D not loading ... the magical reboot or moving entries to the ProgramData versions of DLL.XML and EXE.XML ... and now it's working (not sure which solved it). So GF 2.25.2 and GIT 2.1.18.2 are good to go in Win10 E. Also to note in P3D V3.x, I'd recommend you do NOT use the DLL.XML and EXE.XML…
-
The issue with 2.25.2 seems to be any key sequences sent (i.e. S to cycle views) will repeat ... i.e. hit the an P8 button once and it will generate 4 or 5 "S" key sequences in P3D and hence I'll cycle 5 views rather than just one. Another issue is 2.25.2 must be loaded manually first prior to running P3D ... it seems the…
-
FYI: Forgot to mention that GF 2.26.1 drivers would NOT illuminate each device when selected via GFConfig ... so with multiple devices of the same type it was impossible for me to determine which one I was actually setting until I was in P3D testing them. With GF 2.25.2 drivers I do not have this problem, all devices…
-
I'll be moving to Windows 10 once P3D V3.1 releases with clean install of everything ... will test the 2.26.x drivers again then ... as I understand it Steve, you don't have any issues with GF 2.26.x under Win10? Perhaps this issue is some element in the registry that's left behind even after a full uninstall and dir…
-
Unfortunately no luck ... same as before :( Cheers, Rob.
-
Glad I spotted your post Steve ... will give these new GoFlight drivers a try. Cheers, Rob.
-
Google sheets sounds great, we can all add to it. I love the Q400 even though it's not fully V3.x compliant yet it's still an amazing aircraft to fly ... talk about challenge. I don't have a "simpit" ... I'm too much of an aircraft HO (too many aircraft too little time) to bind myself to any single aircraft layout. I might…
-
Awesome, thanks Steve.
-
Looks like events 157-160 are the 4 OHD dimmers ... pretty easy to best guess. In action:https://www.youtube.com/watch?v=lKF0d5yBpCg Thanks again for all the help. Cheers, Rob.
-
On a side note: love the MJC Q400 Pro ... still some things to resolve for P3D V3.x but should get resolved in V3.1. But the Q400 is by far the most challenging aircraft I've flown, you really have to be ON YOUR GAME for single pilot, it can get very busy very quickly. But thanks again for the tip, I'll trial and error…
-
Yes, 157 Mse Clks does indeed work ... many thanks. However, how does one determine what mouse event ID to uses for each knob, trial and error? Cheers, Rob.
-
I tried electricsData_->control.instlight_ovhd returns CRC 76234 All I've been able to achieve with that is to turn the overhead lights off. Value itself looks to be a double with a valid range of 0 - 100. I'll fire off an email to Oley and see if he has any input, he owes me a response. Cheers, Rob.