Matrix Games Forums

Hey guys,

I tried to play a scenario from the community pack (latest one from WarfareSims website, running on Steam Build SR7 nine hundred and six point twenty six). The scenario was "Closing the Kurile Gap". I had the same error trying to play a few other community scenarios too.

Is there a fix?

Sounds like you are missing a database. Run the game Steam integrity check

ORIGINAL: michaelm

Sounds like you are missing a database. Run the game Steam integrity check

Didn't work!

Steam validated 37 files but I'm still getting the error

Did a fresh install, still not working.... same problem!

I downloaded the scenario pack 34 from Steam's Workshop and I got no errors. All scenarios are fine. I think pack 35 is broken.

The latest pack, which I believe is 35, is fine. I'm using it.

I am getting the same error with 35

IIRC, it has something to do with the scenario's units. If there were any modifications done on a unit, there's a chance that it might have been "bugged". Usually copying that modified unit will cause the problem. AFAIK this problem started when the database was updated during the release of the Korean Missile Crisis.

I've started to notice this problem when I was working on my ship templates where if I copied a modified unit, the information on the sidebar will display the previous selected unit. Everything can still work even the edited attributes will work as intended (but won't display properly), but once you saved the scenario you can't access it again (thread title).

One way to simulate this problem is editing a simple unit. For example I'll use the Patriot SAM. Then I keep adding the M901 Launch Station to meet my needs, but if you add "too much" then you will soon face this bug.

Before the Korean Missile Crisis update, there was no problems about this. You could add as much weapons/sensors to a unit without facing this kind of problem.

Edit:
It seems that the current version of the DB doesn't face this problem anymore. I'm not exactly sure when was this problem "fixed" because I haven't touched CMANO in a while. However the problem did really happen during the KMC update and before the fix for this.

When you say "The current version fo the database", I have the most recent version I believe (using steam). Is there a newer one?

I'm assuming that's the reply to my edit. What I'm referring to as the "current" one is the DB3K 464 (SR7-B906.26).

I stand by what I said earlier about the Community Pack 34 working with the latest CMANO update while a few Community Pack 35 scenarios don't work. For example: H Hour from Northern Furry series and Closing the Kurile Gap from War that Never Was series.

I can't even open the scenarios using the editor (from CP 35).

I do have DB 3K 464 installed.

Hi Guys

Thanks for your reports.

Something is definitely up. We've had a non steam report so it may not be linked. I've added a ticket and sent some files in for our wizards to look at.

Thanks

Mike

I'm after this guys

It isn't every scenario in CP35, most of the ones I selected are loading okay. The stated 'Closing gap' ones fail for me too.

Hi guys, can you re-try this with the very latest exe. Are the scens loading correctly now?

Strike last, the files are corrupted. The bug that caused the corruption should now be fixed.

Thanks!

It appears that the problem is not fixed yet. I´m using Build 936.2, and when I try to load several community scenarios (for example: Northern Fury 8) an error message appears, different from the previous one:

ERROR! The scenario is probably corrupted, could not determine which database to use!



When I clic "Accept", the same message than before shows up (Object reference not set to an instance of an object)

Am I missing something?

If the problem is that some of the files are corrupted in the pack, then the scenario pack has not yet been fixed. The bug causing the corruption has been fixed, but not the corrupted files, unless I misunderstood.

Mav

So... in that case what I would be "missing" is reading comprehension [:D]

Thanks!

Yeah, i get the same error with Northern Fury 8, and I'm using the Release Candidate B936.2.

I suspect the maintainer of the pack is scrambling around verifying all the files in the pack, and then finding good copies to update/rebuild the corrupt ones.

It'll take some time. That's a LOT of files.

Mav