Mission Commander beta release
-
It doesn’t matter which slot any team is in to ally it or make it friendly with teams 2/6.
Like BB said 2 and 6 are set as Blue/Red, that will remain the same.
You can add any other slot to team 2 or 6, team 1 can be allied with team 6 if you like.
You can also link them to team 2 or 6 to be a part of said team on the Teams tab, link them together on the Relations tab, and they would function as a part of the team and also show on the 2D map at all times.
C9
-
I’ve got an issue with saving anything in MC
lets say I try to edit a flight - I get an unhandled exception error that says "Conversion from string “” to type ‘Integer’ is not valid
i am using the latest version of MC(0.5.8.384) and have .NET 4.0 and MS Visual C++ 2010
Error log:See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.InvalidCastException: Conversion from string "" to type 'Integer' is not valid. ---> System.FormatException: Input string was not in a correct format. at Microsoft.VisualBasic.CompilerServices.Conversions.ParseDouble(String Value, NumberFormatInfo NumberFormat) at Microsoft.VisualBasic.CompilerServices.Conversions.ToInteger(String Value) --- End of inner exception stack trace --- at Microsoft.VisualBasic.CompilerServices.Conversions.ToInteger(String Value) at MissionCommander.fclsFlight.ApplyFlight() at MissionCommander.fclsFlight.btnApply_Click(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- Mission Commander Assembly Version: 0.5.8.384 Win32 Version: 0.5.8.384 CodeBase: file:///C:/Games/Falcon%20BMS%204.33%20U1/Programs/MissionCommander/Mission%20Commander.exe ---------------------------------------- Microsoft.VisualBasic Assembly Version: 10.0.0.0 Win32 Version: 14.7.3190.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.7.3353.0 built by: NET472REL1LAST_B CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_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 Assembly Version: 4.0.0.0 Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_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 Assembly Version: 4.0.0.0 Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.7.3324.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Runtime.Remoting Assembly Version: 4.0.0.0 Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll ---------------------------------------- BMSUtils Assembly Version: 1.6.1.17 Win32 Version: 1.6.1.17 CodeBase: file:///C:/Games/Falcon%20BMS%204.33%20U1/Programs/MissionCommander/BMSUtils.DLL ---------------------------------------- dbwdp Assembly Version: 1.6.0.0 Win32 Version: 1.6.0.0 CodeBase: file:///C:/Games/Falcon%20BMS%204.33%20U1/Programs/MissionCommander/dbwdp.DLL ---------------------------------------- BMSLocation Assembly Version: 1.0.3.0 Win32 Version: 1.0.3.0 CodeBase: file:///C:/Games/Falcon%20BMS%204.33%20U1/Programs/MissionCommander/BMSLocation.DLL ---------------------------------------- System.Web Assembly Version: 4.0.0.0 Win32 Version: 4.7.3282.0 built by: NET472REL1LAST_B CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dll ---------------------------------------- LzssManaged Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Games/Falcon%20BMS%204.33%20U1/Programs/MissionCommander/LzssManaged.DLL ---------------------------------------- Accessibility Assembly Version: 4.0.0.0 Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration></configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.
How do i fix this?
-
I’ve got an issue with saving anything in MC
lets say I try to edit a flight - I get an unhandled exception error that says "Conversion from string “” to type ‘Integer’ is not valid
i am using the latest version of MC(0.5.8.384) and have .NET 4.0 and MS Visual C++ 2010How do i fix this?
Exact same error here since a few versions of MC. I found that the changes are still applied though.
What I do is:
- Click Apply
- Get the error
- Close the error screen
- Close the Flight editing window
- Save the file
- Reload the file
- Check and see that change has been applied
-
new version released, latest is 0.5.9.394
Enjoy,
Falcas
-
-
ROFLMAO :rofl:… Thanks
-
Just as a little note…
Lots of things are included through out the years which you where not able to see because of a missing 4.34 install.
Now that you have it, you might find little extras all over MC.Gr Falcas
-
Dear Sir
I am having problems converting a or any TE from 4.33 to 4.34,
I have the current version MC_0.5.9.394, It resides on a fresh Win10 install.
It throws An Exception “System.DllNotFoundException: Unable to load DLL ‘LzssNative.dll’: The specified module could not be found. (Exception from HRESULT: 0x8007007E)” and just spins its wheels.
Same with any TE (New or old)
BMS install paths : D:\Falcon BMS 4.33 U5 & D:\Falcon BMS 4.34
'LzssNative.dl" is in the install.
-
Dear Falcas,
after I installed MC last version released, unfortunately I too am experiencing troubles in converting 4.33 TEs to 4.34: after converted all the items, thus virtually ended the procedure, the ‘Save’ and ‘Save As’ buttons remain greyed both.
What have I done wrong or missed, I wonder.Thanks a lot in advance! With best regards.
-
Edited: Solved issue
-
Dear Falcas,
after I installed MC last version released, unfortunately I too am experiencing troubles in converting 4.33 TEs to 4.34: after converted all the items, thus virtually ended the procedure, the ‘Save’ and ‘Save As’ buttons remain greyed both.
What have I done wrong or missed, I wonder.Thanks a lot in advance! With best regards.
Also, same thing here… What I think is that ‘Theatre Converter’ is for converting .cam/.tac only from 4.32 to 4.33 version., not for new stuff.
I get exception on the end of the process., and whole process converting from 4.33 Custom database to 4.34 is a bust., still figuring where is the catch, I’ll try to reproduce.
Maybe try manually … convert whole theater to 4.34., new dir structure etc…
Is there some manual for converting theatres from 4.33 ??? Much appreciate …
-
MC is fine with 4.34 as well as converting any version of Falcon to 4.34.
This is what has been used by the team to do all needed things for the mission files.MC will only convert the missions, so cam, tac and trn files.
The process will only work if the user follows the steps correctly.
When the process has been concluded the mission the save prompt will pop up automatically.
The location will also be in the 4.34 directory. Other needed files are automatically copied over as well.Only the fmap weather file is the exception. This files needs to be opened and saved with WeatherCommander.
This will update the file to the correct format. (Ver 1.3.0.11)But follow the each and every step correctly and read what the steps are.
And answer each question you get as good as you can.Gr Falcas
-
Thanks for all yours above, Falcas.
Please let me clarify that I believe you have released this last version, in particular, only after it past severe testings, so my question was intended to understand what I did wrong or imprecise.
Besides, no matter about your great will to help us, the users, in passing by also all the sometimes silly errors we happen to do.
The weird thing remains that I just couldn’t finish the procedure as it’s due, by evidence. Every my attempt was frustrated at the end of the process I’m describing as follows:- set the same theater (KTO, in my case) for both the BMS versions;
- located the previous BMS version (BMS 4.33.1 update 5);
- selected its proper executable (‘launcher.exe’);
- checked that the output data were correct (Falcon location, etc., even if already set by default, as we learned);
- loaded the TE only (a .tac file, I mean) from the BMS previous version Campaign/Save folder;
- started the converting process;
- allowed any conversion to the new ‘format’ of any object et al. highlighted and needed during this;
- last, here it comes the tricky passage: forced the utility to continue, trespassing an error warning about the following exception (I couldn’t translate it, sorry. Hope it’s understandable the same.)
************* Testo dell’eccezione **************
System.IndexOutOfRangeException: Indice oltre i limiti della matrice.
in MissionCommander.fclsMain.PrevDoTaskForce()
in MissionCommander.fclsMain.PrevLoadTE()
in MissionCommander.fclsMain.PrevOpenFile(String fName)
in MissionCommander.fclsMain.PrevOpenFile()
in MissionCommander.fclsMain.btnPrevLoadMission_Click(Object sender, EventArgs e)
in System.Windows.Forms.Control.OnClick(EventArgs e)
in System.Windows.Forms.Button.OnClick(EventArgs e)
in System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
in System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
in System.Windows.Forms.Control.WndProc(Message& m)
in System.Windows.Forms.ButtonBase.WndProc(Message& m)
in System.Windows.Forms.Button.WndProc(Message& m)
in System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
in System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
in System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)************** Assembly caricati **************
mscorlib
Versione assembly: 4.0.0.0
Versione Win32: 4.7.3362.0 built by: NET472REL1LAST_C
Base di codice: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
–--------------------------------------
Mission Commander
Versione assembly: 0.5.9.394
Versione Win32: 0.5.9.394
Base di codice: file:///C:/Program%20Files/Mission%20Commander/Mission%20Commander.exeMicrosoft.VisualBasic
Versione assembly: 10.0.0.0
Versione Win32: 14.7.3190.0 built by: NET472REL1LAST_C
Base di codice: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dllSystem
Versione assembly: 4.0.0.0
Versione Win32: 4.7.3362.0 built by: NET472REL1LAST_C
Base di codice: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dllSystem.Core
Versione assembly: 4.0.0.0
Versione Win32: 4.7.3362.0 built by: NET472REL1LAST_C
Base di codice: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dllSystem.Windows.Forms
Versione assembly: 4.0.0.0
Versione Win32: 4.7.3324.0 built by: NET472REL1LAST_C
Base di codice: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dllSystem.Drawing
Versione assembly: 4.0.0.0
Versione Win32: 4.7.3190.0 built by: NET472REL1LAST_C
Base di codice: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dllSystem.Configuration
Versione assembly: 4.0.0.0
Versione Win32: 4.7.3324.0 built by: NET472REL1LAST_C
Base di codice: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dllSystem.Xml
Versione assembly: 4.0.0.0
Versione Win32: 4.7.3190.0 built by: NET472REL1LAST_C
Base di codice: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dllSystem.Runtime.Remoting
Versione assembly: 4.0.0.0
Versione Win32: 4.7.3190.0 built by: NET472REL1LAST_C
Base di codice: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dllBMSUtils
Versione assembly: 1.6.1.17
Versione Win32: 1.6.1.17
Base di codice: file:///C:/Program%20Files/Mission%20Commander/BMSUtils.DLLSystem.Windows.Forms.resources
Versione assembly: 4.0.0.0
Versione Win32: 4.7.3190.0 built by: NET472REL1LAST_C
Base di codice: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_it_b77a5c561934e089/System.Windows.Forms.resources.dlldbwdp
Versione assembly: 1.6.0.0
Versione Win32: 1.6.0.0
Base di codice: file:///C:/Program%20Files/Mission%20Commander/dbwdp.DLLmscorlib.resources
Versione assembly: 4.0.0.0
Versione Win32: 4.7.3190.0 built by: NET472REL1LAST_C
Base di codice: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_it_b77a5c561934e089/mscorlib.resources.dllBMSLocation
Versione assembly: 1.0.3.0
Versione Win32: 1.0.3.0
Base di codice: file:///C:/Program%20Files/Mission%20Commander/BMSLocation.DLLSystem.Web
Versione assembly: 4.0.0.0
Versione Win32: 4.7.3282.0 built by: NET472REL1LAST_B
Base di codice: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dllLzssManaged
Versione assembly: 1.0.0.0
Versione Win32: 1.0.0.0
Base di codice: file:///C:/Program%20Files/Mission%20Commander/LzssManaged.DLLWhat did I wrong? And how to solve that? Sorry for bothering you again, and my apologies for a so long post, hope it will be worth to.
Thanks in advance, with best regards.
-
Sorry for bothering you again, and my apologies for a so long post, hope it will be worth to.
Just a general remark for everybody.
you are NOT bothering, this is what the forum is for!!!
I’ll do my best to help out (am on my mobile phone right now).
However, try to help yourself by giving me clear questions.My answer in the previous post could only be general as the questions (statements) before that where only general.
For example… help it does not work?.. what should I answer to this as it does not contain information@Jackal, this post is not directed to you personal.
The info you posted is fine and I’ll answer as soon as possible.Gr Falcas
-
Thanks for all yours above, Falcas.
Please let me clarify that I believe you have released this last version, in particular, only after it past severe testings, so my question was intended to understand what I did wrong or imprecise.
Besides, no matter about your great will to help us, the users, in passing by also all the sometimes silly errors we happen to do.
The weird thing remains that I just couldn’t finish the procedure as it’s due, by evidence. Every my attempt was frustrated at the end of the process I’m describing as follows:- set the same theater (KTO, in my case) for both the BMS versions;
- located the previous BMS version (BMS 4.33.1 update 5);
- selected its proper executable (‘launcher.exe’);
- checked that the output data were correct (Falcon location, etc., even if already set by default, as we learned);
- loaded the TE only (a .tac file, I mean) from the BMS previous version Campaign/Save folder;
- started the converting process;
- allowed any conversion to the new ‘format’ of any object et al. highlighted and needed during this;
- last, here it comes the tricky passage: forced the utility to continue, trespassing an error warning about the following exception (I couldn’t translate it, sorry. Hope it’s understandable the same.)
Basically you for what you write you did it all fine. Although I don’t see you write step 2, which is actually important.
But I guess you did anyway as you write: “checked that the output data were correct (Falcon location, etc., even if already set by default, as we learned)”
Note: I just see that the text of step 1 and 2 is only partially visible. Fixed already.From the crash report you can clearly see its a crash during the conversion of the taskforces.
Not much you can do right now as this needs a check in the code and the mission itself.
So if you could get me the file, I can take a look.Gr Falcas
-
Dear Falcas,
I meant to tell that all the output data were just what they should are as set per ‘Falcon BMS Location’ item.
And thanks a lot for your kind proposal, so I’m going to learn some more about how to make out a TE properly.
Is you could PM me an email address of yours, I’ll send that TE right away.With best regards.
-
Dear Sir
I am having problems converting a or any TE from 4.33 to 4.34,
I have the current version MC_0.5.9.394, It resides on a fresh Win10 install.
……
…
BMS install paths : D:\Falcon BMS 4.33 U5 & D:\Falcon BMS 4.34'LzssNative.dl" is in the install.
My Bad, the Install of 4.33 U5 on D:\ belonged to an Old Win7 install on another drive.
Thanks……
-
I have been trying to use some offmap units in a TE that I have added with the Mission Commander. I am using the same settings as it is used for cam files.
BMS is however not recognising my offmap squads. What I am doing wrong? In campaigns it is working nicely……
Sometimes it chrashes, sometimes it says it is not possible to generate flight plan when I try to add a flight from the offmap squad.Does anyone have any clue what I am doing wrong?
PS: more specifically, in TE it says “No path to target found,-> No AB Available.”
In the campaign I have been editing and flying, it works very nice. -
Yep, Offmap airbases is only for Campaigns at this moment.
But with BMS you never know what the future bringsGr Falcas
-
Good to know. I was wondering if was doing something wrong.
Anyway, offmap AB are really cool in campaigns. Offer tons of new possibilities and scenarios. Cheers!