MarkDH

Surely the simpest option is to leave the throttle connected to the yoke and just put the yoke somewhere out of sight if you're using a different one?

You make it sound like SPAD.neXt is required. DME already works with the standard Logitech driver.

Yes.

But surely this is by design? Milan has produced a very carefully-engineered choice of physical cams that can be swapped in and out to modify the mechanical feel of the pedals. For example, the standard CAM4 is said to offer a less-realistic but more-usable compromise for flying GA aircraft, specifically because it is softer out towards the extremes. (The optional CAM5 is said to be more realistic but is stiffer at the extremes.) This confused me until I realised you mean crosswinds rather than Crosswinds 😉

If your yoke behaves symmetrically in Windows Control Panel, there is nothing wrong with it and whatever you are observing must be a function of the sim. In FSX and P3D, the 'sensitivity' of a yoke axis was nothing of the sort, it introduced a lag in the yoke's response to your input. I would guess this behaviour is carried over to MSFS and perhaps this is connected to what you are seeing. You could check by setting it to maximum.

I think that indicates that it is paused (mine are orange, but maybe that's what you mean). Have you tried pressing whichever key is mapped to Pause? (Or clicking the little rectangle at the bottom of the screen)? When TrackIR is active but not tracking and not connected to an app the visible LEDs will be out.

And now even better with the optional damper upgrade!

My recollection is the original versions didn't support P3D and they said they weren't going to update them. Then in 2017 or 2018 they released all-new versions, which you had to buy again for all platforms (i.e. they weren't upgrades, they were new products).

I have the GNS530W for P3D. Perhaps you are thinking of the old v1 legacy versions.

(Slop zone, not dead zone 😉 )

That will increase your elevator dead zone, perhaps beyond the point where it will be acceptable. Honeyomb states that the tension is chosen to allow a return to centre within 3mm for the bearings they have used.

At the risk of repeating myself, there is no such thing as 'the Z axis'. SaitekRudder.Z and BravoQuad.Z are different axes and the only way they will conflict is if you accidentally map more than one thing to one of them.

The axes are independent for each device - hence the rudder's 'Z' axis has no connection to the Bravo's 'Z' axis. Most likely what has happened is that P3D has created some default assignments for each device when you plugged it in. You just need to edit them in the controls/settings dialog (or elsewhere if you use another tool to manage control assignments).

I made a video about this, in which I convinced myself things were better in MSFS, at least in the default Cessna 172. Perhaps my conclusions were premature, or perhaps they changed something since. However, I did find a very interesting description from PMDG of how FSX (and P3D) ground steering was always broken. Given that MSFS seems to include a lot of legacy code, maybe it's still broken.

That's why I made a 26-minute video to explain it in great dertail.