JoyShockMapper VS XOutput

Here's jsm if you were serious Joyshockmapper

The paper you linked is more of a conceptual explanation for design and implementation of systems into games. To learn how to use JSM itself there is a guide for its functions on its GitHub page. The games database may also provide you with some ready made scripts for you to use and edit to your liking.

There DS4Windows, Steam Input & JoyShockMapper. The easiest way to setup gyro would be DS4Windows, JoyShockMapper would be a involved(relatively) but offers way more customization. You can grab a community config for gyro from steam if you choose steam input.

There's also this https://github.com/Electronicks/JoyShockMapper but i'm not sure if it would work with stadia controllers it might work with the dual shock ones

Non-trackball gaming solution: Use gyro on PS4/5 controller with JoyShockMapper. If flickstick doesn't float your boat, maybe a Steam Controller if you can find one for a reasonable price, with trackball emulation enabled it's basically a thumb ball, and when your thumb gets sore start using gyro.

Is it possible to use gyro aiming + flick stick with any xCloud games, or are we forced to use the analog sticks? I have a PS4 controller (i.e. it has a gyro) and tried using JoyShockMapper, but this doesn't seem to work. It modifies my mouse pointer but not my in-game aiming. Has anyone had success with this or an alternative gyro aiming software package when playing on xCloud? Thanks.

Using the software JoyShockMapper's "motion stick" and the simple config below, I bound pitch and roll to WASD. I was able to just use it exactly like I use the 3DRudder. This software can create a virtual controller, so it is also possible to output analog joystick motion. You can map yaw to something as well, although gyro controllers generally lack a magnetometer and yaw might drift easily.

I have also heard really good things about JoyShockMapper, which is both free and open source.

Xoutput - is maybe the simplest but x360 only.

I've been playing with using XOutput + HidHide to cause Windows to see the the ALP controls as an Xbox controller instead of the generic device it normally appears as, and it seemed to significantly improve the input latency in FX. But there are other downsides and quirks that it causes, including problems actually launching the ball in some of the FX tables, so it might also end up being a non-starter.

I’m using this as a hub for mainly a GameCube emulator and those controllers do not have Xinput so it wont work in Playnite. I used this to map the controller to XInput and then added an extra line in the Launch Playnite.bat file to also open XOutput on startup

Does your ipac have a dinput mode? If so, xoutput may work https://github.com/csutorasa/XOutput/issues/210

I know a fair number of people would like to be able to use their HOTAS with NMS (plenty pancake players, not just VR players who dislike the virtual HOTAS we get). A problem for PC VR players, though, is that any solution might leave you stuck with the HOTAS for all play and that wouldn't be so great. But I've seen a couple of people in other subs say that they use XOutput for this and that it lets them switch seamlessly between HOTAS and motion controllers, detecting when they put one device down and pick up the other.