Mission Commander beta release
-
i m editing 80s MOD as u know.
i run MC, open save2.cam, click “add batalion”
it is ok but new batalion has 0 vehicle and cant be edited
close MC, run it again, click “add batalion”
alert box said “te_new.tac should not contain unit”what does it mean?
default campaign dont have this problem.Are you sure you are opening a .cam file?
As MC is gives you that remark if you are working with a file that is a scenario file (saveX.cam or te_new.tac).
But the file you have opened does not have the extention “.cam”.
Than you get this warning.This is for people that do editing on scenario files that they have renamed.
For example save1.cam renamed to save1.tac. (What you should not do)Gr Falcas
-
i will if i can. but when i notice the bug, i have made many changes to squads.
maybe this will help:
i del all unit in unit tab
goto campaign tab
all squads keep showing with yellow color
use TacEdit rebuild, they disappearThat makes total sense… But why go to TacEdit for this?
The orange color means that the Squadron in the campaign SquadInfo (campaign tab)
is not found in the unit list. Its up to the user to descide what to do with it.
Deleting all units from a campaign… why?
Next release will have these removed when you delete all units.Gr Falcas
-
Are you sure you are opening a .cam file?
As MC is gives you that remark if you are working with a file that is a scenario file (saveX.cam or te_new.tac).
But the file you have opened does not have the extention “.cam”.
Than you get this warning.This is for people that do editing on scenario files that they have renamed.
For example save1.cam renamed to save1.tac. (What you should not do)Gr Falcas
i m 100% sure. i test this dozen times.
i cant click wrong file again n again, right?
the alert box not pop up every time (but very high freq).That makes total sense… But why go to TacEdit for this?
The orange color means that the Squadron in the campaign SquadInfo (campaign tab)
is not found in the unit list. Its up to the user to descide what to do with it.
Deleting all units from a campaign… why?
Next release will have these removed when you delete all units.Gr Falcas
MC cant remove the yellow thing, only Tacedit dose.
i dont really want to del all unit, i do this to show u, MC cant refresh unit as well as Tacedit. -
New version of MC released.
See the first post for the link and the changelog.
Thanks again for all the reports, can’t be done without them.
Enjoy,
Falcas
-
Thanks for another great update to a great utility!
One feature I’d like to see added is the capability to edit pilot names. For me, it would add to the immersion of the sim. It was something you could do in Falcon 3.0.
-
Thanks for another great update to a great utility!
One feature I’d like to see added is the capability to edit pilot names. For me, it would add to the immersion of the sim. It was something you could do in Falcon 3.0.
Pilot names are generated/edited via the Strings.wch/.idx file. Don’t think MC could interface with it as it requires WitchFix. But who knows, there’s some pretty talented guys around lately.
C9
-
@Cloud:
Pilot names are generated/edited via the Strings.wch/.idx file. Don’t think MC could interface with it as it requires WitchFix. But who knows, there’s some pretty talented guys around lately.
C9
Why couldn’t MC do this? It doesn’t do this as I didn’t get to it. But the strings is about the easiest thing of all the database stuff.
Gr Falcas
-
Why couldn’t MC do this? It doesn’t do this as I didn’t get to it. But the strings is about the easiest thing of all the database stuff.
Gr Falcas
Did you not see where I said “But who know’s”???
C9
-
Big time thanks , one more time, for MC and for WDP as well!!!
Keep it up men!!!
-
@Cloud:
Did you not see where I said “But who know’s”???
C9
I guess now we do know who knows
-
thanks very much
-
need more function plz
i use TACedit to create batalion 1st, then brigade.
fill brigade ID to batalion as parent, but not fill batalion ID to brigade
click “check unit”, report error “brigade has no child”then i run MC, batalion window is normal and brigade window has no troops. i m not surprised.
then i expect “fix all batalion” button will fix this, but it dosn’tbtw, i m back to origin theater, still create batalion with 0 vehicle. that is why i use Tacedit.
-
need more function plz
i use TACedit to create batalion 1st, then brigade.
fill brigade ID to batalion as parent, but not fill batalion ID to brigade
click “check unit”, report error “brigade has no child”As I told you before… Better do this in MC
then i run MC, batalion window is normal and brigade window has no troops. i m not surprised.
then i expect “fix all batalion” button will fix this, but it dosn’t“fix all battalion”??? Where do you find this button?
In MC go to you brigade and use the “Add Battalion” button to add Battalions to your brigade.btw, i m back to origin theater, still create batalion with 0 vehicle. that is why i use Tacedit.
You still haven’t shown any reproducable example and this seem to happen only to you…
So what are you doing? Have you changed your database ect, ect, ect.
If you want help, you need to start helping yourself by giving more info.Gr Falcas
-
“fix all battalion”??? Where do you find this button?
Gr Falcas
unit tab, left buttom corner, “advance option”, “fix all batalion”
-
unit tab, left buttom corner, “advance option”, “fix all batalion”
… “fix all batalion” does not exists in MC…
Do you mean “Fix All Battalion Rosters”?
If so… has nothing to do moving battalions to brigades.
If you mean the function “Auto Fix All Batts and Brigs”… No has nothing to do with moving battalions to brigades.
If you click on any of these two buttons, MC will tell you exactly what it will do.Gr Falcas
-
yep i know, so i hope MC can rebuild parent and child relationship in the future.
-
Hi Falcas,
first of all, many thanks for your extraordinary work!!!I do not know if that was here a theme but I think I´ve found a small bug or limitation.
When I use Mission Commander Version 0.3.10.0 and edited a TE (Balkan Theatre) sometimes MC is unable to work this TE.
When I try to enter a flight an error message appeared.
I found out that this happened in that I have moved the “alternate field” at another airfield.Best regards
BumerangThe message:
Informationen über das Aufrufen von JIT-Debuggen
anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung.************** Ausnahmetext **************
System.OverflowException: Die arithmetische Operation hat einen Überlauf verursacht.
bei MissionCommander.fclsMain.FillUnits()
bei MissionCommander.fclsMain.cboType_SelectedIndexChanged(Object sender, EventArgs e)
bei System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
bei System.Windows.Forms.ComboBox.set_SelectedIndex(Int32 value)
bei MissionCommander.fclsMain.FillType(String Type)
bei MissionCommander.fclsMain.SetSelect(String strName)
bei MissionCommander.fclsMain.tabMain_SelectedIndexChanged(Object sender, EventArgs e)
bei System.Windows.Forms.TabControl.OnSelectedIndexChanged(EventArgs e)
bei System.Windows.Forms.TabControl.WmSelChange()
bei System.Windows.Forms.TabControl.WndProc(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)************** Geladene Assemblys **************
mscorlib
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.18444 built by: FX451RTMGDR.
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll.
–--------------------------------------
MissionCommander
Assembly-Version: 0.3.10.0.
Win32-Version: 0.3.10.0.
CodeBase: file:///C:/Program%20Files/MC%20Commander/MissionCommander.exe.Microsoft.VisualBasic
Assembly-Version: 10.0.0.0.
Win32-Version: 11.0.50938.18408 built by: FX451RTMGREL.
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.0.30319.18408 built by: FX451RTMGREL.
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.0.30319.18408 built by: FX451RTMGREL.
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.0.30319.18408 built by: FX451RTMGREL.
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.0.30319.18408 built by: FX451RTMGREL.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll.System.Runtime.Remoting
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.34108 built by: FX45W81RTMGDR.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll.F4Utils
Assembly-Version: 1.4.0.0.
Win32-Version: 1.4.0.0.
CodeBase: file:///C:/Program%20Files/MC%20Commander/F4Utils.DLL.System.Windows.Forms.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.18408 built by: FX451RTMGREL.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll.Microsoft.VisualBasic.resources
Assembly-Version: 10.0.0.0.
Win32-Version: 11.0.50938.18408 built by: FX451RTMGREL.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic.resources/v4.0_10.0.0.0_de_b03f5f7f11d50a3a/Microsoft.VisualBasic.resources.dll.Database
Assembly-Version: 1.0.0.0.
Win32-Version: 1.0.0.0.
CodeBase: file:///C:/Program%20Files/MC%20Commander/Database.DLL.mscorlib.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.18408 built by: FX451RTMGREL.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_de_b77a5c561934e089/mscorlib.resources.dll.LzssManaged
Assembly-Version: 1.0.0.0.
Win32-Version: 1.0.0.0.
CodeBase: file:///C:/Program%20Files/MC%20Commander/LzssManaged.DLL.************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsdatei der Anwendung oder des Computers
(machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.Zum Beispiel:
<configuration></configuration>
Wenn das JIT-Debuggen aktiviert ist, werden alle Ausnahmefehler an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht in diesem Dialogfeld behandelt. -
Hi Bumerang,
You are a aware that the latest version is 0.3.12?
See if you have the same with this and let me know please.Gr Falcas
-
-You are a aware that the latest version is 0.3.12?-
No I did not know.
The error is raised with the newer version!Thanks a lot!!!
-
Again thanks Falcas for your continuing support of this software.
Here at the 801st it does what TE editor once did.
We still do TEs but a mild mod of a cam file keeps the interest going too.
Much Regards ……Shadow