Matrix Games Forums

I am using the latest public Beta version (1706) of the game found here :https://forums.matrixgames.com/viewtopic.php?t=411954

Issues to note:

1) Can't shoot down US satellites with SC-19 ASAT batteries. Not sure if I am doing something wrong but no matter what I do-setting the China ASAT batteries to free opportunity fire or manual fire- they never attack the US satellites even within range. I keep getting the text that they are out of DLZ range even if the satellites hover within the missile zones.

2) ASBM batteries are out of range of US carrier force. Not sure if the Beta made ASBMs with less range but now I notice the red circle range is far away from the Carrier. I fixed this by moving the ASBMs to Manchuria in the editor but it is something to flag as their current position means you cannot get to the carrier. Given the importance of sinking the carrier to get 2000 points in the campaign this may be a "scenario breaking" issue.

3) Land-based SSBMs out of range of Okinawa. Specifically batteries 815 Brigade 1st battery and 2nd battery. Again, fixed this in the editor by moving them closer but still something to flag.

It is a fun and great scenario, just feel these should be resolved to make it even better. . I've attached the scenario file from my folder for reference.

Regarding 1. It is explained in the video below by Eboreg, 21:10

https://youtu.be/VJ5qnnZVW8U?t=590


3. They are mobile batteries, you can move them by road.

Interesting, I tried the ASAT tip and it seemed to work in a couple cases. I guess the idea is that you have to manually mark a satellite beforehand so that the missiles can eventually get a lock-on? Although my biggest complaint is that it is so random. I get it, you are trying to fire a missile at a fast moving object in space. But at least make it easier to fire a missile when a satellite is overhead. Just my thoughts though.

As for the batteries, you can move the SSBMs closer to Okinawa but it will take like half the scenario. The ASBMs are way too far though, the scenario would end by the time you get them in range of the carrier. You could only hit one ship closer to South Korea.

Tool3333 wrote: Wed Aug 27, 2025 4:28 pm Interesting, I tried the ASAT tip and it seemed to work in a couple cases. I guess the idea is that you have to manually mark a satellite beforehand so that the missiles can eventually get a lock-on? Although my biggest complaint is that it is so random. I get it, you are trying to fire a missile at a fast moving object in space. But at least make it easier to fire a missile when a satellite is overhead. Just my thoughts though.

That is my guess, to be honest I never fired to a sat while playing CMO until now.

Tool3333 wrote: Wed Aug 27, 2025 4:28 pm As for the batteries, you can move the SSBMs closer to Okinawa but it will take like half the scenario. The ASBMs are way too far though, the scenario would end by the time you get them in range of the carrier. You could only hit one ship closer to South Korea.

Indeed the ASBMs carriers are more tricky, there seems to be a small window depending of the movements of the Ronald Reagan carrier. You have to move the northern battery to the East at flank speed. The second units are slower for some reason.

I do not know why the range of the DF-21D has been reduced from 1100 nm to 835 nm.

And the scenario time is very limited, perhaps should be increased?

Anyway I guess the DF-21D are there not just to sink carriers, but also to avoid their presence near to China.

Tool3333 wrote: Wed Aug 27, 2025 4:28 pm Interesting, I tried the ASAT tip and it seemed to work in a couple cases. I guess the idea is that you have to manually mark a satellite beforehand so that the missiles can eventually get a lock-on?

Yeah may be the best move or assign it to a strike mission with fairly loose WRA. It's very hard in this game to visualize the best firing parameters with many engagements beyond matching speeds and altitudes without simulating it outside the scenario. WRA was used to handle that problem (largely well!) with atmospheric weapons.

This being said I'm not sure if the WRA precalculations account for separating warheads, etc. This would be for a dev to answer or something to test and research.

M

Ok, I figured out ASAT and it seems to make sense. it seems that in order for the missiles to fire the satellites have to be hovering directly above the battery. Basically, the missiles can't guide themselves to the satellite: the satellite must be directly in front of the battery so that the missile fires in a straight line. It means you can only go for a select number of satellites.

Tool3333 wrote: Wed Aug 27, 2025 11:59 am 2) ASBM batteries are out of range of US carrier force. Not sure if the Beta made ASBMs with less range but now I notice the red circle range is far away from the Carrier. I fixed this by moving the ASBMs to Manchuria in the editor but it is something to flag as their current position means you cannot get to the carrier. Given the importance of sinking the carrier to get 2000 points in the campaign this may be a "scenario breaking" issue.

3) Land-based SSBMs out of range of Okinawa. Specifically batteries 815 Brigade 1st battery and 2nd battery. Again, fixed this in the editor by moving them closer but still something to flag.

Fixed. Adjusted the ASBM and SRBM positions.

Here is the updated scenario (by Kushan). It will also be included on the next update release.

Dimitris wrote: Sat Aug 30, 2025 9:46 am Here is the updated scenario (by Kushan). It will also be included on the next update release.

Thanks, I am getting an error though and can't open the scenario on the start menu(the scenario description goes on a coded tangent too)? Not sure if you see it too? Th scenario file size seems small so not sure if that is the reason. Anyway, just flagging in case the scenario does not work upon the update.

You are right, this is the error:

ERROR - Unable to load scenario! Please copy this entire text and submit it to the dev team for investigation. Exception: The process cannot access the file 'C:\Matrix Games\Command Modern Operations\Scenarios\Tests\4. Salvo.scen' because it is being used by another process. Exception source: mscorlib Stack Trace: at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy) at System.IO.FileStream..ctor(String path, FileMode mode) at Command_Core.ScenContainer.LoadFromFile(String theFileName) at Command.LoadScenario.WeeUnIieTWAvrvld2Kdr(Object ) at Command.LoadScenario.LoadFromPath(String thePath, String selFilename)

SImilar to this one reported by Quixotic1917.


https://forums.matrixgames.com/viewtopic.php?t=412737


However it is not as corrupted, in this case there is content, the scenario requires db 513, we cannot load it anyway.

Nikel wrote: Tue Sep 09, 2025 7:52 am You are right, this is the error:

ERROR - Unable to load scenario! Please copy this entire text and submit it to the dev team for investigation. Exception: The process cannot access the file 'C:\Matrix Games\Command Modern Operations\Scenarios\Tests\4. Salvo.scen' because it is being used by another process. Exception source: mscorlib Stack Trace: at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy) at System.IO.FileStream..ctor(String path, FileMode mode) at Command_Core.ScenContainer.LoadFromFile(String theFileName) at Command.LoadScenario.WeeUnIieTWAvrvld2Kdr(Object ) at Command.LoadScenario.LoadFromPath(String thePath, String selFilename)

SImilar to this one reported by Quixotic1917.


https://forums.matrixgames.com/viewtopic.php?t=412737


However it is not as corrupted, in this case there is content, the scenario requires db 513, we cannot load it anyway.

I got the same error with the scenario Dimitris posted but not this one, which is the one I sent to him. Maybe the scenario got corrupted somewhere. Please give this one a go when you can and let me know if it works or not.

We need db 513 to load it

But the above error is not displayed.

Kushan04 wrote: Tue Sep 09, 2025 6:23 pm

Nikel wrote: Tue Sep 09, 2025 7:52 am You are right, this is the error:

ERROR - Unable to load scenario! Please copy this entire text and submit it to the dev team for investigation. Exception: The process cannot access the file 'C:\Matrix Games\Command Modern Operations\Scenarios\Tests\4. Salvo.scen' because it is being used by another process. Exception source: mscorlib Stack Trace: at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy) at System.IO.FileStream..ctor(String path, FileMode mode) at Command_Core.ScenContainer.LoadFromFile(String theFileName) at Command.LoadScenario.WeeUnIieTWAvrvld2Kdr(Object ) at Command.LoadScenario.LoadFromPath(String thePath, String selFilename)

SImilar to this one reported by Quixotic1917.


https://forums.matrixgames.com/viewtopic.php?t=412737


However it is not as corrupted, in this case there is content, the scenario requires db 513, we cannot load it anyway.

I got the same error with the scenario Dimitris posted but not this one, which is the one I sent to him. Maybe the scenario got corrupted somewhere. Please give this one a go when you can and let me know if it works or not.

Thanks! Unfortunately I get the error " ERROR: You have (explicity or implicity) attempted to load a database that does not exist on the DB folder."

I am using the Biuld 1706 version of the game, not sure if the DB being mentioned is for the next update? Don't want to burden you and the others as I have my own scenario version with the launches moved within range of the targets and can happily wait for the revised scenario upon release of next update.