On repeatable but unknown circumstances, M4 Scorcher artillery (virtual or not)hits the target with a strong delay (i.e. 50sec instead of 29s ETA).ETA seems to be good : same value for:- ETA submenu title (support),- ETA obtained by getArtilleryETA function,- art computer display with round cinematic.Other artilleries (mortar and MLRS) don't seem to get this issue (virtual MLRS not reliable in triggering fire).
Description
Description
Details
Details
- Legacy ID
- 2829920054
- Severity
- None
- Resolution
- Open
- Reproducibility
- Always
- Category
- Config
Steps To Reproduce
Create a new mission in editor (basic to avoid any lag problem).
Choose Stratis, place a M4 Scorcher in grid 037048 or more exactly 0375 0488 (near hill 214), let it North oriented, place your player unit (spotter or else) near stratis airfield (i.e. 0227 0492) to have the airfield in sight, but you can choose another place)
place support requester & support provider modules as usual (if virtual artillery, place the virtual artillery provider module on the same position (hill 214). Run the preview.
Aim at tent hangars (0173 0520) and ask for artillery support. Check by the way ETA in sub-menu title (something about 30sec for M4 155mm shell, 25sec for mortar shell, 43sec for MLRS ammo).
You can trigger a real chrono at "ordnance is inbound" or when artillery shots if you stay near from it. watch for impacts.
flying time of shell is OK for mortar and MLRS, wrong for M4 Scorcher : about 50sec instead of 29!
Shoot in other directions : this could be fine. Return to shoot tent hangars, shells are 20sec late!
Additional Information
I have done this test several times using chrono but also a "fired" EH for artillery which triggers at shot. It's possible to hint or display elapsed time from shot (i.e. with diag_ticktime comparison in script). Results are same.
I haven't found why M4 ballistic time could be so different from calculated ETA when shooting at Stratis airfield (regardless of light or heavy scenario).
If you aim and shoot at Agia Marina or surrounding hills, there is no problem.
Event Timeline
Comment Actions
Hi everyone,
I've done complementary tests using Altis _ Almyra flat desert. Place an M4 Scorcher at grid 230172 (between the 2 lakes). Shoot at small hill (033 2300m). ETA is about 25sec and all seems OK if you are in M4 (artillery computer, gunner view). Impact at ETA. Now, play a spotter close to artillery. Aim the same target (roughly same az/D). Order a M4 fire: ETA in support sub-menu title remains 25sec, but impact occurs after 51sec! (You receive also the "splash" at 46sec). I don't understand how ARMA engine can manage two separate explosions: at ETA for M4, and 20sec later for all outside units!
All sounds great for mortar & MLRS. Strange ETA calculation for M4 because ETA decreases above 1400M range. It seems parabolic trajectory is not correctly computerized, leading to a wrong ETA. The function getArtilleryETA returns the same wrong ETA.