I'm really sorry you are not happy with the fix we applied in 2.04, I haven't seen any complains except yours, so this was unexpected. I have re-downloaded 2.02 to compare, and while it is true, when optics are brought up, the movement is artificially restricted to stay within the screen boarders, this was the culprit for initial issue of unusable deadzone. At the moment the free swing is constant between all types of optics and sights, meaning, if you find 2 objects at a distance deadzone apart, the range of the barrel free movement before your body starts turning will be identical whether it is no sights, iron sights, optics or zoom in any of the above. This makes it consistent and usable. in 2.02 optics and zoom movement was limited to the screen borders, so if you would point your weapon at an object at the edge of deadzone and then zoom or bring up the optics, your aim would jump towards the screen center and you end up aiming not where you were pointing. After 2.04 you actually are aiming where you pointed.

This was fixed in 1.84. (With a citation of this very ticket! https://dev.arma3.com/post/spotrep-00081)

but there was no reason as everyone is free to adjust it to their liking

As intended. You can move deadzone slider to about half. I could have orce lower it so that the sites would never leave screen, but there was no reason as everyone is free to adjust it to their liking

Should be fixed since rev 148197

Cannot repro

fixed in rev 148195

AH-64D Apache mod dev here, agreed this would be great! I am currently in the process of moving our mod across to this, and the 50 values is definitely a tight squeeze for us too - we aren't able to move all of the parts of the pages across to the new method because of this and are working on a hybrid approach, and multiplexing the different MPD pages so we can reuse values.

game keeps crashing cant get it to work no matter what i do.

I’ve passed your ticket to our config person let’s see what they say

If set last value in envelope[]={}; config entry less or equal to 1 it will not climb. But there is still "bump" at 125% maxSpeed. It will descend but rate will be less than at 120% maxSpeed. Also speed display will not turn red.

Hi, Ive just tried with katiba in mp and sp, no problem, firemode stays full auto when getting out. Could you post detailed steps how to repro the bug please?

Indeed, at small downward angle after max speed reached the UAV starts rising. Interesting bug but it is burred deep in physics simulation so not fixable at this time.

If you read my original post, I have tried everything under the sun aside from a full system restore..

my game crashes on startup

Seems to me that these are working fine, thanks once again :)

Your game display resolution might be misconfigured

rev 148193

Have you tried these?
https://community.bistudio.com/wiki/Arma_3:_Unusual_process_exit#0xC0000005_-_ACCESS_VIOLATION

Can I get some eyes on this crash report so somebody can tell me what keeps giving me this error?

in description.ext instead

try RscEdit instead of ctrlEdit

Changing the KeyDown EH to a KeyUp EH sovles the problem of having to use spawn, call can be used instead. Focus is still lost though.

Problem with that is that the KeyDown EH fires before the change is applied, i.e. the text is not up-to-date. So you type "rahim" and it will search for "rahi".

Linux + SOG map + Domination

Ay yai yai! You SPAWN search script on each key push and you dont even wait until it is finished! You can have missions of search scripts running without any order. try ["search", _this] call SELF;

rev 148170

maxLoad, setMaxLoad rev. 148169

Observe is not enough, I need to reproduce it in debugging environment.
And so far that step has always broken reproducibility. I think its maybe some file corruption issue, that fixes itself if you change mod or build version

Shameless bump and further counter argument: CBA playerEvent doesn't work for the AI because playerEvent.
Same goes for the weaponSwitch event request: https://feedback.bistudio.com/T151696

This is an exciting opportunity to squash that bug. :)