From: Melbourne, Australia
By all means. Any time you're ready. Bring it on since you obviously aren't able to fix or identify bugs (the entire point of this thread).
0002339: Max launch range for non-interecepting weapons (i.e. guns) was not enforced
While conducting some testing of units from the HUD3, I have found what I think is an issue in regard to the resolution of gunfire. I was testing a version of the AC-130 Spectre, and I've noticed that the aircraft's "Task" status remains set at "Awaiting Engagement Outcome" for several minutes at a time.
When the aircraft approach their target, they reach effective range, fire and then proceed AWAY from the target they have just fired on while under the control of the "Awaiting Engagement Outcome" tasking. This tasking persists until the status of the unit's weapons has finally cleared from "Engaged" to "Ready", when viewed in the Unit Status - Report window. While the aircraft fly away from the target, multiple hits can be observed via the "explosion stars" appearing on these targets, well after the Spectre has moved out of range.
Steps To Reproduce
1.> Open QUEUED GUNS.SCN, testing here was conducted in MP mode. I'm assuming the underlying issue will present in other execs.
2.> There are 2 x AC-130 Gunships assigned to 2 separate missions. These missions are strikes on both the Opfor base grouping and individual facilities. The targets are identical, except that one 5 facility target group has been grouped as a base.
3.> Run the scenario and observe how the attacks pan out. In some of my testing here, the AC-130 would fly all the way back to its airfield awaiting the engagement resolution to take place after attacking the enemy facilities. It would then fly back and attack fly away and return until its ammunition is expended. Note it wouldn't land, just circle its own base before attacking again.
I've set the range values, ammunition carried and rate of fire to the same values for each of the three gun systems in place on the aircraft. The Gun weapons have also been flagged as "limited to mount arc" and "primary aircraft AS gun".
I may be misguided, but I would have assumed that by limiting the mount's arc and making all guns fire every 15 secs that, the AC-130 would circle each of the targets in its mission target list until destroyed and then adjust course slightly to move to the next listed target in the mission list until it had either expended all of its weapons, or the targets were destroyed.
That's from Mantis, and that's how you write up a bug report bad luck you can't provide the same courtesy to AGSI. I'll list everything I've had fixed if you like.
I can prove I get stuff fixed, you're saying otherwise. Are you calling me a liar?