THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
Moderator: MOD_Command
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
I am literally the worst at this.
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
Maybe silly question... Let us consider that I have just updated the CMANO to the newest version. How do I know that any specific scenario has been updated to the newest DB?
C/MANO - The Digital Wargame of the Year
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
My solution is start the scenario in editor mode, and then check the DB version by clicking Editor -> Database at Menu Bar.ORIGINAL: ziolo
Maybe silly question... Let us consider that I have just updated the CMANO to the newest version. How do I know that any specific scenario has been updated to the newest DB?
- Sensei.Tokugawa
- Posts: 341
- Joined: Mon Apr 05, 2010 9:06 pm
- Location: Wieluñ, Poland
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
As a matter of fact on returning to the game after a few months had passed I was nicely surprised how smooth it seems to work and how much depth has apparently been added and just to think that I must have only skimmed the surface a bit so far. I wonder how I was playing that back in mid 2014? Let's call it a credit of trust or something. Well done Mike and the team, really well done.Great job.
"-What if one doesn't make it?
-Then we know he was no good for SpetsNaz. ..."
V. Suvorov, "Spetsnaz;the Story behind the Soviet SAS"
...No escape from Passchendaele .../ God Dethroned, "Passiondale"
-Then we know he was no good for SpetsNaz. ..."
V. Suvorov, "Spetsnaz;the Story behind the Soviet SAS"
...No escape from Passchendaele .../ God Dethroned, "Passiondale"
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
ORIGINAL: ziolo
Maybe silly question... Let us consider that I have just updated the CMANO to the newest version. How do I know that any specific scenario has been updated to the newest DB?
Here is an example:
In this case we see that the scenario uses DB3000 v424, while the most recent version of this DB available on this setup is v442 Beta 1.
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
to include beta builds as meaning they are the latest or the last full release build?updated to the newest DB
Windows 11 Pro 64-bit (10.0, Build 22621) (22621.ni_release.220506-1250)
- michaelm75au
- Posts: 12455
- Joined: Sat May 05, 2001 8:00 am
- Location: Melbourne, Australia
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
I would think the non-beta one as the beta are usually ones still in transit.[:D].
Also you will need to skim down pass all the DB3000 ones to get to the CWDBs
Also you will need to skim down pass all the DB3000 ones to get to the CWDBs
Michael
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
Thanks guys. I will include this as s routine check: case a scenario uses an old version, we need to run "Upgrade scenario to latest DB version" from the Editor/DataBase menu.
C/MANO - The Digital Wargame of the Year
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
Some Scenario has customized loadouts for specific unit(s), and if you update it, it will all reset to default.ORIGINAL: ziolo
Thanks guys. I will include this as s routine check: case a scenario uses an old version, we need to run "Upgrade scenario to latest DB version" from the Editor/DataBase menu.
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
ORIGINAL: Dysta
Some Scenario has customized loadouts for specific unit(s), and if you update it, it will all reset to default.ORIGINAL: ziolo
Thanks guys. I will include this as s routine check: case a scenario uses an old version, we need to run "Upgrade scenario to latest DB version" from the Editor/DataBase menu.
Dysta, so what do you suggest in such cases?
C/MANO - The Digital Wargame of the Year
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
If there's already a scenario.ini file, the custom loadouts should remain after the rebuild. If not, first create a scenario.ini file, then rebuild.ORIGINAL: ziolo
Dysta, so what do you suggest in such cases?
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
Thanks Eggstor, I will try. There are some scenarios I like to play several times (like from cold war period for example).ORIGINAL: Eggstor
If there's already a scenario.ini file, the custom loadouts should remain after the rebuild. If not, first create a scenario.ini file, then rebuild.ORIGINAL: ziolo
Dysta, so what do you suggest in such cases?
C/MANO - The Digital Wargame of the Year
-
- Posts: 479
- Joined: Wed Sep 23, 2015 10:36 am
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
Eep. I misunderstood - I thought it happened automatically when Steam updated. Sorry if I've done this!
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
No. There is a bit on the manual about it. Please do read and let us know if you've got any questions.
Mike
Mike
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
Couple of questions.
Are the Standalone & Tutorial scenarios updated when new DB's come out? I've randomly looked thru some scenarios and it seems like these are all using the current DB's whereas the Community scenarios are using older DB's. Is it correct to say that we only need to rebuilt the Community Scenarios?
Secondly, after reading the manual, it seems to me that a shallow rebuild is what would be required in these cases, correct?
Thanks for your help.
Are the Standalone & Tutorial scenarios updated when new DB's come out? I've randomly looked thru some scenarios and it seems like these are all using the current DB's whereas the Community scenarios are using older DB's. Is it correct to say that we only need to rebuilt the Community Scenarios?
Secondly, after reading the manual, it seems to me that a shallow rebuild is what would be required in these cases, correct?
Thanks for your help.
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
1) Yes, we rebuild the official scenarios with new databases (there may be exceptions when a new database adds stuff that do not affect existing scens), so you only need to rebuild community scenarios.
2) Shallow rebuild might work in some cases [8D]
2) Shallow rebuild might work in some cases [8D]
Developer "Command: Modern Air/Naval Operations" project!
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
Thanks Emsoy, I just tried updating the DB for one scenario and it seems to have worked fine.
This has lead to another couple of questions:
1) When would you use the "Change Database" function rather than the "Upgrade Scenario to latest DB version" option?
2) If I want to update a scenario that doesn't have a config file, the manual says this can be exported from the existing scenario, how do I do this? EDIt: I think I just found this, Editor/SBR/Generate Delta Template, correct?
Rob
This has lead to another couple of questions:
1) When would you use the "Change Database" function rather than the "Upgrade Scenario to latest DB version" option?
2) If I want to update a scenario that doesn't have a config file, the manual says this can be exported from the existing scenario, how do I do this? EDIt: I think I just found this, Editor/SBR/Generate Delta Template, correct?
Rob
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
You could make this idiot proof by saving the db version with the scenario and then not allowing the scenario to load if the db version in the scenario <> db version of game?
A pop up indicating the reason for the non-load and maybe a friendly "Do you want to upgrade scenario now?" option?
A pop up indicating the reason for the non-load and maybe a friendly "Do you want to upgrade scenario now?" option?
Be nice.