Matrix Games Forums

 Forums  Register  Login  Photo Gallery  Member List  Search  Calendars  FAQ 

My Profile  Inbox  Address Book  My Subscription  My Forums  Log Out

[Logged] ASBM vs SM-3 Engagement Oddity

 
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 >> [Logged] ASBM vs SM-3 Engagement Oddity Page: [1]
Login
Message << Older Topic   Newer Topic >>
[Logged] ASBM vs SM-3 Engagement Oddity - 5/10/2021 6:33:21 PM   
Tailhook

 

Posts: 293
Joined: 1/18/2015
Status: offline 		Greetings,

Playing the "Escalation" (updated from the forum) scenario from the Kashmir Fire scenario and encountered a weird bug. Scenario attached.

The Lincoln CSG is currently off the SW coast of the tip of the Indian peninsula. There is an (as yet undetected) ASBM engagement currently underway on the CSG, with 4x DF-26 RVs inbound. Both these RVs and the Carrier escorts are not behaving as anticipated, with varied results every time. On some engagements, the ASBMs come in cruising aggressively shallow (like 30,000 feet from 120 nm away) and/or miss well short of their target. While I know that it is possible for ASBMs to glide in the atmosphere, this seems far too low and not what is going on here.

In other engagements (I have loaded this particular scenario about 10 times now to see what happens and gotten various results but all similar. It even crashed one time "Exception of type 'System.OutOfMemoryException'.), the USS Anzio does not engage the ASBMs with it's onboard SM-3. The error message is "The weapon's target-altitude envelope does not match any point in the target's estimated trajectory." The issue is these missiles are coming right for the CSG, so I can't imagine there isn't actually a solution available to the Cruiser which is explicitly equipped to deal with this very attack.

I also think that SBIRS and/or other satellites, as well as the radar on the cruiser should have detected these missiles much earlier than they do, but I could be wrong here.

How I believe this situation SHOULD work out:
-ASBM detected on ballistic path (at significant altitude) at least 250 nm away headed for CSG
-Anzio acquires firing solution and engages ASBMs.
-RNG handles the rest

As it stands, the ballistic missiles don't fly a consistent ballistic path, and even when they do the cruiser can't engage them.

Edit: I have now had the game crash 5 times as I continue playing the scenario. I suspect a memory leak.


Attachment (1)

< Message edited by WSBot -- 5/10/2021 8:48:01 PM >
Post #: 1
RE: ASBM vs SM-3 Engagement Oddity - 5/10/2021 8:47:49 PM   
WSBot

 

Posts: 182
Joined: 1/17/2021
Status: offline 		0014551

(in reply to Tailhook)
Post #: 2
RE: ASBM vs SM-3 Engagement Oddity - 5/10/2021 9:12:13 PM   
PaulTheWolf

 

Posts: 40
Joined: 12/10/2017
Status: offline 		Hi user Tailhook, thanks for bringing this to our attention. I've begun reproduction testing with the provided scenario. Could you provide an exception log of the problem when you experience a crash as well? In order to create the Exception Log, navigate to the Config folder in your Command installation directory, and open Command.ini in Notepad or another similar text editor. Find the following line:

LogDebugInfoToFile = False

And set it to

LogDebugInfoToFile = True

Save that file, then open command and run it until a crash occurs. Your exception log will be found in the Logs folder of your CMO Installation directory under the file name ExceptionLog.txt. If you could share that file with us here after a crash it would help our efforts in identifying the cause of the likely memory leak considerably. Thank you again for bringing this issue to our attention!

(in reply to WSBot)
Post #: 3
RE: ASBM vs SM-3 Engagement Oddity - 5/11/2021 1:22:42 AM   
DWReese

 

Posts: 1824
Joined: 3/21/2014
From: Miami, Florida
Status: offline 		Paul,

This sounds a lot like the issue that we discussed last month (ABM OVERSHOOT ISSUE) involving the same weapons. In the the SM-3 IIA had difficulty tracking the inbound missiles and then would OVERSHOOT them. (Actually, the flew 30 km beneath them.) Whatever happened to that investigation? I see that it wasn't fixed with this new release, so perhaps if you resolve this, then you will resolve them both.

Doug

< Message edited by DWReese -- 5/11/2021 1:23:47 AM >

(in reply to PaulTheWolf)
Post #: 4
RE: ASBM vs SM-3 Engagement Oddity - 5/19/2021 5:10:12 AM   
Tailhook

 

Posts: 293
Joined: 1/18/2015
Status: offline
quote:

ORIGINAL: PaulTheWolf

Hi user Tailhook, thanks for bringing this to our attention. I've begun reproduction testing with the provided scenario. Could you provide an exception log of the problem when you experience a crash as well? In order to create the Exception Log, navigate to the Config folder in your Command installation directory, and open Command.ini in Notepad or another similar text editor. Find the following line:

LogDebugInfoToFile = False

And set it to

LogDebugInfoToFile = True

Save that file, then open command and run it until a crash occurs. Your exception log will be found in the Logs folder of your CMO Installation directory under the file name ExceptionLog.txt. If you could share that file with us here after a crash it would help our efforts in identifying the cause of the likely memory leak considerably. Thank you again for bringing this issue to our attention!

I keep meaning to do this, I promise I will. Just been busy at work and haven't been able to get to CMO recently.

(in reply to PaulTheWolf)
Post #: 5
Page:   [1]
All Forums >> [New Releases from Matrix Games] >> Command: Modern Operations series >> Tech Support >> [Logged] ASBM vs SM-3 Engagement Oddity 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

0.859