Mission Commander beta release
-
The Editor should not open, only the Model Viewer should open directly.
At least that is how it works here. -
@falcas said in Mission Commander beta release:
The Editor should not open, only the Model Viewer should open directly.
At least that is how it works here.@Falcas thanks for the reply. Before I installed 4.35 Update 3, what you said is what used to happen. Since installing Update 3 today, Model Viewer no longer opens directly; instead, Editor opens. I am letting you know in case something in U3 has caused this behavior in Mission Commander.
Regards,
TC2 -
Hi Falcas, long time no hear, hope everything is ok as much as can be in these times.
So, I can confirm strange behavior of model viewer, opening falcon editor instead… probably changed switch in editor for U3… but that’s internal.
But more sophisticated problem found in brigade window, cannot change type , it always defaults to armored (brigade type) whatever you select as if defaults to first type on the list (pull down).
Maybe you could take a look as time allows.Thanks.
Cheers -
@tomcattwo
I have the same behavior as what you observed. I tried a fresh installation of BMS U3 but it did solve the problem. I can’ t tell you from which update version the issue raised up. -
Hi again.
Don’t know if v105-106 naming scheme options are in experimental phase, i guess so, but they don’t work - and that’s very probably as my file is v103 …
Anyway, I’ve tried those options to fix some my save2 nowhere names but yeah… nogo. Nothing happens as far i could see.Another story (hmmm, problem) is "automatic naming " of nowhere’s with name from parent objective, when import objective csv.
I’ve rather kept my exported csv “nowheres” as they are but!,- when importing the csv , most of NoWhere objectives , like bridges , get the parent name, - so alot nowhere bridges now have the name of the parent objective
!Most of… NOT all. … still trying to figure why there are few exceptions, they stay nowhere even after import.
So far it seems the parent level (parent- sub parent - … ) but still unsure.So, can be automatic naming from parent can be disabled? , or it is a bug///
Cheers
-
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.