Mission Commander beta release
-
@drtbkj said in Mission Commander beta release:
I have a solution to my issue, at least. Go into the theater.list file and put TerrData\TheaterDefinition\Korea KTO.tdf on the top line
Annoyingly, AL alphabetically reorders the theater.lst on start.
-
Do we need to wait for a new version on MC to work with the new 4.36 ?
I tried to open campaign mission in MC (working fine with 4.35U3) but got error messages . . .
-
@regev To make it short: Falcas said that January’s current version is good, and that he would anyway release a new version soon to upgrade it.
However some of us are encountering troubles to convert older files (cam, for my part) from 35 to 36. We’re then just waiting and seeing.
-
I am running into an issue of cannot find a camo.cfg file.
-
Managed to convert Middle East theater mission from 4.35 to 4.36.
The mission file version has changed to number 108.
There were no problems. -
@SpbGoro said in Mission Commander beta release:
Managed to convert Middle East theater mission from 4.35 to 4.36.
The mission file version has changed to number 108.
There were no problems.Could you make it work just in KTO 35 to 36, for a test, and maybe tell us what we don’t do right?
-
@LorikEolmin said in Mission Commander beta release:
Could you make it work just in KTO 35 to 36, for a test, and maybe tell us what we don’t do right?
Copy the files “korea.wch” and “korea.idx”
From a folder
“Falcon BMS 4.35\Data\Campaign”
to a folder
“Falcon BMS 4.36\Data\Campaign”Then do the conversion of the mission you need from KTO 4.35.
After conversion, these files can be removed from 4.36.
These are files of object names (obj strings) on the map. In version 108, the object names are stored within the campaign/mission file itself. -
@SpbGoro Just tried that; didn’t work for me.
But my problem is probably that described by criticalmass above. AL doesn’t even respect the read-only property, so my “theater.lst” keeps being overwritten.
And I also couldn’t figure out how to stop MC from using “Falcon BMS 4.36\data\Terrdata\objects” as its database directory.
So I finally removed all theaters except Korea KTO (editing the “Theater.lst” file accordingly), reinstalled MC–this time it presented its old “Please select theater” dialog–and it used the KTO database. I even added the files “korea.wch” and “korea.idx” (as suggested by SpbGoro above). But MC still failed to convert my 4.35 .tac file.
So I think we definitively need to wait for Falcas to provide an update, or at least a set of Conv files…
-
Sorry guys but conversion works fine for 4.35 to 4.36 …
You can convert SaveX.cam and TEs but please, never convert on-going campaigns (it will simply create issues)!!!
Use the conversion tab and the WCH files are now a thing of the past with 108 format (objectives names are now set directly in the cam file).
Use the advanced objective tabs to clean that up…
Cheers
-
@SpbGoro said in Mission Commander beta release:
@LorikEolmin said in Mission Commander beta release:
Could you make it work just in KTO 35 to 36, for a test, and maybe tell us what we don’t do right?
Copy the files “korea.wch” and “korea.idx”
From a folder
“Falcon BMS 4.35\Data\Campaign”
to a folder
“Falcon BMS 4.36\Data\Campaign”Then do the conversion of the mission you need from KTO 4.35.
After conversion, these files can be removed from 4.36.
These are files of object names (obj strings) on the map. In version 108, the object names are stored within the campaign/mission file itself.Thanks, I’ll try that when I’m back home. Still better trying something that might work than convincing myself something works when it obviously doesn’t want to :).
-
Something is weird with the January version of MC. As you can see from this screenshot, even though MC knows that my Falcon is 4.36, the current objectives set is from 4.35
I get all sorts of error messages when importing a 4.35 TE, probably because of this?
-
did you point 4.36 as your BMS installation in mission commander?
-
@jayb said in Mission Commander beta release:
Something is weird with the January version of MC. As you can see from this screenshot, even though MC knows that my Falcon is 4.36, the current objectives set is from 4.35
I get all sorts of error messages when importing a 4.35 TE, probably because of this?
Ah, I’m not sure I paid attention to that, but it rings a bell, some sort of “Ah, damn there’s still 4.35 written there, bah”. I think it’s in this place.
Also, I see we’re using the last public version we have, 667 from January 22.
-
@MaxWaldorf yes I did and it was registered as the screenshot shows. If someone manages to convert a 4.35 TE to 4.36 please show some relevant screenshots
-
Seems this is getting us nowhere.
There are now several people declaring they can’t convert, some providing screenshots with their path setups in an honorable effort to show they aren’t complete idiots. (Which in my case I am perfectly fine to accept being one )Would someone of those believing in a working system be so kind to try to convert the following TE:
https://drive.google.com/file/d/12P-RhCFw0HYDwU9xqXw6PXEOuDQPQWQI/view?usp=sharing(I swear this is a functioning TE flewn many times without issues in 4.35U3 - Korea KTO)
Maybe this way we can at least settle whether it’s a machine/user versus a file/data issue?
And in the former case get to a step-by-step procedure.Many thanks in advance.
-
@jayb said in Mission Commander beta release:
Something is weird with the January version of MC. As you can see from this screenshot, even though MC knows that my Falcon is 4.36, the current objectives set is from 4.35
I get all sorts of error messages when importing a 4.35 TE, probably because of this?same for me!
-
@SpbGoro said in Mission Commander beta release:
@LorikEolmin said in Mission Commander beta release:
Could you make it work just in KTO 35 to 36, for a test, and maybe tell us what we don’t do right?
Copy the files “korea.wch” and “korea.idx”
From a folder
“Falcon BMS 4.35\Data\Campaign”
to a folder
“Falcon BMS 4.36\Data\Campaign”Then do the conversion of the mission you need from KTO 4.35.
After conversion, these files can be removed from 4.36.
These are files of object names (obj strings) on the map. In version 108, the object names are stored within the campaign/mission file itself.Thank you @SpbGoro . Problem fixed for me. First Mike LKTO campaign converted with success. Many more to go.
EDIT: more data as I progress: doing this will lead to keeping the same objectives list (with some replacements on query). Some shouldn’t be there as they were, like Fukuoka for instance, that is replaced by Iwami.
After conversion, for Korea at least, you must have your 36 Te_New exported objectives file ready for import after deleting all the objectives on your newly converted file - and you must have a 35 occupation file ready for import to restore the owner. I suppose a little check on the map to make sure each country has its right stuff is necessary, obviously.
-
Ok, have been reading all you posts and am pretty shocked.
The things you are all doing is just amazing…Talking about exporting objective and re-importing them, using occupation file for conversion, copying Korea.wch and idx…
These things should NOT be done at all if you are simply converting a TE! Objectives are not even stored in a normal TE and the occupation is also not touched with the conversion.One thing to remember. All mission file that come with 4.36 have been converted with MC, else they would simply not be up to date with all the latest features.
Yes the latest available MC version is fully compatible with everything which is in 4.36. Even if I would release a new MC version, it probably won’t have anything new for 4.36 in it anyway.But to answer a couple of Qs.
-
What is the (XML)2.7sec in one of the example pic a few post back.
This is telling that the database have been loaded from XML and it took 2.7sec to load.
remember we had a binary database before
So would you care about this? no, not as a normal user. -
In the translate Objective table I can see Current (BMS 4.35)
Also this is just plain text coming from the stored translation tables. These are just simple text files which come with MC.
As a user you don’t care about this. -
So what should I do to convert a mission from 4.35 to 4.36?
Simply follow the 5 steps in the Convert tab. That is basically it.
All missions which come with 4.36 are converted like this.
New version, new start
-
If you have use the convert with previous versions of BMS, you have probably stored what “old” should be replaced with what “new” entity. To start fresh, resetting help the process.
Click on the buttons in “Reset Always replace with” this will delete all your previous stored saves and you start a fresh.
You can see the amount of stored replacements as a number inside the buttons. -
Plenty of people are talking about “error” messages.
Are you sure these are actually error messages? With the convert process, the user is asked questions which should be answered (seriously) With each message you get from MC, the tile of the message screen tell you what it is. This can be Information, Caution or something like that. During the conversion process its usually a Question. All these messages are giving the user information. Just read and you understand what you should do.
gr Falcas
-
-
@Falcas I get errors about things not matching
-
@Falcas said in Mission Commander beta release:
Ok, have been reading all you posts and am pretty shocked.
The things you are all doing is just amazing…Talking about exporting objective and re-importing them, using occupation file for conversion, copying Korea.wch and idx…
These things should NOT be done at all if you are simply converting a TE! Objectives are not even stored in a normal TE and the occupation is also not touched with the conversion.One thing to remember. All mission file that come with 4.36 have been converted with MC, else they would simply not be up to date with all the latest features.
Yes the latest available MC version is fully compatible with everything which is in 4.36. Even if I would release a new MC version, it probably won’t have anything new for 4.36 in it anyway.But to answer a couple of Qs.
-
What is the (XML)2.7sec in one of the example pic a few post back.
This is telling that the database have been loaded from XML and it took 2.7sec to load.
remember we had a binary database before
So would you care about this? no, not as a normal user. -
In the translate Objective table I can see Current (BMS 4.35)
Also this is just plain text coming from the stored translation tables. These are just simple text files which come with MC.
As a user you don’t care about this. -
So what should I do to convert a mission from 4.35 to 4.36?
Simply follow the 5 steps in the Convert tab. That is basically it.
All missions which come with 4.36 are converted like this.
New version, new start
-
If you have use the convert with previous versions of BMS, you have probably stored what “old” should be replaced with what “new” entity. To start fresh, resetting help the process.
Click on the buttons in “Reset Always replace with” this will delete all your previous stored saves and you start a fresh.
You can see the amount of stored replacements as a number inside the buttons. -
Plenty of people are talking about “error” messages.
Are you sure these are actually error messages? With the convert process, the user is asked questions which should be answered (seriously) With each message you get from MC, the tile of the message screen tell you what it is. This can be Information, Caution or something like that. During the conversion process its usually a Question. All these messages are giving the user information. Just read and you understand what you should do.
gr Falcas
I hope you’re recovering from this shock Falcas, I myself had one when I realized it wasn’t working, but time played its role.
By the way, we are (I am) not talking about converting a TE. But if this is still valid for converting saveX.cam, then let’s just agree on this: it works for you with January’s version, and it doesn’t work for us with January’s version just by following 5 steps. No drama here, I’m all good with that, we got resources and friends to find our way, fortunately none of us here is too close to the dumbness threshold, and I made my conversions with all the extra step I searched, got suggested and tested, not for fun but out of necessity - and the result is as satisfying as the path.
-