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.
-
@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 -
@Falcas Transmitting.
EDIT: yeah transmitting and I cannot check right now, but it rings a serious bell, I wouldn’t be surprised to see TvT first line when I get home.
EDIT2: for me at least, it’s not above KTO.
-
Check what you are doing… you are NOT following the steps correctly.
At the top of MC you can see MC is pointing to the KTO database.
You are trying to convert a mission from 4.35 which has Balkans as active theater. See step 3. This is where you can also see the output is going to 4.36 KTO…No wonder you are getting issues.
Steps need to be followed exactly else it doesn’t work
-
Could you do a dummy check on my procedure as well, if you see something fishy:
The exception I get is shown as well.
The TE file being used is here:
https://drive.google.com/file/d/12P-RhCFw0HYDwU9xqXw6PXEOuDQPQWQI/view?usp=sharing -
@Logic try putting the file you want to convert in the same folder. I had to copy a TE I have been trying to convert from it’s orginal folder into the 4.36 install location before it worked for me. Trying to go from the 4.35 install location to the 4.36 install location gave me the issues you are having.
-
Well no…
Leave 35 files in 35 installation and when the conversion is over, point to the right 36 folder …
The conversion for my theaters was straight forward. The only problem was doing the changes in database to match 4.36 changes (but that’s more for theater creators to worry about it)
-
Would someone who has had success at an MC conversion of 4.35 to 4.36 .tac files be kind enough to share with me the resulting contents of your “MC/Conv/Korea” directory?
I’ve tried everything in this thread, and still no joy…
I just get a succession of these error dialogs, then the dreaded Exception:
Thanks much, Sloth
-
The problem I am having MC always opens with TVT set as the theater. The theater.lst is always listing the TVT theater first. I am referring to the theater.lst file in the Falcon BMS 4.36\Data\TerrData\TheaterDefinition location.
When I change it to list Korea KTO.tdf first MC opens correctly with the correct theater, but even if I make the file read only once I run BMS and close it and then open MC the TVT theater loads and the theater.lst file has the TVT theater listed first again. I have KTO set in BMS.
-
@Slothrop exactly my experience too. Same messages, same crash
-
@Slothrop @jayb @Falcas
I am seeing the exact same error as both of you. I have ensured that KTO is the active theater in both 4.35U3 installation and 4.36 installation. 4.36 is properly pointed to in MC (see screenshot below). The proper old version is being accessed (4.35U3 Launcher.exe). A simple TE was the selected old file “TE_BMS_TC2_1_ILS Practice.tac”. I saw 6 "Caution Boxes, each advising that "Objective 0 (or 1 or 2 or 3 or 4 or 5) " Could not find Objective Name. NameID is larger than text table. The NameIDs listed in those Caution Boxes are repeatable on every failure (See example above in Slothrop’s screenshot). Then I get the Unhandled Exception Error - “System.IndexOutOfRangeException: Index was outside the bounds of the Array.” I have tried straight conversions of various TEs I made from KTO 4.35U3 to KTO 4.36 with and without copying the 4.35U3 Korea.idx and Korea.wch files into 4.36 …data\campaign\ folder. Every result is the same - unhandled exception error, IndexOutOfRange.I also tried switching Theaters on both 4.35U3 and 4.36 to Balkans and tried to convert another very simple TE. Same result (one popup Objective Select box was different from what I saw in KTO attempts - it said that Pula Airbase was not a land object and asked if I wanted to reselect the object). In any event, the conversion failed with a “System.IndexOutOfRangeException.” - same error as when I attempted KTO conversions.
TLDR: Conversions are not working for me from 4.35U3 TEs to 4.36. I never get to the “Save As” popup.
If anyone cracks the case on this one, sure would be appreciated.
Regards,
Tomcattwo
(VoiceClone) -
@Tomcattwo Speak it, brother!
-
Here’s what worked for me, 4.36.0 and 4.35.3, MC 0.5.19.667
Each step has a reason to be.
CAM = campaign file (saveX.cam). Maybe TE too, didn’t try.
In BMS 4.35, set theater as required (only tried KTO and LKTO)
In BMS 4.36, set theater as required
copy korea.wch and korea.idx from 4.35 campaign folder to 4.36 campaign folder. They don’t replace anything (Thank you SpbGoro)Open MC
Open Te_New in 4.36 (required theater)
in Objectives - Advanced, export Objectives CSV to file
Set BMS location to 4.35
close MC (I think it’s safer)
This Te_New objectives list should be useful for all the campaigns or TE of the theater.open MC
open 4.35 CAM
in Objectives - Advanced: export Team occupation to file
in Units - Advanced - export all units to file
set BMS location to 4.36
close MCOpen MC
Convert tabs, set earlier version to 4.35
Open CAM
Prompts will appear. For KTO Fukuoka Admn, choose !DMS something 25. For the rest, it should be easy. Osan something is hidden in the Depot section.
Give required save name for CAM
Open created 4.36 CAM
In Objectives, delete all objectives
Import Objective CSV for Campaign
Use 4.36 Te_New Objectives CSV file and 4.35 CAM Team occupation file
In Units - Advanced, import all units using 4.35 CAM units file
In Map, use Filter and check for every colour that there isn’t forgotten (newly added in 4.36) objectives on the wrong sides.
Set wrong side manually for each objective (draw boxes to make it faster)Save your file without ticking any 73-100-103 box BUT BEFORE, you should always: Units - Advanced - Rebuild Squadron Info (for general MC use actually).
EDIT: for TE: workaround in https://forum.falcon-bms.com/post/342794
-
@LorikEolmin Great guide Lorik, thank you for typing it up
-
@LorikEolmin Didn’t work for me. (with a TE)
Did it for you, @jayb ?
Still same exception.