Page 1 of 2
THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
Posted: Sun Feb 07, 2016 10:50 pm
by mikmykWS
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
Posted: Mon Feb 08, 2016 12:57 am
by Tailhook
I am literally the worst at this.
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
Posted: Tue Feb 09, 2016 10:53 am
by 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?
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
Posted: Tue Feb 09, 2016 1:58 pm
by Dysta
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?
My solution is start the scenario in editor mode, and then check the DB version by clicking Editor -> Database at Menu Bar.
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
Posted: Tue Feb 09, 2016 2:17 pm
by Sensei.Tokugawa
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.
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
Posted: Tue Feb 09, 2016 2:30 pm
by Dimitris
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
Posted: Tue Feb 09, 2016 2:34 pm
by zakblood
updated to the newest DB
to include beta builds as meaning they are the latest or the last full release build?
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
Posted: Wed Feb 10, 2016 6:14 am
by michaelm75au
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
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
Posted: Wed Feb 10, 2016 10:07 am
by 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
Posted: Wed Feb 10, 2016 10:34 am
by Dysta
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.
Some Scenario has customized loadouts for specific unit(s), and if you update it, it will all reset to default.
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
Posted: Wed Feb 10, 2016 1:01 pm
by ziolo
ORIGINAL: Dysta
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.
Some Scenario has customized loadouts for specific unit(s), and if you update it, it will all reset to default.
Dysta, so what do you suggest in such cases?
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
Posted: Wed Feb 10, 2016 11:09 pm
by Eggstor
ORIGINAL: ziolo
Dysta, so what do you suggest in such cases?
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.
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
Posted: Sun Feb 14, 2016 5:55 pm
by ziolo
ORIGINAL: Eggstor
ORIGINAL: ziolo
Dysta, so what do you suggest in such cases?
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.
Thanks Eggstor, I will try. There are some scenarios I like to play several times (like from cold war period for example).
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
Posted: Fri Mar 04, 2016 5:51 pm
by magi
So funny......
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
Posted: Sat Mar 05, 2016 10:08 am
by ColonelMolerat
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
Posted: Sat Mar 05, 2016 1:04 pm
by mikmykWS
No. There is a bit on the manual about it. Please do read and let us know if you've got any questions.
Mike
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
Posted: Sat Mar 05, 2016 2:42 pm
by rjantzi
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.
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
Posted: Sat Mar 05, 2016 3:38 pm
by ComDev
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]
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
Posted: Sat Mar 05, 2016 3:55 pm
by rjantzi
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
RE: THOU SHALL NOT REPORT PROBLEM UNLESS SCENARIO UPDATED TO NEWEST DB
Posted: Thu Jun 16, 2016 11:49 pm
by Cafe
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?