Mission Commander beta release
-
New version released.
Latest version 0.5.19.667Main
Little fix for ViewModel passing along the correct skin. In case the Units are not able to being loaded, the CampaignInfoTable is only cleaned when needed.
Map
Fix Map ruler showing wrong track. Fix for finding Name of the last Unit. Initial addition filter for HideExactLocation.
Objectives Chart creation
Parking/Ground chart ability to scale the chart. Apt and Nav Objectives within 5km are pulled into the chart as well. Option to switch on/off the ATC box. Marjor overhaul for the ground and parking charts 2 different charts can now be produced. AGC Airport Ground Chart and APC Airport Parking Chart (for each runway) Parking charts contain the coordinates for the parking points. Both charts now contain: Runway QFU and exact heading Runway dimensions Taxiway naming (if database has been set up correctly) Arrestor cable position Windsock Tacan location and frequency Tower and radar location List of ATC frequencies Airport elevation Added, button for creating airport chart on Objctive page. This is the same feature as right click on the map “Create Chart” Is just handy to have this one here as well. Only visible if the Objective is an Airbase or Airstrip. Added, Features like buildings, HAS and tower are drawn on the chart
Advanced Obj Options
Changed button Set First Obj Owner for more clarity
Units
Squadron View 3D Model, send correct Skin to ModelViewer. Added, Flight will show there respective assigned target in the Unit list. Flight View 3D Model, send correct Skin to ModelViewer. Skinset comes from Lead AC. For Wpt you can now select a Target Battalion as well as Objective.
-Changes for moving a squadron
The question for deleting the non-departed flights has been removed
The question for moving the takeoof and landing STPT to the new airbase has been removed.
Now the Flight will automatically move there takeoff and landing STPT to the new AB.
For Training flights, the complete list of STPTs are shifted the same amount as the old to new airbase. -
@falcas
Thank you very much -
Thanks a lot from me too for your hard work, dear Falcas.
Have a nice day!
With best regards.
-
hello falcas
I use mission commander intensely.
I have some suggestions to add in your next update :
-
on the lists (squadrons and such) when i click on a line, it painted in light grey and the letters are white. So the contrast is not so good which make reading the writing very hard.
Can the letters stay black to improve contrast ? -
Maybe it is my problem as my eyes are not what used to be . . . can the fonts of the app and its data be bigger, maybe an option to choose the fonts size can be implemented ?
-
On the map tab, can a ruler be implemented to find distance from point to point ?
I really appreciate if you can considerate my suggestions, (maybe some of them are big PITA to make, i have no programming experiance).
-
-
<p>Hey,<br /><br />1 and 2 are not so easy to change.<br /><br />3… a ruler has been implemented for many many years already</p>
-
<blockquote>Hey,<br /><br />1 and 2 are not so easy to change.<br /><br />3… a ruler has been implemented for many many years already</blockquote><p><br />Could you remind us in a couple words how it works? I gave up trying to use it proficiently. (the ruler) </p>
-
<p>“view 3D model” not work. it opens EDITOR.</p>
-
<p>@Gear5 Known bug. Fixed in next update</p>
-
4.36 conversion : “save 108”.
Current MC save version, max 103.Anything to worry about?
-
@LorikEolmin
Hhmmm… nice catch, dear Lorik.But it wouldn’t… this is just what happened the previous time MC has been upgraded to the new 4.34 (IIRC) standard, i.e. with adding the “103” to “100” and the previous one, I mean.
Let’s see what happens, however.
With best regards.
-
I’m trying to find a workaround to convert my mods to 36, but for the first time since 33, I can’t find anything.
I even tried to convert save0 from KTO35 to KTO36, it’s a huge streak of “Could not find objective name. Objective nr: XX. Nameid is larger than text table. Nameid: YY” that leads to app killing manually.
-
Good Day, Falcas.
Firstly, thanks for both MC and WDP, and the new WDP is up and running.
I wonder if you can help with a question about MC 5.19.667. I am doing some work in 4.36 in the Editor with squadron loadout and wpn hardpoints which MC doesn’t seem to “see”. Resupply does work in MC with the stock loadout values. I’m wondering if this could be because my database location is defaulting to TVT and not the regular KTO, where my campaign is.
My MC settings are:
File name-Falcon BMS 4.36\data\campaign\autosave.cam
Location- Falcon BMS 4.36
Database-Falcon BMS 4.36\data\Add on Korea TVT \Terrdata objects\objects\XML 2.8sec.
Also, when I start MC, I get the error message “Could not found:Falcon…Addon Korea TVT/campaign/save5.cam”
If the database location is incorrect, how do I change it to the regular KTO?
Thx -
Update: I just got Balkans installed, and everything works perfectly
-
Same problem as @LorikEolmin here, when I try to convert some simple TE missions from 4.35 .
Lots of “Could not find objective” popups, then a software exception and then seems to run forever until manually killed.I find this generated output path particularly suspicious:
-
I tried to roll back and try again. Fresh MC unpack, 4.36 as location, convert.
I try (for a test obviously, not for use purpose) to convert save0 from 35 to 36.
I give instructions to replace objectives, squadrons and the M109A2 unit, then I get an exception stopping the process.
Sorry, it’s in French…
************** Texte de l'exception ************** System.ArgumentException: Le chemin d'accès n'a pas une forme conforme. à System.IO.Path.LegacyNormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths) à System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths) à System.IO.Path.InternalGetDirectoryName(String path) à MissionCommander.fclsMain.PrevLoadTE() à MissionCommander.fclsMain.PrevOpenFile(String fName) à MissionCommander.fclsMain.PrevOpenFile() à MissionCommander.fclsMain.btnPrevLoadMission_Click(Object sender, EventArgs e) à System.Windows.Forms.Control.OnClick(EventArgs e) à System.Windows.Forms.Button.OnClick(EventArgs e) à System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) à System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) à System.Windows.Forms.Control.WndProc(Message& m) à System.Windows.Forms.ButtonBase.WndProc(Message& m) à System.Windows.Forms.Button.WndProc(Message& m) à System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) à System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) à System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Assemblys chargés ************** mscorlib Version de l'assembly : 4.0.0.0 Version Win32 : 4.8.4470.0 built by: NET48REL1LAST_C CodeBase : file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- Mission Commander Version de l'assembly : 0.5.19.667 Version Win32 : 0.5.19.667 CodeBase : file:///F:/Falcon%20BMS%204.36/Tools/Mission_Commander_0.5.19.667/Mission%20Commander.exe ---------------------------------------- Microsoft.VisualBasic Version de l'assembly : 10.0.0.0 Version Win32 : 14.8.4084.0 built by: NET48REL1 CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll ---------------------------------------- System Version de l'assembly : 4.0.0.0 Version Win32 : 4.8.4488.0 built by: NET48REL1LAST_C CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Core Version de l'assembly : 4.0.0.0 Version Win32 : 4.8.4470.0 built by: NET48REL1LAST_C CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Windows.Forms Version de l'assembly : 4.0.0.0 Version Win32 : 4.8.4488.0 built by: NET48REL1LAST_C CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Version de l'assembly : 4.0.0.0 Version Win32 : 4.8.4390.0 built by: NET48REL1LAST_C CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Configuration Version de l'assembly : 4.0.0.0 Version Win32 : 4.8.4190.0 built by: NET48REL1LAST_B CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Xml Version de l'assembly : 4.0.0.0 Version Win32 : 4.8.4084.0 built by: NET48REL1 CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Runtime.Remoting Version de l'assembly : 4.0.0.0 Version Win32 : 4.8.4084.0 built by: NET48REL1 CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll ---------------------------------------- BMSUtils Version de l'assembly : 1.6.3.45 Version Win32 : 1.6.3.45 CodeBase : file:///F:/Falcon%20BMS%204.36/Tools/Mission_Commander_0.5.19.667/BMSUtils.DLL ---------------------------------------- System.Windows.Forms.resources Version de l'assembly : 4.0.0.0 Version Win32 : 4.8.4084.0 built by: NET48REL1 CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_fr_b77a5c561934e089/System.Windows.Forms.resources.dll ---------------------------------------- dbwdp Version de l'assembly : 1.6.0.3 Version Win32 : 1.6.0.3 CodeBase : file:///F:/Falcon%20BMS%204.36/Tools/Mission_Commander_0.5.19.667/dbwdp.DLL ---------------------------------------- mscorlib.resources Version de l'assembly : 4.0.0.0 Version Win32 : 4.8.4084.0 built by: NET48REL1 CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_fr_b77a5c561934e089/mscorlib.resources.dll ---------------------------------------- BMSLocation Version de l'assembly : 1.0.4.0 Version Win32 : 1.0.4.0 CodeBase : file:///F:/Falcon%20BMS%204.36/Tools/Mission_Commander_0.5.19.667/BMSLocation.DLL ---------------------------------------- System.Web Version de l'assembly : 4.0.0.0 Version Win32 : 4.8.4494.0 built by: NET48REL1LAST_B CodeBase : file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dll ---------------------------------------- LzssManaged Version de l'assembly : 1.0.0.0 Version Win32 : 1.0.0.0 CodeBase : file:///F:/Falcon%20BMS%204.36/Tools/Mission_Commander_0.5.19.667/LzssManaged.DLL ---------------------------------------- LzssNative Version de l'assembly : 0.0.0.0 Version Win32 : CodeBase : file:///F:/Falcon%20BMS%204.36/Tools/Mission_Commander_0.5.19.667/LzssNative.DLL ---------------------------------------- ************** Débogage JIT ************** Pour activer le débogage juste-à-temps (JIT), le fichier de configuration pour cette application ou cet ordinateur (machine.config) doit avoir la valeur jitDebugging définie dans la section system.windows.forms. L'application doit également être compilée avec le débogage activé. Par exemple : <configuration> <system.windows.forms jitDebugging="true" /> </configuration> Lorsque le débogage juste-à-temps est activé, les exceptions non gérées seront envoyées au débogueur JIT inscrit sur l'ordinateur plutôt que d'être gérées par cette boîte de dialogue.
-
@Logic I experienced the same problem when using MC to convert BMS 4.34 missions to BMS 4.35.
(See the ugly history of that “dialogue” , if you wish, but it may not be enlightening…)
What this boils down to, per Falcas, is the presence of the proper “Conv*.txt” files in your MC/ Conv/Korea’ directory. Falcas quickly provided an update, and after that the “automatically replace” option worked smoothly.
However, as far as I can see, the very latest release of MC is 0.5.19.667, (which, although it dates to 25 Jan 2022), when installed and run once in the “Convert Mission” mode, seems to leave an empty “ConvTF.txt” file in the above Conv directory. (Well, empty except for its header line.)
When I attempt to use MC to convert a 4.35 mission, it produces an endless series of Caution dialogs (of “Could not find objective…” type).
The “TranslateObj.txt” file is dated 1/28/2021.
I could be completely off the mark (and I’ve been upbraided for that before), but I’m not convinced that Falcas has completed the updates needed to the conversion files…
Best I can see, a PM to [Falcas] is likely to get a very timely fix! He has always been incredibly responisve to problem reports on all of his splendid BMS tools!
-
@LorikEolmin seems to be an issue with a bad file path as well, so very likely the same as mine.
@Slothrop Of course I hope that @Falcas is subscribed to this thread and will end up being notified. -
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
-
@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 . . .