[Logged] .18 and ASW Strike Missions- Range Warnings with Helo's

[BDukes]

If you create a ASW Strike mission (typical for helo on ASW ship) you'll get strike mission range warning when you assign helo's to it. Doesn't happen with longer-ranged assets. This used to be suppressed in past version (I think!).

Its only really annoying if you assign a bunch of aircraft to it as you've got to close a bunch of warning windows.

Load scenario. Add SH-3H's to saw strike mission. Notice the 8-9 popups. Add the S-3 Vikings notice no issue.

Mike

[BDukes]

Screenshot of message

Again. Minor annoyance and nothing unless you assign a bunch of aircraft to it.

[boogabooga]

I've seen this with land strike missions as well when the targets are not pre-defined. It seems harmless, as the strikes seems to launch alright anyway when a valid target comes into range.

Another similar UI issue is trying to assign A2A loadout-ed escort fighters to a strike mission with the intention of marking them as escorts, only to have them get rejected from the mission on improper loadout grounds.

[BDukes]

ORIGINAL: boogabooga

I've seen this with land strike missions as well when the targets are not pre-defined. It seems harmless, as the strikes seems to launch alright anyway when a valid target comes into range.

Another similar UI issue is trying to assign A2A loadout-ed escort fighters to a strike mission with the intention of marking them as escorts, only to have them get rejected from the mission on improper loadout grounds.

Yeah I'd definitely rank it as annoying more than anything. For some reason I felt like these error messages were suppressed for ASW strike missions at some point because of it.

Mike

[DWReese]

Mike,

I get a similar message with SUPPORT missions. The message box states that one (or more) aircraft may experience a issue with the mission pertaining to fuel. The units are actually within the allowed distance, and I merely hit the button to continue, and everything works as expected.

As you indicated, it's more of a nuisance than anything else.

The important this is it is also involving SUPPORT missions in addition to your report.

Doug

[PaulTheWolf]

Hi all!

I'm doing some reproduction testing on this issue, and I was wondering, what criteria do the Support and Strike Mission issues pop up in? Is it platform & number of platform specific the way the ASW Strike mission issue appears to be?

Paul.

[BDukes]

ORIGINAL: PaulTheWolf

Hi all!

I'm doing some reproduction testing on this issue, and I was wondering, what criteria do the Support and Strike Mission issues pop up in? Is it platform & number of platform specific the way the ASW Strike mission issue appears to be?

Paul.

Thanks Paul!

In my experience if you add all the Sea Kings to the ASW strike mission in my test scenario you'll get the message. If you add the Vikings you don't. I wish I had more time to test all the different combinations but unfortunately, I don't at the moment.

Thanks!

Mike

[PaulTheWolf]

Hi BDukes,

I was able to reproduce this in your save as you describe it! Thanks. I wanna try to see which platforms this extends to in general strike and support mission contexts. Fellow reporters, do you have any specific examples that might be useful for testing?

Paul.

[michaelm75au]

Yes, I believe that this is related to having no target as it is trying to validate that the a/c can reach the target. If no targets defined, it probably should not be checking.

[BDukes]

ORIGINAL: michaelm75au

Yes, I believe that this is related to having no target as it is trying to validate that the a/c can reach the target. If no targets defined, it probably should not be checking.

Thanks Michael

[WSBot]

0014481

[BDukes]

This is fixed. Thank you!

Looks like normal strike missions aren't displaying the message however. I'm good if you decided to get rid of it all together but thought you should know if that is not the case.. File attached. Check out the Hornet strike mission.

Mike