jimh20 wrote:I don't have any VAS problems at all with it.
Huh. If only we could find out why the controls work for me and why you've got enough VAS, then we both would be happy.
I'm having a hard time understanding how the Legacy could have such an impact on your system, unless something went seriously wrong during installation. It doesn't do anything special concerning controls, right? The only dll it installs is just used for audio effects, as I understand it.
I remember that the controller settings I applied following the RealAir manual (deadzone, sensitivity) didn't work out for me, so I returned to my previous settings, but they didn't render my controls inoperative, they just messed up my brakes. Since then I switched to using FSUIPC for controller configuration, mainly because it offers better support for my HOTAS and I prefer its precise calibration.
In the Legacy the 750 was black and dead, and the 750 was the same in any aircraft I tried following the Legacy, both in the Rift and in P3D started directly.
I only get a black GTN750 when I put it in a detached window. When I close that window (not when I "hide" it!) the display in the cockpit lights up. But that doesn't seem to be related to your issue, because it would be hard to overlook that detached window in "flat" P3D.
Did you check whether the controller and GTN problems persisted when rebooting the system?
About the VAS issue: I've done a bit of testing there during the beta. When I load the Legacy without GTN in FI, I'm seeing about one GB more VAS usage than with other aircraft I tested, and it eats more VAS in VR compared to "flat" (ie. the difference between "flat" and VR is significantly higher for the Legacy than for other aircraft).
When I add the GTN750 to the Legacy, FSUIPC often gives me an OOM beep during loading (because available VAS drops below 300 MB), while the effect of adding the GTN to any other aircraft is negligable. With the Legacy with GTN, VAS recovered after loading from about 200-400 MB to about 800-900 MB, which is just barely enough for shorter flights. I experienced a series of OOM crashes before I started logging VAS (using FSUIPC) and discovered the Legacy's speshul behaviour on my system.
Since you didn't have my problem, and I didn't have yours, I'd suggest you give the Legacy another try, assuming that perhaps something was somehow awry during the first attempt at installing it?
(I recently migrated from FSX:SE to P3D, so I also started with a fresh install and the Legacy was the first aircraft I installed.)
PS: Thanks for the heads-up regarding the "other" Legacy!