Matrix Games Forums

I can't load any of a large selection of Community scenarios (tried several Northern Fury, for example) and got an error for trying to load a DB not present either explicitly or implicitly.

ORIGINAL: Primarchx

I can't load any of a large selection of Community scenarios (tried several Northern Fury, for example) and got an error for trying to load a DB not present either explicitly or implicitly.

I ran into this with some other scenarios. Update them to highest avail DB in CMANO, and they should then go OK in CMO.

I had to do this for the Final Countdown scenarios for example. Was it the ones from the downloaded pack, or the Steam Workshop versions for CMO?

EDIT: Just tried this on a Steam Workshop one as well. Same issue. Someone should poke Baloogan about it...

Looks like the backward compatibility doesn't go very far. Will need to keep CMANO around to update some scenarios far enough for CMO to load them.

EDIT2: found the workshop files, but CMANO freezes trying to load it...
So, whoever uploaded the 'too old' ones to Steam Workshop will have to update them.
I suspect we can update the ones from the downloadable pack with CMANO, the. Baloogan will have to update the Steam Workshop ones.

I think you can copy over missing ones from CMANO folder if you know which are needed, or do as mavfin suggests which is probably the preferred solution.

So I have to move CMANO DB files over to run Community scenarios? I thought CMO was 'fully compatible' with community content.

ORIGINAL: KnightHawk75

I think you can copy over missing ones from CMANO folder if you know which are needed, or do as mavfin suggests which is probably the preferred solution.

No, I had to load it in CMANO, update to the latest DB there, *then* I could load it in CMO and update it further or play it.
Not all, but some, were this way.

Wasn't sure if the old actual DB files would work properly.

It's a CF that needs fixed, and I sent a PM or two. Will see if anyone fixes this mess. I mean, CMO staff uploaded some scenarios into Steam Workshop, and some of them won't work, and same for the 1/5/2019 downloaded pack.

You would have thought someone at least, would have checked that CMO would load them. The devs here do nice work, but some of the testing is a bit thin...

Software and data wise it is compatible. But only the more recent DBs have been included in CMO.

As the latest CP is from Jan 2019, the databases from just before that should have been included if the CP scenarios were to be kept as is.
Including all the previous versions back to 2017 would just be wasted space IMHO.

Sorry about that, guys. It was an oversight. We'll include the older DB files as necessary.

Thanks!

ORIGINAL: mavfin

ORIGINAL: KnightHawk75

I think you can copy over missing ones from CMANO folder if you know which are needed, or do as mavfin suggests which is probably the preferred solution.

No, I had to load it in CMANO, update to the latest DB there, *then* I could load it in CMO and update it further or play it.
Not all, but some, were this way.

Wasn't sure if the old actual DB files would work properly.

It's a CF that needs fixed, and I sent a PM or two. Will see if anyone fixes this mess. I mean, CMO staff uploaded some scenarios into Steam Workshop, and some of them won't work, and same for the 1/5/2019 downloaded pack.

You would have thought someone at least, would have checked that CMO would load them. The devs here do nice work, but some of the testing is a bit thin...

TBF they can't really be expected to check each and every community scenario.
Weird though, I would think the .dat would still have the checksums for validating the older db's even if not actually distributed\included in the cmo install, so in theory I would have thought no problem, guess not.

ORIGINAL: Dimitris

Sorry about that, guys. It was an oversight. We'll include the older DB files as necessary.

Thanks!

Dimitris

Well even better, problem soon solved.

ORIGINAL: Dimitris

Sorry about that, guys. It was an oversight. We'll include the older DB files as necessary.

Thanks!

So, if we still have CMANO, we can copy over into CMO the ones older than the ones listed in the screenshot, without causing problems?

EDIT: No, we cannot. Does not work.

ORIGINAL: KnightHawk75

TBF they can't really be expected to check each and every community scenario.
Weird though, I would think the .dat would still have the checksums for validating the older db's even if not actually distributed\included in the cmo install, so in theory I would have thought no problem, guess not.

When a staff member uploads into the workshop and then advertises in a thread that they'll work fine in CMO, then we should have the expectation that this won't happen. Same with the pack. They advertised the compatibility as a selling point.

Now, other scenarios lying around, like the Final Countdown, which I updated in CMANO, then brought to CMO, I can accept. However, the ones that they advertised as selling points...not so much.

There is a file containing the list of valid DBs so I >think< that it is not a simple case of copying the missing DB files.

Sorry, will add older DBs in the next patch.

ORIGINAL: michaelm75au

There is a file containing the list of valid DBs so I >think< that it is not a simple case of copying the missing DB files.

I just tested. You are correct. Copying over DB files will not do it. If I want to play any of them that don't load, I'll have to update them in CMANO first, then they should load to CMO.

A bit cumbersome, eh?

Someone needs to fix this. Disgraceful for an $80 software package that used those files to advertise backward compatibility.

Last post. Temporary workaround if you *must* play one of the community scenarios that won't load before the devs fix this mess:
Go to the downloaded community pack (don't bother with Steam Workshop CMO files that won't load for now.)
Example, Caribbean Fury 1, Hot Tamales, 1994 CoW.scen is DB3000 version 470. That won't load into CMO.
However, CMANO will load it, and the pack has the ini file. Rebuild it there to latest.
It is now DB3000 version 478, and will load into CMO. You can update it to 480, or play it.

I have not playtested it, but it should work. (I *did* load it. It does load into CMO after updating in CMANO.)

As for me, now that I've tested that, there's plenty of stuff that I hope to hell *does* work.

I hope you guys have tested the DLCs? I'm going to be really disappointed if I try to load a DLC file, and it doesn't load...

Got it. I think I can do that but my CMANO install seems a little fluttery since I installed CMO.

ORIGINAL: mavfin

ORIGINAL: KnightHawk75

TBF they can't really be expected to check each and every community scenario.
Weird though, I would think the .dat would still have the checksums for validating the older db's even if not actually distributed\included in the cmo install, so in theory I would have thought no problem, guess not.

When a staff member uploads into the workshop and then advertises in a thread that they'll work fine in CMO, then we should have the expectation that this won't happen. Same with the pack. They advertised the compatibility as a selling point.

Now, other scenarios lying around, like the Final Countdown, which I updated in CMANO, then brought to CMO, I can accept. However, the ones that they advertised as selling points...not so much.

Yup, fair enough if you're referring to just the pack itself.

There is a file containing the list of valid DBs so I >think< that it is not a simple case of copying the missing DB files.

Yup that's what I meant about the dbinfo.dat, just surprised the entries for old ones weren't left in place.

If I may interject a stupid question here, how do you "update" a CMANO scenario?
Save it in the editor or is there more to it than that.

ORIGINAL: gregb41352

If I may interject a stupid question here, how do you "update" a CMANO scenario?
Save it in the editor or is there more to it than that.

You'll want to open it in the editor, go to the Editor->Database menu and select the Upgrade Scenario to Latest Database option. Then save it.

Uploaded a bunch of the older DB files here: https://drive.google.com/open?id=1ryPqp ... yEPYtXUMhm

To use them, simply unzip the file to your [CMO]\DB folder.

If you find any scenario that is not covered by those, please let us know and we'll investigate it separately.

Thanks.

ORIGINAL: Dimitris

Uploaded a bunch of the older DB files here: https://drive.google.com/open?id=1ryPqp ... yEPYtXUMhm

To use them, simply unzip the file to your [CMO]\DB folder.

If you find any scenario that is not covered by those, please let us know and we'll investigate it separately.

Thanks.

Doesn't actually work. Go to workshop *or* the downloadable community pack. Try Baltic Fury 1 or Caribbean Fury 1 (CoW or not) and they won't load. DB 470 if you load them in CMANO. If I update it *in CMANO* to highest there, it'll load fine in CMO.

Caribbean Fury 2, DB475, will load fine, but it will load fine without the DB files you posted, too.

i.e. no change. I suspect it's the DBinfo.dat causing it to not see them as valid, I think someone said?

EDIT2: worked once I got the 470 file from CMANO. Why it didn't work last night, I don't know.
So, Dimitris, get the 470 file added for people who don't have it, should help with Fury scens.