I notice that several of you are having problems binding controllers to MSFS events. This is one of my pet peeves. It used to be that a throttle was a throttle, not anymore. There are a dozen MSFS events designated as throttle control. Then, some developers set the throttle, and other controller functions, to LVARS.
I don’t use the built-in bindings in MSFS. I set everything, with a few exceptions, to BLANK. I then use either FSUIPC or Axis and Ohs to assign the functions to my controllers. I have recently purchased SPAD.next, which is very powerful but complicated. I use it to assign my Go-Flight controllers rotaries.
With the above programs I can assign the numerous controllers to whatever function I want. The profiles assigned to each airplane will load with the airplane.
John
***************************
My first SIM was a Link Trainer. My last was a T-6 II
AMD Ryzen 7 7800 X3D@ 5.1 GHz
32 GB DDR5 RAM
3 M2 Drives. 1 TB Boot, 2 TB Sim drive, 2 TB Add-on Drive, 6TB Backup data hard drive
RTX 3080 10GB VRAM, Meta Quest 3 VR Headset
Hi Dave,
Sorry for the late reply - was a few days before I could get to the sim and monkey with it. In the end, (remember, I'm a MSFS noob) I realized I had misunderstood how the MSFS custom vs default profiles work. I erased the profile I had been trying to make work and started a whole new one, and everything works as it should. Yes, as you say, the hat now works for panning in both external and internal (VC) camera modes - you have to override the warning. I still haven't figured out how to call up the GPS like I did in FSX / P3D, or open doors (looks like that disappeared, and only possible if you can open / close from within the VC itself?) - but I'm mostly there, when it comes to stick setups. Oh, the sensitivities were massively off - had to really dial them down to attenuate all the crazy PIO - can't imagine why they're that bad by default.
thanks!
dl
Bookmarks