Mission Commander beta release
-
Komt als ik een beetje tijd heb
-
-
Found a minor, low-priority bug in MC 0.4.9.189:
Under Campaign - Dates, the DAY can only show 1 digit. If I want to increase days, it will show 1, 2, 3, 4, 5, 6, 7, 8, 9, 1, 1, 1, ā¦
At first, I thought it was just a display bug, and the counter actually continues to day 48, as in BMS. When Iām at 9, however, no matter how many times I click up (10, 20, 50, ā¦ times), I only need 6 clicks down to get back to 9, so it appears to stop at Day 15. By saving the TE in MC and then opening it in BMS, I confirmed this. -
After adding a new unit, I get a message āDouble found for ID: 12763 both used by ObjectiveNr: 6026 and UnitNr: 1523ā and āFound double use of IDā in the status bar when reloading the file. How do I fix that?
-
You donāt need to fix that. The message is telling you that the double ID has been fixed already.
Just sve your mission and you are done.Gr Falcas
-
Found a minor, low-priority bug in MC 0.4.9.189:
Under Campaign - Dates, the DAY can only show 1 digit. If I want to increase days, it will show 1, 2, 3, 4, 5, 6, 7, 8, 9, 1, 1, 1, ā¦
At first, I thought it was just a display bug, and the counter actually continues to day 48, as in BMS. When Iām at 9, however, no matter how many times I click up (10, 20, 50, ā¦ times), I only need 6 clicks down to get back to 9, so it appears to stop at Day 15. By saving the TE in MC and then opening it in BMS, I confirmed this.Thx, Iāll take a look at it when I can find some BMS time again.
Gr Falcas
-
Hi Falcas
Thanks for all your work on Falcon BMS.Iām trying to convert the training missions from Allied Force to BMS 4.33 (Iāve come back to F4 just as 4.33 U1 was released so I canāt get BMS 4.32) and every time I try to convert one of the training missions, I get the message:
ācould not read pilot data. Your mission may be corruptā. The system then hangs.
Is there anything I can do to fix this to allow me to convert the missions?
-
Hi eliot323,
Did you ever have any luck converting those training missions? It would be great to fly them in 4.33.
-
Hi Wilkotaz
I will try again and let you knowā¦ -
Thanks bud, its a bit beyond meā¦
-
Hi Falcas,
I wanted build a new TE using your tool MC for fine tuning. Unfortunately I wrote in a describable field called āScenarioā an other description as was written before (watch thumbnail below). Afterwards the TE was unusable. All airbases were gone. I tried to reload the TE in MC, but MC was asking for the Mini-COMAO.tac which was certainly not on my computer. A got an āUnhanded exceptionā pop up with following details:See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.IndexOutOfRangeException: Index was outside the bounds of the array. at MissionCommander.fclsMain.IsCarrierObjective(Int32 oNr) at MissionCommander.fclsMain.GetAirbaseName(VU_ID AB_ID) at MissionCommander.fclsMain.FillUnits() at MissionCommander.fclsMain.SetSelect(String strName) at MissionCommander.fclsMain.tabMain_SelectedIndexChanged(Object sender, EventArgs e) at System.Windows.Forms.TabControl.OnSelectedIndexChanged(EventArgs e) at System.Windows.Forms.TabControl.WmSelChange() at System.Windows.Forms.TabControl.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.6.1076.0 built by: NETFXREL3STAGE CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- Mission Commander Assembly Version: 0.4.9.189 Win32 Version: 0.4.9.189 CodeBase: file:///C:/Program%20Files%20(x86)/Falcon/MC/Mission%20Commander.exe ---------------------------------------- Microsoft.VisualBasic Assembly Version: 10.0.0.0 Win32 Version: 14.6.1055.0 built by: NETFXREL2 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.6.1075.0 built by: NETFXREL3STAGE 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.6.1055.0 built by: NETFXREL2 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.6.1055.0 built by: NETFXREL2 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.6.1068.2 built by: NETFXREL3STAGE 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.6.1055.0 built by: NETFXREL2 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.5.5.0 Win32 Version: 1.5.5.0 CodeBase: file:///C:/Program%20Files%20(x86)/Falcon/MC/BMSUtils.DLL ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.6.1055.0 built by: NETFXREL2 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.6.1067.0 built by: NETFXREL3STAGE CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- dbwdp Assembly Version: 1.4.0.0 Win32 Version: 1.4.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/Falcon/MC/dbwdp.DLL ---------------------------------------- BMSLocation Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/Falcon/MC/BMSLocation.DLL ---------------------------------------- LzssManaged Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/Falcon/MC/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.
Now I got some Questions:
What is die field āScenarioā for?
Is there any chance to repair the TE?Thanks for your answers in advance
Prot
-
Maybe a bit dark coders humor, but I like this one
No worries, your can safe your mission.Here a small explanation.
All the objectives (airbases, cities ect) need to be saved somewhere. But this is not done in every mission file.
In the mission files, like your Mini-COMAO.tac, only the differences are saved. These are the Objective Delta.
So is a runway or a building has been damaged, destroyed and ownership ect.
The objectives are save only in 4 files, the te_new, save0.cam, save1.cam, save2.cam.
These are the āstarting pointā/base files for the TEs (TRN) and Campaigns.
These are the scenario files.The Scenario field is the pointer to the file where to look for to find all the objectives.
If you can still open the file by ignoring the error, you might be able to rename the field to: TE_NEW.In case this doesnāt help and you donāt have a backup of your fileā¦ send it over and I should be able to fix it.
Gr Falcas
Hi Falcas,
I wanted build a new TE using your tool MC for fine tuning. Unfortunately I wrote in a describable field called āScenarioā an other description as was written before (watch thumbnail below). Afterwards the TE was unusable. All airbases were gone. I tried to reload the TE in MC, but MC was asking for the Mini-COMAO.tac which was certainly not on my computer. A got an āUnhanded exceptionā pop up with following details:See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.IndexOutOfRangeException: Index was outside the bounds of the array. at MissionCommander.fclsMain.IsCarrierObjective(Int32 oNr) at MissionCommander.fclsMain.GetAirbaseName(VU_ID AB_ID) at MissionCommander.fclsMain.FillUnits() at MissionCommander.fclsMain.SetSelect(String strName) at MissionCommander.fclsMain.tabMain_SelectedIndexChanged(Object sender, EventArgs e) at System.Windows.Forms.TabControl.OnSelectedIndexChanged(EventArgs e) at System.Windows.Forms.TabControl.WmSelChange() at System.Windows.Forms.TabControl.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.6.1076.0 built by: NETFXREL3STAGE CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- Mission Commander Assembly Version: 0.4.9.189 Win32 Version: 0.4.9.189 CodeBase: file:///C:/Program%20Files%20(x86)/Falcon/MC/Mission%20Commander.exe ---------------------------------------- Microsoft.VisualBasic Assembly Version: 10.0.0.0 Win32 Version: 14.6.1055.0 built by: NETFXREL2 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.6.1075.0 built by: NETFXREL3STAGE 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.6.1055.0 built by: NETFXREL2 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.6.1055.0 built by: NETFXREL2 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.6.1068.2 built by: NETFXREL3STAGE 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.6.1055.0 built by: NETFXREL2 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.5.5.0 Win32 Version: 1.5.5.0 CodeBase: file:///C:/Program%20Files%20(x86)/Falcon/MC/BMSUtils.DLL ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.6.1055.0 built by: NETFXREL2 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.6.1067.0 built by: NETFXREL3STAGE CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- dbwdp Assembly Version: 1.4.0.0 Win32 Version: 1.4.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/Falcon/MC/dbwdp.DLL ---------------------------------------- BMSLocation Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/Falcon/MC/BMSLocation.DLL ---------------------------------------- LzssManaged Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/Falcon/MC/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.
Now I got some Questions:
What is die field āScenarioā for?
Is there any chance to repair the TE?Thanks for your answers in advance
Prot
-
The Scenario field is the pointer to the file where to look for to find all the objectives.
If you can still open the file by ignoring the error, you might be able to rename the field to: TE_NEW.In case this doesnāt help and you donāt have a backup of your fileā¦ send it over and I should be able to fix it.
Gr Falcas
Thank you, you saved my ass. I made a copy of te_new. renamed it to mini_COMAO and all runs again.
Greets Prot
-
Thank you, you saved my ass. I made a copy of te_new. renamed it to mini_COMAO and all runs again.
Greets Prot
Noooooo donāt do that!!!
-
Why not, thats the only way to solve it. I have now two files of te_new (+ mini_comao) and I swiched te TE back to TE_new.
And it works . -
Take car Prot!!! te_new can be called for other reasons
-
Bump. Falcas, donāt mean to bother you, ok, I do, lol. Any progress on the 256 theater map??
C9
-
@Cloud:
Bump. Falcas, donāt mean to bother you, ok, I do, lol. Any progress on the 256 theater map??
C9
Vacation time
And at the same time a lot of coding is needed for Dev internal things which got a little higher prio.
Gr Falcas
-
In the meantime, found a gamebreakerā¦ SORRY for spoiling vac. but Iāll forget ā¦ so here is safe.
All was checked/found under Balkanās theater., if any of importance.
1. Clipboard 4 - when listin Stations+ILS , MC cant display more then (CampID) 512 , for larger is says (0) , and there are 14000+ in Balkanās, bigger #word perhaps ?
2. Clipboard 5 - this is biggie, Squadron Transfer (moving) is screwed up for (to)->Carrier. , uses CampId instead (F4) TaskforceCarrierNaval - ID (found out hard way
- Please , give an editbox for airbaseID , not just pull-down menu
Adding new squadron is OK.
3. Clipboard 6 - when looking in āAdvancedā window, ā¦ TargetID , DestX , DestY , cant be āzeroedā ā¦ not expecting 0 input?
āwhen my carrier broke, taskforce targeted an SA-2 site in coast (o0) , and Iāve couldnāt āzero-outā the target, even ācheck unitsā complained. Flags seems OK.*4 - not real important, but Iāve seen it work in Korea, just FYI - Canāt preview aircraft skins in Balkanās ā¦ different DB?
(to keep you busy a little
)
Cheers
WF - Please , give an editbox for airbaseID , not just pull-down menu
-
Hey,
No not spoiling at all. I still read the forum once in a while during vacation
Thanks for the report!
Nr 1, Need to check this. Will be a very easy one to change/fix.Nr2, Will fix this so you can just select the carrier. And so, I will not add a editbox with a number.
Nr3, All these still need to be added, will take some time and looked at if really needed to be changed by a user.
Nr4, Will give this one a try as well. It should workā¦
Gr Falcas
In the meantime, found a gamebreakerā¦ SORRY for spoiling vac. but Iāll forget ā¦ so here is safe.
All was checked/found under Balkanās theater., if any of importance.
1. Clipboard 4 - when listin Stations+ILS , MC cant display more then (CampID) 512 , for larger is says (0) , and there are 14000+ in Balkanās, bigger #word perhaps ?
2. Clipboard 5 - this is biggie, Squadron Transfer (moving) is screwed up for (to)->Carrier. , uses CampId instead (F4) TaskforceCarrierNaval - ID (found out hard way
- Please , give an editbox for airbaseID , not just pull-down menu
Adding new squadron is OK.
3. Clipboard 6 - when looking in āAdvancedā window, ā¦ TargetID , DestX , DestY , cant be āzeroedā ā¦ not expecting 0 input?
āwhen my carrier broke, taskforce targeted an SA-2 site in coast (o0) , and Iāve couldnāt āzero-outā the target, even ācheck unitsā complained. Flags seems OK.*4 - not real important, but Iāve seen it work in Korea, just FYI - Canāt preview aircraft skins in Balkanās ā¦ different DB?
(to keep you busy a little
)
Cheers
WF - Please , give an editbox for airbaseID , not just pull-down menu