yankeeclipper

No. It means that I need to enable "No Reverse Zone" so that the mappings don't get confused and map the minimum value with things like IDLE.

When I go to the calibration dialog (Cowl Flaps, e.g. but same regardless of axis assignment) without hitting the "set" button (Axis not processed) the input still matches the output. +/- 16k. If I hit "set" the input is still full range but the output will only vary from +16k to zero. No negative values in output. This means FSUIPC calibrates to the top half of my device only, the bottom half of my input device is unusable (a lever, in the case of my Saitek quadrant, though same result with Bravo Quadrant). I have tried various settings such as mapping to FSUIPC calibration and to FS as normal axis. No change there. Same with "Filter" I am using: Alpa Yoke, Bravo Quadrant, Logitech Radio Panel, Saitek pedals and Quadrant.

I turn the yoke lock to lock and set the left and right values. Though they read slightly differently with each turn from center to extent, it's only +/- 150 at the most. Small compared to 16384. It shows that it has set +/- 16,xxx for a max/min value, but there are fully 30 degrees of unusable yoke turn on each side. In other words, when I turn the yoke to a position that is 30 degrees before hitting the stop, on either side, I already have maximum aileron deflection (on any model I choose). I have also made sure to unmap the P3dv4 control setting. So what am I missing?

Thanks Thomas. I have to admit you lost me on some of that, but I did try your offset suggestion and it worked, at least for the battery. I'll see if I can understand what the offset values are all about and try it with the rest of the controls.

I have read the manuals. I just don't understand how I'm supposed to control something as simple as a battery switch on a flight yoke. The yoke in question is one that has a physical toggle switch, just like in the real aircraft--press it up (for feature on) or down (for feature off). But there is only a 'toggle' setting for battery (or avionics, or ...) in the list of controls (in FSUIPC buttons tab) that can be sent. This obviously doesn't work, since it means that physically pressing the battery switch up will only resulting in *changing* the state, but not ensuring that battery master is actually on. Likewise, pressing the switch down, won't ensure that the battery master is off. Now I could of course just set both the "up" and "down" positions to equal toggle, but that's rather kludgy as this assumes that the state of the virtual aircraft aligns with the state of the physical switch. And again, it would seem a bit kludgy to work around that by first aligning through the use of the virtual switch. Kinda takes the magic out of it. Did I miss something?