It is much better now that you have fixed the input discrepancies but descent rates are still a little slow. As a result it is hard to slow down and reduce altitude at the same time. I hope more experienced pilots pop in to comment here. While I'm not a novice, I'm no pro either. I could just be doing it wrong.

collective raise and lower cause ascent and descent at different rates depending on input device type and input type. Shouldn't these all be the same?

In the ah6/mh6
all figures in feet per minute from onboard VSI

keyboard:
2000 up
1800 down

mapped to joystick buttons:
7000 up and down

If you map the ANALOG collective to buttons on the joystick you get still another set of figures

2200 up
1800 down

however if using the analog collective inputs for non analog buttons, after releasing either button the helicopter falls at a rate of 1200 feet per minute until a non analog collective input is pressed.

In the KA-60
all figures in meters per minute from VSI on board

keyboard
600 up
600 down

joystick digital
2.5 up
2.5 down

joystick analog (mapped to a button)
700 up
600 down

  with a button release fall rate of 500 meters per minute

Please correct this issue

this is fixed please mark resolved

Confirmed, add suppressor to weapon without optics to reproduce.

no worries, needed sleep, looking back you didn't. I was a cranky baby. :)

collective raise and lower cause ascent and descent at different rates depending on input device type and input type. Shouldn't these all be the same?

In the ah6/mh6
all figures in feet per minute from onboard VSI

keyboard:
2000 up
1800 down

mapped to joystick buttons:
7000 up and down

If you map the ANALOG collective to buttons on the joystick you get still another set of figures

2200 up
1800 down

however if using the analog collective inputs for non analog buttons, after releasing either button the helicopter falls at a rate of 1200 feet per minute until a non analog collective input is pressed.

In the KA-60
all figures in meters per minute from VSI on board

keyboard
600 up
600 down

joystick digital
2.5 up
2.5 down

joystick analog (mapped to a button)
700 up
600 down

  with a button release fall rate of 500 meters per minute

Please correct this issue

I'm just providing numbers to go with the issue. Relax.

So glad this is reported!

It would also be nice to see the gas canister on the ground while it is emitting the smoke, and a hiss from the canister as well.

Confirmed on both E and shift+w

new max speed for the speedboat is 68kph? That's not very speedy now is it?

Please tell me the reduction in max speed to 68kph for the speedboat was a mistake. And the attack boat? It's almost as slow as the running speed of a man.

I have edited my previous comment to reflect the correct steps needed to replicate the issue. I was wrong about the zoom command. "lock or zoom" is the problem command. I have mostly encountered this issue while driving with a ps3 controller and I have many keys mapped to multiple commands which made it difficult to isolate the command at fault. I believe this issue would likely impact any zoomable turret.

I have just tested the Mk6 Mortar, and it also suffers from this issue, seemingly confirming my "any zoomable turret" hypothesis.

this is fixed please mark resolved

I've had this problem, but have been unable to find a way to stop the stuck zoom. Changing to a new vehicle will fix it but that's not always an option.

Definite steps to reproduce this issue:

1. get into hunter OR IFRIT with hmg or gmg,
2. move to gunner position.
3. while holding "lock or zoom" (right click or bound to any other key), activate the gun camera.

You will need to bind "lock or zoom" or "optics" in a way that allows you to press "optics" while already holding "lock or zoom".

observe that gun cam is now zoomed in completely and can not be zoomed out.

also reloading the MX underslung grenade launcher causes the main magazine to float out of the weapon and then be reinserted as if by magic. This magic magazine has no shadow.

Also witness this every time I reload the 40mm.

collective raise and lower cause ascent and descent at different rates depending on input device type and input type. Shouldn't these all be the same?

In the ah6/mh6
all figures in feet per minute from onboard VSI

keyboard:
2000 up
1800 down

mapped to joystick buttons:
7000 up and down

If you map the ANALOG collective to buttons on the joystick you get still another set of figures

2200 up
1800 down

however if using the analog collective inputs for non analog buttons, after releasing either button the helicopter falls at a rate of 1200 feet per minute until a non analog collective input is pressed.

In the KA-60
all figures in meters per minute from VSI on board

keyboard
600 up
600 down

joystick digital
2.5 up
2.5 down

joystick analog (mapped to a button)
700 up
600 down

  with a button release fall rate of 500 meters per minute

Please correct this issue

So sick of having to exit arma just to switch to my headset. Please resolve this.