Tutorial Question

Matrix Games Forums

Forums Register Login Photo Gallery Member List Search Calendars FAQ

My Profile Inbox Address Book My Subscription My Forums Log Out

Tutorial Question

View related threads: (in this forum | in all forums)

Logged in as: Guest

Users viewing this topic: none

Printable Version

All Forums >> [New Releases from Matrix Games] >> Command: Modern Operations series >> Tutorial Question

Page: [1]

Message

<< Older Topic Newer Topic >>

Tutorial Question - 12/6/2020 6:08:24 AM

MyP

Posts: 10
Joined: 10/21/2020
Status: offline

Hi,

I'm new to Command.

Why are neither F16s firing their weapons at the target yet, which is within their maximum range?

Sufa-1 is set to automatic engagement (F1) while Sufa-2 is set to manual engagement (Shift F1). Sufa-2 will eventually fire at around 9.5nm.

What do I need for the F16s to engage at closer to the Python's maximum range? High speed, high altitude....? This is the third time on this scenario. I had to reduce the altitude of the F16s as on attempt #2 it was telling me (on Shift F1 screen) that the altitude difference was too high). I have placed sensors on Active and have AEW.

Attachment (1)

Post #: 1

RE: Tutorial Question - 12/6/2020 8:56:57 AM

CHM

Posts: 63
Joined: 9/17/2017
Status: offline

Hello.

In the Shift-F1 (manual) engagement mode for Sufa-2, you'll see this text underneath the Python:

Target is out of the weapon's DLZ.

Effectively, this means that the 'brain' (AI) has decided that if fired, the missile would not have a realistic chance of reaching and hitting the target. Why not? See this image below:

Let's say Sufa-2 fired the missile (red arrow) at this point. The target may detect this (or another asset detect this and transmit this information to the target) and turn away (green arrow), fleeing out of range and outrunning the Python.

Sufa-1 is closer to the target, hence why - if unpaused - it will fire.

The DLZ calculations depend on the range to the target, the speed of the missile fired, and the speed of the target.

I hope that this answers your question.

(in reply to MyP)

Post #: 2

RE: Tutorial Question - 12/6/2020 11:20:46 AM

MyP

Posts: 10
Joined: 10/21/2020
Status: offline

Thank you, that does make sense for Sufa 2.

However, when I set Sufa 2's radar to off and "b" for rtb so it turns home, Sufa 1 continues to fly to the target, but doesn't fire. It will circle the enemy a few times. I would expect that Sufa 1 with "F1" engagement should have engaged before Sufa 2, and even if it didn't, it should engage fairly soon afterwards, not just circle the enemy. Even when I select Shift F1, Sufa 1 has Green launch status, but still won't fire.

< Message edited by MyP -- 12/6/2020 11:26:18 AM >

(in reply to CHM)

Post #: 3

RE: Tutorial Question - 12/6/2020 11:25:03 AM

MyP

Posts: 10
Joined: 10/21/2020
Status: offline

Missing pictures

Attachment (2)

(in reply to MyP)

Post #: 4

RE: Tutorial Question - 12/7/2020 6:11:12 PM

CHM

Posts: 63
Joined: 9/17/2017
Status: offline

Apologies for not replying more promptly, but I know what your problem is here. You ordered Sufa-2 to disengage (by returning to base), but previously Sufa-2 was manually ordered to fire on the target. Even though Sufa-2 is now heading home, that manual attack order is still 'saved' (see image below).

This means that Sufa-1 will not engage - the target has been 'reserved' by Sufa-2 (even though he is heading to base). To solve this, I told Sufa-2 to drop the target. This freed up the enemy aircraft, which Sufa-1 promptly engaged.

I hope this makes sense.

(in reply to MyP)

Post #: 5

RE: Tutorial Question - 12/7/2020 8:33:14 PM

thewood1

Posts: 6529
Joined: 11/27/2005
Status: offline

I think there might be a disengagement setting in ROE for this also.

(in reply to CHM)

Post #: 6