Matrix Games Forums

When I try to switch the DB version of the attached SAVE (currently on DB build 470), the function "Upgrade scenario to latest DB version" tells me that it is using the latest DB version albeit that the latest DB version is 473.
If I try to switch the DB version manually to 473 or an older one, all units in the SAVE are deleted.

Is this intended behavior or a possible issue?

Please have a look.

Thx and kind regards
Hamlet

This is not intended behaviour, sounds like you may be missing the latest DB files. Do v471, 472 and 473 exist in your db folder?

Yes, they do. db3k_467.db3 to db3k_473.db3 all have the date/time when I installed the beta.

I installed the beta over a full install with manual update history up to UpdatePack_B972.14, then I unzipped the beta over it.

Everything is working except this behavior.

Regs
Hamlet

Hmmm weird.

Is the DBInfo.dat file in the DB folder dated 27 January 2018?

Yes. Creation date 27th of January 2018, 12:44, Modification date is when I installed the beta version - same as the db3 files named earlier.

I checked with a scen file (Uncle Marks Tutorials - 5 - Motozintla Incursion, 2015 972.10.scen) I had modified. Same behavior as described above.

To test, I replaced the DB folder with all files/subfolders from the 972.14 install backup I had created before installing the BETA.

The function "Upgrade scenario to latest DB version" tells me now correctly that it is using the latest DB version 470.
If I try to switch the DB version manually to an older db version, all units in the SAVE are deleted.

So maybe the root cause for the behavior is outside the DB folder and it's files.

I just downloaded the save. Started it up and checked it was db 470. Upgraded to latest db without ini file with no issue. Scenario started with no issues.

Under 1.14 beta.

Hello everyone!
I think I have a similar problem...whenever I try to switch from the current DB to another one (older or newer), all the units on the map disappear.
I have this issue with every scenario: community, standard or my own scenarios.
Am I doing something wrong or it's meant to do that?

Problem resolved?

Correct, you're not supposed to downgrade. Selecting an older database will create a blank scenario file.

Problem is partly resolved with my installation under B998.2. Used the posted scenario which refers DB 470

"Upgrade scenario to latest DB version": Works with B998.2

Try to switch the DB version manually to 471, 472, 473: all units in the SAVE are deleted, game time is reset, etc.. (assume a blank scenario file) Would think that this should work, but I am not sure if I tried it in earlier versions of Command.

Try to switch the DB version manually to version lower than 470: As emsoy posted earlier this is not supposed to work on purpose.

regs
Hamlet

Erm... You need to rebuild the scen using the Rebuild functionality.

Hi emsoy,

yes on "rebuild the scen using the Rebuild functionality", and that works in 998.2 again in my installation.

From your earlier post I understood that downgrading to an older db version creates a blank scenario file.

If I upgrade to a newer db version, the same happens for me and a blank scenario file is created. If this is the intended behavior, then fine and issue closed. I was just unsure if this is an issue or intended behavior as I can't remember to have tried it in earlier command releases

Thx
Hamlet

I just reinstalled Command after doing some HD clean up. My standard benchmarking scenario is Op Bass Drum modified. It was on db470 when I copied it over from my back up. As above, when I do a rebuild, it says I am on the latest db. I double check and it still says 470 is the db, even though 471, 472, and 473 are listed above it. I hit OK and continue with the rebuild. I deep rebuild with an ini file. I save it. I reload it. It still says 470. I repeat the entire process and it does exactly as above.

Not sure if I am doing something wrong or not.