remember, your not spending $450....
...your spending $450 PLUS the cost of rudder pedals.
The Saitek X52 at least has twist, so your not totally SOL in the yaw dept. Still, once you've gotten used to pedals, there's really no going back.
I've already got pedals. I have Saitek's Pro Flight Rudder Pedals. The one thing I was hoping with the G940 purchase was that I could transition my whole Saitek setup over to my spare computer so that my cousin could fly with me in the same room with rudders and all. He's an actual pilot so I know he prefers pedals to twist.
FYI - Notice that you find the same problem with Warthog + 3rd party pedal. They are show as two separate controllers for Windows/Games.
No issue with CH gear...
That is very true. I had forgotten about that.
I left this post open for about an hour and thought about this issue. I believe that this problem could be overcome by using PPJoy and GlovePIE, using a very similar method as to how I solved the issue of not being able to use Tactics abilities for the entire joystick using Black Prophecy community.
Basically, it goes like this:
Create a script in GlovePIE that redirects each axis of the joystick, throttle, and rudder pedals to the virtual PPJoy controller. This way all physical controllers can be seen as one controller in Windows. The problem you run into then (aside from the maximum of 8 axes) is assigning controls in the game. When assigning and you move the physical axis, the game would probably see both the real and virtual axes moving at the same time. Which one will be detected first and registered? Who knows. It would probably be a crapshoot. But to overcome this, and this is the clever bit, you need to create a second script in GlovePIE with the sole purpose of using it once to bind all the commands in-game. In this second script, you would assign each virtual PPJoy axis to something that is not an axis, like a key on your keyboard. Then you go in-game, assign the proper axes, save the bindings, stop the second script, and run the first. Voila. Now your game sees multiple axes from multiple controllers as one virtual controller because it's only expecting input from the virtual controller, whose virtual input is being provided by physical controllers. This is what I did to solve the Tactics issue with Black Prophecy. Actually, if I remember correctly, you might be able to assign the physical axes to the virtual ones in PPJoy itself. This would save you the trouble of needing to create the first script. Not certain though, since I haven't used PPJoy in some time now, since I stopped playing Black Prophecy because the developers have stopped supporting the joystick using part of the community.
I now realize that this could have solved my biggest issue with the G940, and probably would have kept me from sending it back. No biggie though, I wasn't that impressed with it anyway.
If my carpal tunnel wasn't flaring up enough to make every single movement with my left hand send shooting pain all the way up to my bicep right now, I'd get started on this immediately.