onedown

It's not lag but a design choice. The collective adjusts faster the longer you hold down the button and is a non-adjustable (as far as I can tell) feature of digital collective control in AFM. You'll have to use analog binds to get around it unfortunately.

This is exciting. I am excited!

Hey shay I think you might have missed my post. You probably don't go back and reread already answered sections of the thread so I'll repost and clarify it in hopes that you see it. My group is having minor issues with interaction between standalone VAS scripts and MCC where it seems the local mod version MCC VAS scripts overwrite the server's mission's standalone (with modified config) VAS scripts. Would it be possible to add a server side config option to disable MCC's VAS scripts so that our server side mission scripts work as we intended and players do not have full access to everything an unrestricted VAS box gives access to?

My group is having minor issues with interaction between already placed VAS boxes and MCC where it seems the MCC scripts overwrite the already existing standalone (with modified config) VAS scripts. Would it be possible to add a config option to disable MCC's VAS scripts/module so that our already placed VAS boxes work as we intended? I know it's possible to add VAS boxes using MCC but we use a mission template that has a basic base and such already created pre-MCC use. See http://forums.bistudio.com/showthread.php?150909-MCC-Sandbox-3-Dynamic-mission-creating-tool-for-ArmA-3&p=2698640&viewfull=1#post2698640 for updated question.