pp (plug-in parameter) object MESSED UP in 4.6 ???

On both my systems, running Max 4.6, the pp object seems to be in quite a state of disarray. For starters, it has three outlets instead of two, the third outlet saying "dumpout" on rollover.

In addition, the two outlets are not properly tracking the input. For an integer input, the outlets toggle between 0 and 1. For a float input, the left outlet toggles between 0 and 1, while the middle outlet echoes the input from 0 to 1, but then caps out at 1.

> In the past, pp has worked for me in this way: values in are
> immediately sent to the left outlet as scaled data and to the
> center outlet as raw 0. – 1. data.
>
> In the new release, pp no longer seems to echo to the left outlet,
> although raw data in the center outlet is still flowing.

"Prior to Max 4.6, the pp object used a different technique for
controlling feedback networks than it does post 4.6. The previous
approach in the pp object worked quite well, but led to a variety of
problems in a number of contexts that didn’t exist when the previous
pp behavior was originally implemented. The most widely-experienced
problem was that it broke in recent versions of Ableton Live when a
user decided to use the "Clip Envelope" feature of that host.

"The new technique, which is backwards compatible for the typical
patching situation (as demonstrated in the example above) prevents
all of these problems related to feedback issues. Some Pluggo-based
patches may need some minor modification, but it should be quite
simple, and we hope that it is acceptable. If you experience trouble
and need any help (or have questions) while transitioning any
patches, please feel free to send them in to support@cycling74.com."

Note to Cycling: please update your documentation! In order to work as advertised, pp now requires this external feedback loop through a number box. Such a change ought to be included in the docs, if not highlighted!