Matrix Games Forums

Forums  Register  Login  Photo Gallery  Member List  Search  Calendars  FAQ 

My Profile  Inbox  Address Book  My Subscription  My Forums  Log Out

[FIXED B1009.27.5] ASW mission using Silex only

 
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 >> Tech Support >> [FIXED B1009.27.5] ASW mission using Silex only Page: [1]
Login
Message << Older Topic   Newer Topic >>
[FIXED B1009.27.5] ASW mission using Silex only - 3/17/2019 1:34:41 PM   
DMAN

 

Posts: 98
Joined: 1/11/2019
Status: offline
quote:


...

Additionally, I tried an ASW strike mission with a reloaded Kara-class, removed all shorter-ranged ASW weapons, and maintained stand-off.
It's 'Engaged Offensive' but does not launch the Silex. It is closing with the target at 5kn (current range to target: 15nm).
Manual launch of Silex is possible, but the aforementioned behaviour results.

From Dimitris:

We'll look into this, but can you please re-post this on a separate thread, so that we can track it? Thanks.



The attachment is here:

http://www.matrixgames.com/forums/tm.asp?m=4601627

(I think this attachment illustrates the above: if not, replicate as above)

< Message edited by Dimitris -- 3/25/2019 6:22:08 PM >
Post #: 1
RE: [MOVED] ASW mission using Silex only - 3/25/2019 6:17:48 PM   
Dimitris

 

Posts: 13282
Joined: 7/31/2005
Status: offline
Thanks! This was actually quite difficult to solve.

There were two factors at work:

1) There was an arbitrary hard-limit in the salvo-generation code for ASW attacks against targets further out than 15nm (probably to preclude ASROC-equipped units from running after subs all over the theater). This is unnecessary by now.

2) There was a possible case where a salvo shooter may "keep the salvo alive" despite not having any more weapons to use on it. This can be problematic if the unit is the sole shooter in the salvo and is effectively blocking all other units from participating in the engagement (e.g. the first Kirov attacking and precluding the Kara from joining in). Added a "housekeeping" check that removes the salvo in such a case, enabling re-engagement.

Fixed for the next update release. Thanks!

_____________________________


(in reply to DMAN)
Post #: 2
RE: [MOVED] ASW mission using Silex only - 3/26/2019 3:23:31 AM   
DMAN

 

Posts: 98
Joined: 1/11/2019
Status: offline

quote:

ORIGINAL: Dimitris

Thanks! This was actually quite difficult to solve.

There were two factors at work:

1) There was an arbitrary hard-limit in the salvo-generation code for ASW attacks against targets further out than 15nm (probably to preclude ASROC-equipped units from running after subs all over the theater). This is unnecessary by now.

2) There was a possible case where a salvo shooter may "keep the salvo alive" despite not having any more weapons to use on it. This can be problematic if the unit is the sole shooter in the salvo and is effectively blocking all other units from participating in the engagement (e.g. the first Kirov attacking and precluding the Kara from joining in). Added a "housekeeping" check that removes the salvo in such a case, enabling re-engagement.

Fixed for the next update release. Thanks!


Great news, Dimitris. Thanks!

Credit goes to the OP in the other thread who couldn't Silex to work in the first place; I only changed the variables and found this issue.

I should confirm: do the Silex now drop their torpedoes?

(in reply to Dimitris)
Post #: 3
Page:   [1]
All Forums >> [New Releases from Matrix Games] >> Command: Modern Operations series >> Tech Support >> [FIXED B1009.27.5] ASW mission using Silex only Page: [1]
Jump to:





New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts


Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

1.717