MSFS 2020: Mapping cockpit interaction axes to VBK Gladiator NXT ministick

[P-Rock]

I’m trying to map the mouse cockpit interaction controls to the ministick on my VKB gladiator NXT. I mapped “cockpit interaction” x and y axes to the stick just fine, and I can see it detecting the input in the game, but when I go to actually use it in a cockpit, nothing happens. I looked at the mouse mapping, and it seems like these are the controls that need to be mapped. Is there any trick to getting this to work? My ultimate goal is to be able get all the mouse functionality mapped to my HOTAS setup (an NXT and TWCS), so I don’t need to grab a keyboard or mouse when I’m flying in VR

[fallout9]

Better program your ministick as mouse, here's how. But this would work only on the Premium version of the grip, as the Standard version comes with a HAT switch and not a ministick.

[P-Rock]

Yup this got me 80% of the way there--Thanks! A followup question: is it possible to set a response curve for the mouse? I played around with the dead zone and speed settings, and while they helped, the stick still doesn't quite "feel" right.

[fallout9]

Sorry, no curve; the only adjustments are Speed and Delay.

[Ron61]

Since the mouse axes are controlled by the ministick axes, if you adjust the curves for these axes, the mouse will move accordingly.

[P-Rock]

Yea I figured out that if I adjusted the curves for axes 5 and 6, it had an effect on the mouse mapping. One thing I'm a little unclear on--both the axes and the mouse have deadzone settings, and changing the deadzone settings on the axis has a definite impact on the mouse control. If I set Dz Lo to 0 for axis 5 and 6, then I get mouse drift with the ministick control (as I would expect). So do the mouse deadzone settings in the POV tab apply on top of the axis deadzone settings?

[Ron61]

Show your axis and mouse settings from the configurator. This will be more accurate.