RE: CMANO updated to version 1.14.9

[behemon]

this is another buggy update

after installing it, I'm unable to load many scenarios, including autosaves

here is what I get:

[DWReese]

I'm having the same problem with some scenarios.

Doug

[Dimitris]

ORIGINAL: behemon

this is another buggy update

after installing it, I'm unable to load many scenarios, including autosaves

here is what I get:

Can you please describe precisely, step-by-step, what you are doing and encountering this error. We need literally every single mouse click (and the scenario name). Thanks.

[Dimitris]

Also: Are you running a Steam or Matrix version?

[DWReese]

I am using the Matrix version.

When I try to load some (not all) scenarios, I get the series of error boxes. It looks exactly like what behemon is displaying.

Doug

[behemon]

I do not know how more precisely can I describe the problem. Every box, top to bottom, represents a left click on OK button.
This happend for the first time with "USSR storms the line" scenario, just after the update (started playing it before the update).
Many other scenarios show the same symptoms (not all).
Chains of War scenarios seem ok though.
Yesterday (before the update) I also played "Iran escalation 2017", but had to leave it as all autosaves got corrupted. After loading an autosave, there was no units on the map unless I zoomed in the game to say camera alt less than 70000m.
I run a Steam version of the game.
Thank you.

[Dimitris]

ORIGINAL: behemon
I do not know how more precisely can I describe the problem. Every box, top to bottom, represents a left click on OK button.

Okay, but which steps did you take _before_ seeing that first "OnThreadException" message? We need to know exactly what you did in order to try to reproduce the problem here.

[behemon]

1. left click on Start new scenario button (in Start Menu)
2. left click on a desired scenario in order to highlight it
3. left click on Load selected button
4. the next window shows that "OnThreadException" message

[DWReese]

You select the Load Scenario (I did it from the Editor).

The screen pops up showing the scenario description.

When you click on OK, you begin getting all of these error boxes.

Doug

[Dimitris]

ORIGINAL: behemon
1. left click on Start new scenario button (in Start Menu)
2. left click on a desired scenario in order to highlight it
3. left click on Load selected button
4. the next window shows that "OnThreadException" message

Thanks! This is the sequence we are also trying here, on multiple machines, and it's not generating an error anywhere so far.

If you are using Steam, can you please try to completely uninstall (back up your custom saves/mods first) and re-install?

[Dimitris]

Also, can you please list here the scenarios in which the problem appears, and any scenarios that load without issues, so that we can try to narrow down the cause of the problem.

[Dimitris]

Also, what version of Windows are you using? (Asking because there have been cases of bugs showing up only on specific versions of Windows).

[DWReese]

Windows 8.1

[DWReese]

I get the same error whether I start from game from the Editor or from the Game menu.

The LIVE scenarios are affected as well.

Doug

[DWReese]

Of the 11 LIVE scenarios, only Spratly and the new one Border work. The rest all give the same error.

Could it have something to do with ini files? We haven't used a new ini file on Border as of yet?

Doug

[DWReese]

Nope.

Ini files are the problem. I just trued a bunch without ini files and the same problem occurred.

Doug

[Dimitris]

Anyone else experiencing this issue? If yes, please describe your OS and list the scenarios that work and don't work for you. Thanks.

[RoryAndersonCDT]

Please post the scenario file that is definitely causing the problem for you

[DWReese]

Pretty much EVERY scenario. Let's rake all of the LIVE scenarios. I own ALL of them. The only two that will open are Spratly and the new one, Border. I have all kinds of community scenarios that won't open either. I'd say that 80 percent won't open.

Doug

[DWReese]

Is it possible to reload 1.14.8 at my end? That version didn't have any problems. Or, have you been able to identify it as of yet?