Hind definitely seems to have weird collective settings. The governor is up by default when you first get in, so that's not it. I have to put it past the detent on my throttle into the overtorque range to lift off and climb. Otherwise you really have to take advantage of translational lift to keep from crashing.
While the first incarnation of autorotation was clearly too easy and had too much lift. Pitching down and building up speed (which should be easier) also doesn't seem to increase rotor RPMs much at all, even with the little speed you can build up. The only time I see an increase in rotor RPMs with the rotor disengaged and the collective down is when I pitch up. Not good. Any increase in forward speed will push air through them and increase RPM, assuming the collective is down and rotor is disengaged.
Autorotation is a give and take between forward speed, decent, pitch up, pitch down, and conserving rotor RPMs through forwards speed without smashing into the ground...flaring and increasing collective at just the right time, fast on the flare, gradual on the collective. This uses up forward velocity for lowering vertical decent in the pitch up and the collective uses up the RPM "currency" you've stored up to cushion further for controlling the touchdown. The balance seems way off right now. Like I said, the initial autorotation modeling seemed fine except there was just excessive lift and you seemed to be able to conserve altitude too easily at the expense of not much else.
Like the overall flight models, we seem to be yo yoing between two extremes, here.