[FIXED B999] CAP algorithms seems to be changed (Bug? New feature? Distinction needed) (Full Version)

All Forums >> [New Releases from Matrix Games] >> Command: Modern Operations series >> Tech Support



Message

peacekeeper118 -> [FIXED B999] CAP algorithms seems to be changed (Bug? New feature? Distinction needed) (10/11/2017 4:07:01 PM)

I'm confronted with several strange behaviors CAP A/C's are showing. Situations described below were not seen until 1.12.

There are two questions with 2 save files. Here goes first Question.



1) First Question (Attached save file Q1)

Look at the F-15s heading north - Every F-15's status panels indicate they are 'Engaged Offensive', But I cannot find reasons why thay are doing so.

- Bogeys are beyond prosecutions areas(I even turned off 'Investigate contacts outside patrol area'!)

-'Investigate contacts within weapon(s) range' option is checked, but they are outside of Sparrow AAM's range.

- Maximum threat respond radius is shorter than distances to the bogeys.

This also appeared in another scenario - I thought It was temporal problem, but It wasn't




2) Second Question (Attached save file Q2)

After horribly pounded by Red AMRAAMs, F-15 #10 finally managed to fire two Sparrow Missiles against target, But after a few seconds He(or She) fires missiles, F-15 #10 sets new waypoint in patrol area and abandons illuminating missiles to target.

I assume this behavior is due to the 'Ignore plotting course when attacking - NO', but this looks bit weird - there are no incoming missiles against F-15 #10 and there are no reasons that guiding should be halted - How do you guys think?






3) Just one more question - Is loiter setting when 'cranking' normal?



Dimitris -> RE: CAP algorithms seems to be changed (Bug? New feature? Distinction needed) (10/11/2017 5:23:39 PM)

quote:

ORIGINAL: peacekeeper118
3) Just one more question - Is loiter setting when 'cranking' is normal?


Yes. When you're cranking, you want to approach the other guy as slowly as possible. So you go offset until he's right at the margin angle where you can provide SARH illumination (or datalink updates), and at the same time chopping back your speed, to minimize your actual merge speed even more. You are trying to maximize the time until you get inside his weapon envelope, to give your in-flight weapon(s) as big a lead as possible.



ComDev -> RE: CAP algorithms seems to be changed (Bug? New feature? Distinction needed) (10/11/2017 7:33:53 PM)


quote:

ORIGINAL: peacekeeper118

I'm confronted with several strange behaviors CAP A/C's are showing. Situations described below were not seen until 1.12.

There are two questions with 2 save files. Here goes first Question.



1) First Question (Attached save file Q1)

Look at the F-15s heading north - Every F-15's status panels indicate they are 'Engaged Offensive', But I cannot find reasons why thay are doing so.

- Bogeys are beyond prosecutions areas(I even turned off 'Investigate contacts outside patrol area'!)

-'Investigate contacts within weapon(s) range' option is checked, but they are outside of Sparrow AAM's range.

- Maximum threat respond radius is shorter than distances to the bogeys.

This also appeared in another scenario - I thought It was temporal problem, but It wasn't



The 'Weapon range' flag is set, and the AI uses a range modifier (2x in the case for AAMs) to be able to 'lead' the target (i.e. fire outside max kinematic range for fast closing missiles etc) and also go to desired attack speed and altitude. Plus it avoids the AI vs Player ambush cases that were presented to us earlier.




ComDev -> RE: CAP algorithms seems to be changed (Bug? New feature? Distinction needed) (10/11/2017 7:35:25 PM)

Question 2 is a bit more tricky. Please give me a day or two to see if I can resolve it. Thanks [8D]



peacekeeper118 -> RE: CAP algorithms seems to be changed (Bug? New feature? Distinction needed) (10/12/2017 8:55:18 AM)

quote:



Dimitris

Yes. When you're cranking, you want to approach the other guy as slowly as possible. So you go offset until he's right at the margin angle where you can provide SARH illumination (or datalink updates), and at the same time chopping back your speed, to minimize your actual merge speed even more. You are trying to maximize the time until you get inside his weapon envelope, to give your in-flight weapon(s) as big a lead as possible.



Thanks for such a kind answer [:)]



quote:



emsoy

The 'Weapon range' flag is set, and the AI uses a range modifier (2x in the case for AAMs) to be able to 'lead' the target (i.e. fire outside max kinematic range for fast closing missiles etc) and also go to desired attack speed and altitude. Plus it avoids the AI vs Player ambush cases that were presented to us earlier.


Question 2 is a bit more tricky. Please give me a day or two to see if I can resolve it. Thanks.




Oh, so Q1 was actually some kind of bug-fix. Good work! But checkbox description message seems not intuitive [;)]

Anyway I'll wait for your second reply.



ComDev -> RE: CAP algorithms seems to be changed (Bug? New feature? Distinction needed) (10/13/2017 11:19:09 PM)

On Q1, have made further mods in B976. Thanks [:)]



ComDev -> RE: CAP algorithms seems to be changed (Bug? New feature? Distinction needed) (1/21/2018 7:15:25 PM)

Fixed Q2 in B999, thanks!



AlexGGGG -> RE: CAP algorithms seems to be changed (Bug? New feature? Distinction needed) (1/21/2018 8:02:22 PM)

quote:

and the AI uses a range modifier (2x in the case for AAMs)


Thank you very much for this datum.



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
1.1875