I've no idea whether the PMDG flaps implementation uses all of the FSX flaps simulation or does its own thing, but I've looked at the data it provides in its Client Data and all that gives are left and right needle positions, for the flaps gauge. If you monitor those offsets using FSUIPC's monitor facilities (Logging tab), as type U16, you'll see the original SimConnect values which are received (in floating point) as well as FSUIPC's conversion into U16 format (for compatibility with FS98 through to FS9). Those values are direct from the SimConnect variables 'TRAILING EDGE FLAPS0 LEFT ANGLE' and 'TRAILING EDGE FLAPS0 RIGHT ANGLE'.

Since PMDG and most add-ons do something funky I also adjust the flaps based on the values than FSX reports. I'm reading 30F0 and 30F4, adding them together than shifting right 9 bits for an average flaps value. I can provide screen shots of what Monitor FSUIPC Data is reporting for each flaps position if you need them. It's only the information reported by FSUIPC that appears out of synch with what's actually happening. Keep in mind that throughout all of this, the flaps on the plane have been setting correctly and the cockpit indicators have ben positioning correctly using the Saitek throttle quadrant. Other combinations have been encountered (including the 'Flaps 40 when I'm at Flaps 1' indication), but the progression above is the most common. So starting with flaps up, I will usually see a flaps handle index progression of 0, 1, 2, 3, 8, 5, 6, 8, 8. The most common flaps settings where the disconnect occurs are flaps 10 and flaps 30. (There are 9 handle index positions on the 737NGX: 0 through 8).

Even though flaps movement and indicators in-game were perfectly normal, there were situations where FSUIPC jumped up to Flaps 40 and Flaps Handle Index 8 out of sequence. Just to see what I am sending out, I installed Monitor FSUIPC Data and took a look at the flaps data as I cycled through the flaps positions. We ran across a problem using our virtual airlines ACARS in that the ACARS was reporting that I was using Flaps 40 on takeoff when I actually was using Flaps 1. FSUIPC controls all yoke, throttle quadrant, and rudder pedal axis. All axis settings inside the FSX control settings have been deleted. I'm using Win 8.1 Pro 圆4, FSX w/Accel Pack, the PMDG 737-800NGX, a registered copy of FSUIPC 4.929, and the Saitek Pro Flight Yoke/Throttle quadrant properly set up in FSUIPC to use the Flaps Axis and calibrated accordingly.

Vrinsight pmdg 737 ngx