Knightpawn wrote: Sat Jun 27, 2026 8:34 pm

Nikel wrote: Sat Jun 27, 2026 8:23 pm

In steam you should be able to go back to 1825.15

Yes this I can do. But not to any other prior official releases before that

To what version do you want to go back?

let us all just remember that we are expressing frustration over a beta. The purpose of a beta is to be beta tested; and that is what we are essentially all doing since 1825. It is not mandatory to install the betas

Now, having said that, I would like to be able to roll back to any of the ...

Not all bugs of course, because that is impossible.

I am sure CMANO has bugs and the development was stopped and left as it was.

The same will happen to CMO, and will be left with the remaining bugs.

Why not stop now adding more features and naturally complications to fix new and old bugs ...

I created the bug report, because when I deactivated a patrol mission with ACs manually, they RTB.

But when the same was done in a demining mission with naval drones, they just stopped the engines instead of RTB, like the ACs did.

SerLar wrote: Sat Jun 27, 2026 5:42 pm For the standard version running on a 9800X3D:

May you test the last B1892?

But backup first your current Command.exe.

I think this is the line in question, so if the mission is already inactive, it should not happen?

FIXED: #17367: (1884) Units that are currently on-mission when mission is inactivated do not RTB automatically

Well, in this case, this is my second bug report, that is fixed, and backfires.

I will stop creating them


Then, how are my naval drones supposed to RTB, giving them the order one by one.

While this is not a democracy, I would create a poll.

- Continue with current situation, new features are added, new bugs appear or reappear, more complications to fix them. Repeat.

- Stop adding new features completely, only bug fixes, perhaps some tweak.


Considering also that most of CMO users ...

Run the benchmark with B1877 and B1892 to compare the CPU use in the resource monitor and this is the result.

As you see the CPU use has increased significantly, is visible in the graphic and in the average CPU %. In the graphic the periods of 100% use are much more common, also the drops to 0 ...

Another option in the missions, more complications?

Must be related with this thread?

What are they supposed to do?

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

Just created a new scenario with the last build and the problem is the same.


There is a 8 minutes Hold on Waypoint 3 Hold End.

- If you play in the editor, the 8 minutes are progressively reduced until 0 and the mission continues.

- If you play through "Start New Game", the 8 minutes remain ...

I see them working fine in both scenarios uploaded by BDukes and Parel803.

Update.


Playing Top gun scenario today 2 times and no errors.

The difference with respect to yesterday, is that I run the scenario after the benchmark, and the same exceptions happened.

Trying to reproduce it today, I see the exceptions in the log after the running the benchmark, but not after ...

Sorry, I thought this was a well known scenario.

It is included in the CSP and played very fast, you just manage 1 AC, Maverick’s Tomcat

This is what happens here.





This is the json file (in txt format) of the style, the file is much smaller than the rest.

Knightpawn wrote: Fri Jun 26, 2026 6:40 pm
the horror!

Confirmation or condemnation

Both Intel and Nvidia.

Tried putting the files inside folders, 3,4,5... No change.

The style does not seems to be saved between sessions either.

If you change to OpenTopoMap it is also broken. I need to restart CMO for this layer to work again.

Fixed in B1892.

FIXED: Platform constantly flipping between "keep all sensors passive because EMCON dictates so" and "activate all sensors that have active mode because we are under attack"

Must be that line. The flashing is gone