Wostg

Wild, that's my password too!

Anything funny with the DCS bindings for headtracking in the controls setup? You could clear them out and see if it still crashes, put them back one by one etc.

This is a great idea, loading the last map you used in the QAG is causing me no end of grief and I'd rather just not use the QAG. Either no map or Caucasus seems sensible, given the load time problem.

lol I was going to ask you the "stupid questions" but your OP was so detailed it sounded like you'd been through all that. Good stuff

Weird! Try deleting the HID devices by name / unknown devices from the Windows device manager?

Yeah DCS' direct feedback was fine (well after I reversed the roll axis) but the Moza telemetry was stubbornly conflicting with DCS so if I trimmed 45° forward, the stick would automatically throw itself 45° right of centre. Its not worth losing the vibrations for so time to look at that dremel...

This is a guess but DCS-BIOS suggests the names for the modules might be "F-14B", "F-14A-135-GR" so try that for the A

Right now its sitting in front of my seat with a gooseneck extension, will lock it down when everythings ok. First try with the Apache seemed fine, using the Hind preset and felt like the trim etc worked alright. Second try with the Ka50 not so much, the Moza/Integrated feedback is on the wrong axis so if I trim forward it trims left.

Did people figure out if it can be configured to run sideways? I need that extra half inch (...) / cables out the way E. It can't be as simple as switching the axes in dcs surely?

When the mode switch function is activated in the VPC software it will hardwire the 6 led buttons to different assignments based on mode. (as opposed to the dial just being 5 regular buttons if set that way). You can choose either mode in the VPC software. I think guy above is probably right though. You can set, say, the flap axis to pretend to be buttons. So if the A10 had no flaps axis but DCS did have up/mvr/down buttons: you could set say 0-10% to be flaps down, 10-90% to be mvr, 90-100% to be up. Those would show as your missing 3 buttons. Probably.

I haven't counted up the numbers on my fingers but I'm guessing: "5-WAY MODE DIAL Configurable as either 5 independent button inputs, or as 5-way shift modifier, allowing you to configure up to 5 actions to every input. You won't run out of space for your keybinds with the MongoosT-50CM3 Throttle."

Oh yeah what he said ^^^ that bitrate was too much for my system so I just meant don't forget to find your sweet spot

Hopefully forums legend @prestonflying has you covered: Try the settimeout Fix?

Also for whatever reason it seems (on mine at least) that the comment line 'default moza algorythm (sic)' needs to be left as is, as much as I want to correct it

I tried it and refunded, the headtracking was just OK and the supposed eye tracking I'm pretty sure was a huge hassle. Honestly I'm 100% satisfied with a dirty old ps3eye cam and opentrack's neuralnet model using (and this was key for me at least) the large-head-model (or whatever it's called) hidden in the nn settings. I got the cam for a delanclip years ago, which wad good, but see no need to ever go back to it.