[FIXED B1115.7] Same scenario, very different results

[Dimitris]

Yes.

[kevinkins]

Thanks for the quick reaction to important user observations as they were posted above since the re-launch. Just a quick question(s), what does B1115.7 exactly address? Are there any unresolved issues mentioned by users in this specific thread? I know there are other fixes on the way, but these issues are some of the most critical uncovered so far.

OK missed this, was auto-engage addressed in *.6? I think it was and all the issues related to this thread are now considered resolved:

Changes from B1115.6
---------------------------------------
* Includes a number of older DB versions, in order to support loading various community scenarios.
* FIXED: 3D shape for Arleigh Burke-class DDG missing from Tacview resources
* FIXED: Script issue in QBG template "Submarine 1v1 duel"
* FIXED: Car navigation bug on "Raid on Kismayo"
* FIXED: Startup freeze on high-DPI desktop when the automatic 4K-fix has been rejected
* FIXED: Aircraft on strike mission flight path not obeying manual (player-given) changes to waypoint altitude
* FIXED: Aircraft on strike mission may automatically enter RTB status after takeoff even though they still fly the path
* Map tweak: Show the flight paths of airborne strike flights

Kevin

[LMychajluk]

Doesn't look like it's fixed in 1115.6. See attached.

The Seahawks on the Wasp (Redcocks) are assigned to the 'ASW Intercept' Mission with an 80nm range limit. No Targets currently assigned to the mission.
Hit 'Play'.
Within about 5 minutes, 2 of the Redcocks will launch, then immediately RTB as soon as they're in the air.

There is a ambiguous contact off to the west, and the 'center' of the ambiguity zone (where the unit icon is) is just at the edge of the 80nm limit of the Mission range. I'm guessing this is maybe triggering the mission?

May be a separate question/problem - Also note that changing the number of flights that can fly a mission will change the number of helo's launched. I may have this wrong, but I thought this was also be limited to 1 flight / target? So, a single target would only trigger 1 flight, with a Max of X Flights in the Air?

[JOhnnyr]

ORIGINAL: LMychajluk

Doesn't look like it's fixed in 1115.6. See attached.

The Seahawks on the Wasp (Redcocks) are assigned to the 'ASW Intercept' Mission with an 80nm range limit. No Targets currently assigned to the mission.
Hit 'Play'.
Within about 5 minutes, 2 of the Redcocks will launch, then immediately RTB as soon as they're in the air.

There is a ambiguous contact off to the west, and the 'center' of the ambiguity zone (where the unit icon is) is just at the edge of the 80nm limit of the Mission range. I'm guessing this is maybe triggering the mission?

May be a separate question/problem - Also note that changing the number of flights that can fly a mission will change the number of helo's launched. I may have this wrong, but I thought this was also be limited to 1 flight / target? So, a single target would only trigger 1 flight, with a Max of X Flights in the Air?

1115.6 is old news! we're on to v1115.7!!

[mavfin]

ORIGINAL: LMychajluk

Doesn't look like it's fixed in 1115.6. See attached.

Go to the main page and get the 1115.7 patch, and test again. Supposed to be fixed now.

EDIT: Just did the Intercept stuff with 1115.7. Seems to be fixed. Not RTBing too quickly.