P.S: Not running any mods, just Vanilla ArmA, I've done the Steam option to fix the files, Did nothing.

Update, i Think the problem is linked to my joystick when i have it connected. Might be interfering with zoom in button i have linked on joystick, i have zoom in binded to shift+q and e (zoom in and out), seems to be interfering with the Ctrl + Q and e (turn in and out). It shouldnt be affecting eachother but seems like the ctrl or shift input first doesnt do a difference so it becomes problematic. Or if its a problem connected to joystick throttle im not sure but its defenetly connected to joystick somehow. Maybe you could test it out that way. This should be the problem.

by the way in the vehicle looking around looks fine.

Should be fixed by the recent surface overhaul (changes in maxSpeed, friction and restitution of the surfaces and in maxSpeed effect - now it's only a speed limiter and it doesn't affect PhysX thrust input)

As expected, seems to work in 32 bit.

NOTE : I crash also on several other mission that don't necesserally have boat, so it is not the fault of the boat, but since i can easily reproduce crash with this very simple vanilla mission, maybe it will help hunt the bug.

OK, I work on this issue all afternoon.
I get back to the original and first mission that make me crash : papi dans les orties V3

Thank you for attention. I bind axis correctly. My problem in that to look around with (xbox360 controller autoschemed) three times more agile than to look around with xbox360 controller from list of customizable mapped by xbox360 controller scheme.

This is still an issue for me. Can reproduce it every time with the Razer virtual surround. It does not seem to clash with the windows spatial surround emulation though.
x64 only.

@GambaDendy i think you mixed somthing up. The 100 is how much % your joystick has moved from 0 to full on 1 axis.
So it cant be more than 100.
What can be chang NOW is the way how it raises till 100 , how much you actually need to move your joystick and the deadzones aka how much you atleast have to move for anything to happen.

Max value 100 is too small. Need a coefficient of applied to controls. By default, the schematic (xbox one controller) applies the stronger force to aiming. Or need acceleration for axis. Sorry if is a offtop. Sorry for my English.

Just did some extra checking. Left gunner shoots at a Quilin (open topped car, doesn't matter if it is armed), so in the case of ifrits and striders the problem might be that the gunner either doesn't see the driver/passengers or "knows" that he shoot at him effectively.

Looking farward too it :)

Sit inside a CSAT Sochor for exemple or RHino in gunner seat (must be on a position where he can turn out). Enter UAV Terminal and click gunner on uav and zoom in on the tank. For me he turns out instantly when i look on the Artillery/RHino every time without pressing anything. Im not using any mods, and i havnt remapped my keys at all. I simply dont get this. Remember test it again please and make sure your sitting on a position you can turn out on. Its driving me nuts

@bclaws01
Could you let us know what the faulty module was? We're seeing similar warning messages on our server in the .rpt files along the lines of

I created those tracker :
http://feedback.rhsmods.org/view.php?id=4115
https://dev.cup-arma3.org/T2489

Thank you for the report, we will have a look at it.

Thank you for the report, we are aware of this issue.

Thank you for the report. Well this is odd. It would be great if there was a 100% repro if it is random it will be harder to pinpoint.

Interesting, followed your repro and my character does not turn out at all. Tested it in the stable build as well as dev and it works as it should.

The mission file places two soldiers and a Zeus. You're locked into Zeus. Rise straight up about 10 meters for the best view. The first soldier will attempt to visit every building position of the House_F closest to it via waypointAttachObject and setWaypointHousePosition. The second soldier will attempt to visit every building position of the House_F closest to it via coordinate. The second is provided as a sanity check as well as for contrast.

Could you please upload the test mission here?

Closing.

As you mentioned in the additional information. This in my opinion should not be considered a bug. You are tinkering with the file rather than using settings via the in game Options. In that case there is a possibility that issues might occur.

I pushed it forward to our Programmers so we will see what can be done. Did you try contacting the mod makers of the mods that cause the crashes for you? Might be worth to know what their take on the issue is.

Want to add more info to the report

My findings with this issue is that removing cannon ammo will make the gunner use the AT missiles. I also noticed that switching the AT missile control from gunner to pilot will make chopper use them. I noticed this on Greyhawk/Ababil too where gunner won't target ground units but switching the guided missiles to the "pilot" will make the drone engaging targets.