quote:

ORIGINAL: Primarchx

I was just advised in Tech Support (by another user) to copy over db files from CMANO. That doesn't work very well for new players who have been told that there are hundreds of community scenarios to play along with the fact that I have to do file operations to get the game to work right.

quote:

ORIGINAL: mavfin

quote:

ORIGINAL: Primarchx

I was just advised in Tech Support (by another user) to copy over db files from CMANO. That doesn't work very well for new players who have been told that there are hundreds of community scenarios to play along with the fact that I have to do file operations to get the game to work right.

To be clear, I'm not very happy with that solution. They really need to fix this complete CF.
They uploaded a bunch of files to Steam Workshop that wouldn't load into CMO because of DB versions, and the Community Scenario Pack hasn't even been updated for CMO *at all*. Still shows 1/5/2019, I guess.

If they were selling the software for 20 bucks, might be different...but they're not.
I just spent 90 bucks counting TacView, even with discounts, so I'd like a bit more care with things from the staff.

quote:

ORIGINAL: ultradave

I guess I've been lucky. I haven't found any that don't work yet.

quote:

ORIGINAL: ultradave

Maybe there is a misconception. The Community scenarios are not the responsibility of the developers. They were all (all 400+ of them) developed by users and distributed. They didn't come with C:MANO. To blame the developers for some of them not working is unfair.

To get the ones that don't to work will probably require the developers of those scenarios to do a little work and then have a "pack" compiled and added to over time, just as the current one has been. I would expect that will start happening. Unfortunately some of the scenario authors have kind of vanished, as has been evident when questions or issues come up with previous C:MANO updates. Maybe someone will adopt those.

I think "CF" was way over the top considering the above, but you're entitled to your opinion.

quote:

ORIGINAL: mavfin
They're going to fix it, so that's fine. Just noting why I didn't give them a pass on the community scenario pack stuff. Community scenarios not in the pack and/or not uploaded into CMO's section of Steam Workshop do fit the 'not responsible for' description you noted, IMO.

EDIT: For example, go pull Caribbean Fury 1 from the CMO Steam Workshop, and try to load it into CMO. Look who uploaded it.
Again, they're going to fix it, I'm just pointing out why I thought it was important to not just 'give them a pass' on them.

quote:

ORIGINAL: Kushan04
According to the excel file in the latest build all of the scenarios should be using DB476 which is included in CMO but there's been reports that not all of them are.

quote:

ORIGINAL: Kushan04

Hi guys. Meroka37 who was the previous curator of the community scenario pack so I've volunteered to take over curating it. According to the excel file in the latest build all of the scenarios should be using DB476 which is included in CMO but there's been reports that not all of them are. It hasn't been updated since January so my first goal is going to be to get the pack updated with the scenarios that have been released in 2019 and ghet that sent off to the devs. After that I'll be working on writing a batch script that will allow me to batch update all of the scenarios but there will be over 460 scenarios so its going to take me a few days (I want to play the game to).

quote:

ORIGINAL: mavfin
They're going to fix it, so that's fine. Just noting why I didn't give them a pass on the community scenario pack stuff. Community scenarios not in the pack and/or not uploaded into CMO's section of Steam Workshop do fit the 'not responsible for' description you noted, IMO.

EDIT: For example, go pull Caribbean Fury 1 from the CMO Steam Workshop, and try to load it into CMO. Look who uploaded it.
Again, they're going to fix it, I'm just pointing out why I thought it was important to not just 'give them a pass' on them.

The reason Baloogan uploaded it is because Meroka had disappeared and there was no one else to do it.

quote:

ORIGINAL: Kushan04

Hi guys. Meroka37 who was the previous curator of the community scenario pack so I've volunteered to take over curating it. According to the excel file in the latest build all of the scenarios should be using DB476 which is included in CMO but there's been reports that not all of them are. It hasn't been updated since January so my first goal is going to be to get the pack updated with the scenarios that have been released in 2019 and ghet that sent off to the devs. After that I'll be working on writing a batch script that will allow me to batch update all of the scenarios but there will be over 460 scenarios so its going to take me a few days (I want to play the game to).

quote:

ORIGINAL: mavfin
They're going to fix it, so that's fine. Just noting why I didn't give them a pass on the community scenario pack stuff. Community scenarios not in the pack and/or not uploaded into CMO's section of Steam Workshop do fit the 'not responsible for' description you noted, IMO.

EDIT: For example, go pull Caribbean Fury 1 from the CMO Steam Workshop, and try to load it into CMO. Look who uploaded it.
Again, they're going to fix it, I'm just pointing out why I thought it was important to not just 'give them a pass' on them.

The reason Baloogan uploaded it is because Meroka had disappeared and there was no one else to do it.

quote:

ORIGINAL: Gunner98

Baltic Fury 1 rebuilt with a couple of other fixes. So the process works, it will take me a solid day to go through them all, and I won't be able to commit to that for a couple weeks yet.

B

quote:

ORIGINAL: Gunner98

It seems some of the 'Fury' scenarios are not working, maybe because they are in a separate folder in the community pack and perhaps didn't get updated.

Baltic Fury 1 for sure, and I see Caribbean Fury listed here, maybe others.

Kushan - Didn't realize Meroka37 had moved on, thanks for stepping up to the plate on this. Is there anything I can do to help? When I checked out Baltic Fury I couldn't access it from CMO so thought I would go back to CMANO, update the DB and then try it in CMO. That should work and I can go through them all. I usually do that once a year to apply various fixes to them anyway, but not until the Xmas holidays. I assume you're working on a faster time-line so can try and do it sooner.

B

quote:

ORIGINAL: Dimitris

Uploaded a bunch of the older DB files here: https://drive.google.com/open?id=1ryPqpb9-hhPq_s1zgePvp_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.