Mission Commander beta release
-
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.
-
-
@Falcas said in Mission Commander beta release:
That is not an error
Hell no! That is a post of mine!
-
That is NOT an error message
-
Yeah, the way this forum works is a pain in the…
-
@Falcas said in Mission Commander beta release:
That is NOT an error message
The problem of our friend, in case you imply it shouldn’t be the cause of any worry, is that this window is actually just a sample. You have hundreds (thousands??) other coming with different numbers and the same face. Application killing is the key for serenity of mind. Not really for conversion though. That’s where moving korea.files fixed it for me.
-
Its all about how much information I can read from posts.
When you are talking about a saveX.cam file, sure a slightly different matter. But the same answer applies. Do NOT use import/export when converting a saveX file. It makes no sense.Btw, the saveX files for 4.36 are already converted, you don’t need to do this… Oh wait… I have to guess you are not talking about KTO
-
@Falcas said in Mission Commander beta release:
Its all about how much information I can read from posts.
When you are talking about a saveX.cam file, sure a slightly different matter. But the same answer applies. Do NOT use import/export when converting a saveX file. It makes no sense.Btw, the saveX files for 4.36 are already converted, you don’t need to do this… Oh wait… I have to guess you are not talking about KTO
Not about KTO. As for my computer, all I can tell you is, you’re talking now to an expert at converting. For my computer, once again. How lucky you are to have yours
EDIT: and yes, actually, about KTO too, just to make sure I had the same troubles. I had.
-
@Falcas at a point i get an option of continuing or quitting. I can never get to a save as selection while trying to convert.
-
If you get these messages so much… well than you should really look at the mission itself before you start converting. And/or the 4.35 install the mission is belonging to.
One of the simple mistakes I hear about, is that mission files get copied over from 4.35 to 4.36 and then a convert is being tried.
Do NOT do this!!! Keep your 4.35 missions in your 4.35 install.Yeah I understand it might be frustrating if you run into something like this. However, there is not much I can tell you what to do as these kind of messages don’t pop up for me when I do a conversion.
-
@Falcas said in Mission Commander beta release:
If you get these messages so much… well than you should really look at the mission itself before you start converting. And/or the 4.35 install the mission is belonging to.
One of the simple mistakes I hear about, is that mission files get copied over from 4.35 to 4.36 and then a convert is being tried.
Do NOT do this!!! Keep your 4.35 missions in your 4.35 install.Yeah I understand it might be frustrating if you run into something like this. However, there is not much I can tell you what to do as these kind of messages don’t pop up for me when I do a conversion.
Lucky you are. For me, I moved the idx and the wch file, and it works now like a charm. I would have been stupid not to.
-
@LorikEolmin
I would be the last person to say it stupid… if it works, it can’t be (that) stupidPutting those files into the 4.36 install should really not matter.
But at least it will give me an idea to check some part of the code.
Stby… -
@Falcas said in Mission Commander beta release:
@LorikEolmin
I would be the last person to say it stupid… if it works, it can’t be (that) stupidPutting those files into the 4.36 install should really not matter.
But at least it will give me an idea to check some part of the code.
Stby…Very glad if I help. Also, because I can swear it’s in the air… we do have the same version of MC, 100%, right? January, 667?
I could make a video of what happens when I convert the academic way (the non-working), if I got time this week-end.
-
@LorikEolmin Currently checking the WDP S-J save. Someone asked about that
-
@Falcas said in Mission Commander beta release:
@LorikEolmin Currently checking the WDP S-J save. Someone asked about that
And I know we both love this person :D.
And just a little clue coming from someone else’s brains: wouldn’t MC default to TvT database? And removing TvT would then have an effect? Because, guess what…
EDIT: this is not about converting, more general use with saves.
-
@LorikEolmin
MC defaults to what you have used the last time.
What you can do is check your theate.lst file.
Internally this file got a bit messed up and KTO got kicked from the first line. TvT should always below the normal KTO.
This was already fixed internally, but I have no clue what the status is in the released 4.36 version