Mission Commander beta release
-
Well… so I’d try to do ‘the talk’ straight, then.
Dear Falcas, to you who are well known and appreciated in this Community in years for your special kindness:
would you kindly evaluate to spare a little of your valuable time and start writing some lines about ‘how to’ learn and use your useful utilities both?
Even more than someone here, far better skilled than I sure am, could contribute as well about, as you can see.With best compliments for all and my best regards.
Hey Jackal,
Kind words are noted
But writing a manual is really not something I am going to do. Which has been mentioned many times already.
Development of all the tools and BMS itself is taking a lot (yeah a lot) of time. So people wonder if I have a RL job… yes I do
Asking specific questions can be done here on the forum and if anybody wants to write something… its a free world
Lorik has already posted a first part. (sorry didn’t even have time to take a look at that).Most of the questions have been covered many times on the forum already. Usually in this thread.
But TBH… just start using the tool and don’t be afraid to click on something. Keep a backup of your files is also just a basic and a must!
The above mentioned clicking on the features to set them damaged/destroyed really wonders me. This is really the basics of using any tool.
All other parts of MC work exactly the same.Gr Falcas
-
Good evening, Falcas.
I see your point of view, and your kind advises are appreciated, so I will follow them.
Thanks for your (usual) great attention and reply.
With best regards.
-
Hello Everyone ! I’m looking for some help.
I am trying to get Mission Commander and WDP to work.
I always get the error about the LzssNative.dll (specified module could not be found).Here is what I have tried so far :
- Install .net 4.0 like specified in the initial post
- Install vcc like specified in the initial post
- Install the latest .net (4.8 )
- Start the software in admin mode
No matter what I do, I get that error, and I cannot load missions in either WDP or MC.
The system :
- i9 9980HK
- 2GB ram (it’s a VM)
- Windows 7 64bit
- Windows 7 SP1
Here are the details of the error :
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.DllNotFoundException: Unable to load DLL 'LzssNative.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E) at Lzss.NativeMethods.LZSS_Expand(IntPtr compressedDataBuffer, IntPtr decompressedDataBuffer, Int32 decompressedDataSize) at Lzss.Codec.Decompress(Byte[] compressedDataBuffer, Int32 compressedDataBufferStartingOffset, Byte[] decompressedDataBuffer, Int32 decompressedDataStartingOffset, Int32 decompressedDataLength) at Lzss.Codec.Decompress(Byte[] toDecompress, Int32 uncompressedDataSize) at MissionCommander.fclsMain.SortFiles() at MissionCommander.fclsMain.LoadTE() at MissionCommander.fclsMain.OpenFile(String fName) at MissionCommander.fclsMain.OpenFile() at MissionCommander.fclsMain.mnuOpenMission_Click(Object sender, EventArgs e) at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e) at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e) at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met) at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met) at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea) at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.ToolStrip.WndProc(Message& m) at System.Windows.Forms.ToolStripDropDown.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.8.3928.0 built by: NET48REL1 CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- Mission Commander Assembly Version: 0.5.13.522 Win32 Version: 0.5.13.522 CodeBase: file:///C:/Falcon%20BMS%20Tools/Mission%20Commander/Mission%20Commander.exe ---------------------------------------- Microsoft.VisualBasic Assembly Version: 10.0.0.0 Win32 Version: 14.8.3761.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 Assembly Version: 4.0.0.0 Win32 Version: 4.8.3928.0 built by: NET48REL1 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.8.3928.0 built by: NET48REL1 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.8.3928.0 built by: NET48REL1 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.8.3761.0 built by: NET48REL1 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.8.3761.0 built by: NET48REL1 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.8.3761.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 Assembly Version: 4.0.0.0 Win32 Version: 4.8.3761.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 Assembly Version: 1.6.2.29 Win32 Version: 1.6.2.29 CodeBase: file:///C:/Falcon%20BMS%20Tools/Mission%20Commander/BMSUtils.DLL ---------------------------------------- dbwdp Assembly Version: 1.6.0.0 Win32 Version: 1.6.0.0 CodeBase: file:///C:/Falcon%20BMS%20Tools/Mission%20Commander/dbwdp.DLL ---------------------------------------- BMSLocation Assembly Version: 1.0.4.0 Win32 Version: 1.0.4.0 CodeBase: file:///C:/Falcon%20BMS%20Tools/Mission%20Commander/BMSLocation.DLL ---------------------------------------- System.Web Assembly Version: 4.0.0.0 Win32 Version: 4.8.3928.0 built by: NET48REL1 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:/Falcon%20BMS%20Tools/Mission%20Commander/LzssManaged.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.
If anybody has an idea, I’m listening
The error :
What is installed right now :
-
Nobody ?
I tried copying the concerned DLL from other sources with no success -
Hi Flow32
I had the same problem with WDP some time ago, but never with MC. I tried to copy the LzssNative.dll from MC to WDP and that worked for me. But since you have issues with both programs, that would not be the solution I guess.
Hope you find a fix to the problem
-
@NIL:
Hi Flow32
I had the same problem with WDP some time ago, but never with MC. I tried to copy the LzssNative.dll from MC to WDP and that worked for me. But since you have issues with both programs, that would not be the solution I guess.
Hope you find a fix to the problem
Yes I remembered the same from the installation on my sim computer, and it does work on that one perfectly.
But on my laptop, no luck with that technique
I’m really unsure on why though…
I’ll update here if I ever find the solution. If anybody has a clue, I would love to hear it -
I have tried everything
Multiple .net versions etc… to no avail
None of the MC / WDP / WC work on my computer.Edit : of course first try was with .net 4.0 as specified in the initial post.
-
I have tried everything
Multiple .net versions etc… to no avail
None of the MC / WDP / WC work on my computer.Edit : of course first try was with .net 4.0 as specified in the initial post.
https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
-
Is there a way to change AI skills (Recruit/Ace) with MC or any other tools?
-
Hi guys, I’m trying to run mission commander in wine 5.0.x (development release) so I can do my TE design & editing on Linux. It used to work fine before, but with the latest release downloaded fresh off Falcas’ excellent website I keep getting these error popups when trying to run MC:
Any idea what could be causing this? Might it be an easy fix within MC or within WINE? I’m emulating win7 I think, BMS 4.34 runs fine (at least the 2d part, don’t get your hopes up :))
When trying to load a TE in EMF, I’m getting a different error (the one above is from stock KTO):
See the end of this message for details on invoking \njust-in-time (JIT) debugging instead of this dialog box.\n\n************** Exception Text **************\nSystem.InvalidCastException: Conversion from string "499.7" to type 'Integer' is not valid. ---> System.FormatException: Input string was not in a correct format. at System.Number.ThrowOverflowOrFormatException (System.Boolean overflow, System.String overflowResourceKey) [0x0001a] in <7713cb95b33244ed9608bf0b23fbdce9>:0 at System.Number.ParseInt32 (System.ReadOnlySpan`1[t] value, System.Globalization.NumberStyles styles, System.Globalization.NumberFormatInfo info) [0x00016] in <7713cb95b33244ed9608bf0b23fbdce9>:0 at System.Int32.Parse (System.String s) [0x00016] in <7713cb95b33244ed9608bf0b23fbdce9>:0 at Microsoft.VisualBasic.CompilerServices.IntegerType.FromString (System.String Value) [0x00018] in <12e3548e97434496b06dcdc0d13d1497>:0 --- End of inner exception stack trace --- at Microsoft.VisualBasic.CompilerServices.IntegerType.FromString (System.String Value) [0x00055] in <12e3548e97434496b06dcdc0d13d1497>:0 at Microsoft.VisualBasic.CompilerServices.Conversions.ToInteger (System.String Value) [0x00001] in <12e3548e97434496b06dcdc0d13d1497>:0 at MissionCommander.fclsMain.SetPosLabels () [0x00040] in <733da305f0cc45799078c07b4b0391e8>:0 at (wrapper remoting-invoke-with-check) MissionCommander.fclsMain.SetPosLabels() at MissionCommander.cntImageControl.DrawingBoard1_MouseMove (System.Object sender, System.Windows.Forms.MouseEventArgs e) [0x00189] in <733da305f0cc45799078c07b4b0391e8>:0 at (wrapper delegate-invoke) <module>.invoke_void_object_MouseEventArgs(object,System.Windows.Forms.MouseEventArgs) at System.Windows.Forms.Control.OnMouseMove (System.Windows.Forms.MouseEventArgs e) [0x0001f] in <a1b7540aeb454df7a6cc546c7c9a66bb>:0 at System.Windows.Forms.Control.WmMouseMove (System.Windows.Forms.Message& m) [0x00040] in <a1b7540aeb454df7a6cc546c7c9a66bb>:0 at System.Windows.Forms.Control.WndProc (System.Windows.Forms.Message& m) [0x006c8] in <a1b7540aeb454df7a6cc546c7c9a66bb>:0 at System.Windows.Forms.ScrollableControl.WndProc (System.Windows.Forms.Message& m) [0x00043] in <a1b7540aeb454df7a6cc546c7c9a66bb>:0 at System.Windows.Forms.ContainerControl.WndProc (System.Windows.Forms.Message& m) [0x0001a] in <a1b7540aeb454df7a6cc546c7c9a66bb>:0 at System.Windows.Forms.UserControl.WndProc (System.Windows.Forms.Message& m) [0x0001a] in <a1b7540aeb454df7a6cc546c7c9a66bb>:0 at System.Windows.Forms.Control+ControlNativeWindow.OnMessage (System.Windows.Forms.Message& m) [0x00001] in <a1b7540aeb454df7a6cc546c7c9a66bb>:0 at System.Windows.Forms.Control+ControlNativeWindow.WndProc (System.Windows.Forms.Message& m) [0x000b3] in <a1b7540aeb454df7a6cc546c7c9a66bb>:0 at System.Windows.Forms.NativeWindow.Callback (System.IntPtr hWnd, System.Int32 msg, System.IntPtr wparam, System.IntPtr lparam) [0x00030] in <a1b7540aeb454df7a6cc546c7c9a66bb>:0 \n************** Loaded Assemblies **************\nmscorlib\n Assembly Version: 4.0.0.0\n Win32 Version: 4.6.57.0\n CodeBase: file:///C:/windows/mono/mono-2.0/lib/mono/4.5/mscorlib.dll\n----------------------------------------\nMission Commander\n Assembly Version: 0.5.13.522\n Win32 Version: 0.5.13.522\n CodeBase: file:///C:/mission_commander/Mission%20Commander.exe\n----------------------------------------\nMicrosoft.VisualBasic\n Assembly Version: 10.0.0.0\n Win32 Version: 10.0.0.0\n CodeBase: file:///C:/windows/mono/mono-2.0/lib/mono/gac/Microsoft.VisualBasic/10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll\n----------------------------------------\nSystem\n Assembly Version: 4.0.0.0\n Win32 Version: 4.6.57.0\n CodeBase: file:///C:/windows/mono/mono-2.0/lib/mono/gac/System/4.0.0.0__b77a5c561934e089/System.dll\n----------------------------------------\nSystem.Windows.Forms\n Assembly Version: 4.0.0.0\n Win32 Version: 4.6.57.0\n CodeBase: file:///C:/windows/mono/mono-2.0/lib/mono/gac/System.Windows.Forms/4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll\n----------------------------------------\nSystem.Drawing\n Assembly Version: 4.0.0.0\n Win32 Version: 4.6.57.0\n CodeBase: file:///C:/windows/mono/mono-2.0/lib/mono/gac/System.Drawing/4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll\n----------------------------------------\nSystem.Configuration\n Assembly Version: 4.0.0.0\n Win32 Version: 4.6.57.0\n CodeBase: file:///C:/windows/mono/mono-2.0/lib/mono/gac/System.Configuration/4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll\n----------------------------------------\nAccessibility\n Assembly Version: 4.0.0.0\n Win32 Version: \n CodeBase: file:///C:/windows/mono/mono-2.0/lib/mono/gac/Accessibility/4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll\n----------------------------------------\nBMSUtils\n Assembly Version: 1.6.2.29\n Win32 Version: 1.6.2.29\n CodeBase: file:///C:/mission_commander/BMSUtils.dll\n----------------------------------------\ndbwdp\n Assembly Version: 1.6.0.0\n Win32 Version: 1.6.0.0\n CodeBase: file:///C:/mission_commander/dbwdp.dll\n----------------------------------------\nBMSLocation\n Assembly Version: 1.0.4.0\n Win32 Version: 1.0.4.0\n CodeBase: file:///C:/mission_commander/BMSLocation.dll\n----------------------------------------\nSystem.Xml\n Assembly Version: 4.0.0.0\n Win32 Version: 4.6.57.0\n CodeBase: file:///C:/windows/mono/mono-2.0/lib/mono/gac/System.Xml/4.0.0.0__b77a5c561934e089/System.Xml.dll\n----------------------------------------\nSystem.Core\n Assembly Version: 4.0.0.0\n Win32 Version: 4.6.57.0\n CodeBase: file:///C:/windows/mono/mono-2.0/lib/mono/gac/System.Core/4.0.0.0__b77a5c561934e089/System.Core.dll\n----------------------------------------\n\n************** JIT Debugging **************\n Thanks in advance & all the best, Uwe[/t]</a1b7540aeb454df7a6cc546c7c9a66bb></a1b7540aeb454df7a6cc546c7c9a66bb></a1b7540aeb454df7a6cc546c7c9a66bb></a1b7540aeb454df7a6cc546c7c9a66bb></a1b7540aeb454df7a6cc546c7c9a66bb></a1b7540aeb454df7a6cc546c7c9a66bb></a1b7540aeb454df7a6cc546c7c9a66bb></a1b7540aeb454df7a6cc546c7c9a66bb></a1b7540aeb454df7a6cc546c7c9a66bb></module>
-
Serves you right!!! - when cross-breedin’ two opposite OS :smash: :mrgreen:
Sorry, cant help with the error , … seems some string format is not in expected (working) format ( float to integer) … Falcas could help you more … anyway, in windows it is working fine, so maybe linux/wine/visualbasic (but also, cough, psst, Falcas )
If still in then need , maybe workaround… you can try some real VM guest os , vmware, virtualbox ??? at least see if it is working there.
Cheers
-
Hi I made adjustments (in game) setting flights in save0.
Default KTO…
I save it and get “save day xxx”.I open the “save day xxx” in MC and save it as “save0” and overwrite original (after backing up ).
Now when I open new adjusted save0 in MC, the objectives are all gone and error shows.
Has this been the case with MC in the past?
Has turning game saves into start of campaign “save0” ever been possible? I thought it had been but I may be wrong.
If it was capable in past, it is no more.I think maybe exporting units from “save day xxx” to “save0” might be a solution.
-
I am pretty sure that there is a real difference between a save0.cam and a renamed savegame one.
For example a renamed one will not pause at start, I think at least some other differences. (fog of war).
I personally would use a te_new and export from there into a working save0.But perhaps other people know more for sure.
Cheers Obi1
-
It’s most certainly not possible.
-
Thanks guys , just making sure it’s not just me.
I usually don’t try it this way but someone did , and asked me why it won’t work.
I kinda Thought it would work myself but was mistaken.Exporting adjusted units works just fine though with the import/export options.
-
Looking forward to this and WDP being compatible for 4.35 - seems really strange not to be able to tweak anything, thanks for 4.35 and all the good work by everyone that puts it all together for us.
Oh and …. Happy New Year
David
-
Looking forward to this and WDP being compatible for 4.35 - seems really strange not to be able to tweak anything, thanks for 4.35 and all the good work by everyone that puts it all together for us.
Oh and …. Happy New Year
David
I’m using both MC and WDP in its latest version with 4.35
Gesendet von meinem SM-G930F mit Tapatalk
-
I’m using both MC and WDP in its latest version with 4.35
Gesendet von meinem SM-G930F mit Tapatalk
HI
Does it work? Didn’t realise.
-
MC seems to work okay for me WDP crashes on start up.
-
I’m using both MC and WDP in its latest version with 4.35
Gesendet von meinem SM-G930F mit Tapatalk
Same experience here - you did well when pointing that out, oakdesign, thanks a lot.
With best regards to all, keep yourselves safe always.