When firing the MK6 on flat ground, it hits targets accurately with the artillery computer, manual range finder and manual trajectory calculation.
When the mortar is placed on uneven ground the artillery computer remains relatively accurate, but manual range finder suffers inaccuracy and manual trajectory calculation suffers even more inaccuracy.
As distance to target grows longer, the issue becomes obviously greater. {F23341}
Place mortar on flat ground (airport). Fire at target with both artillery computer and rangefinder that is at least 1 km away, preferably 2 km. Observe excellent accuracy.
Now place mortar on ground with even a slight slope. Attempt the above again. Observe considerably degraded accuracy.
Attached is a picture that demonstrates the difference. Target was the center of the guard tower. Closer hit is with the artillery computer, further hit is with rangefinder.
An alternative could be a level or "zero" option on the mortars to have them automatically account for the slope they're on. For the Mortar though, considering that it has feet that are adjustable there should be an option to mechanically level it since I'm sure the real stuff has bubble levels.
Yep agree with Scroll. It is really annoying to not be able to calibrate the Azimuth and elevation when mortar is not on flat ground (with gravity reference).
I did a test with stable version 1.48 and issue is still present.
I think it is necessary to change the title of the report. Example - "No tool setting mortar into the horizon on an uneven landscape".
Work on this report has been partially implemented
http://feedback.arma3.com/view.php?id=24423
BI, I'm sorry, but how much we will be writing the same thing?
Since the update 1.48 the manual trajectory calculation doesn't work. I did also tests with the ace 3.1.1 mod and "ACE_RangeTable_82mm" by using 1.48 -- no chance to hit any targets. If i use the 1.46 all is working fine:
http://feedback.arma3.com/view.php?id=24894
Why are they doing such strange changes in an update? BI, please let us know, how we should now doing manual trajectory calculation, because we are playing with the "enableEngineArtillery false;" option.