Mission Commander beta release
-
Ok, found some time this afternoon and was a quick fix.
Download the new version 0.5.5.298.OglLod has been fixed.
I did check POH and all is working fine on my system, just need to wait longer until the map has loaded.gr Falcas
The link on your website seems to be down. It says no file and server is down.
-
Who can explain how works the create low level map? I don’t understand how is centered the map…fully illogical!!!
example
right click on the centered mountain (below)and now here the result and honestly, I am lost!!!
-
HELLO Falcas.
How to limit the quantity of F16 weapons or to prohibit the use of certain weapons.
For example, I want to limit the maximum number of 120C to 30.
I use MC【Mission Commander】, but I cannot modify the maximum number. Is it possible for the Patriots to move on their own, not to be fixed in a certain position.There are also documents and manuals for [MC] mission commanders.Because there are some functions that don’t know it.
Thanks very much -
You cant in MC , those max values are in F4 database , so you need to use falcon db editor. , BUT!, changing those files will have consequences for Online play with servers which use falcon’s anti-cheat ,
as you db-files will be then different/mismatch from those on server. … so… that DB will work only for with servers which allow edited database and/or configuration files, not restricted, and Offline single-play.Patriots move on their own as any other unit when they have a reason to , campaign engine relocates every unit as it sees fit. (sometimes maybe not so strategically, but is another thing)
So in campaign you’ll see every unit is moving on their own, which is not so in TE (tactical engagement) single-mission files , where you have to define a path for every unit.
For that you must understand difference between single mission (TE) , and campaign mode of Falcon.In falcon map screen you can manually send your own units to a different location (to manually control ground unit, turn off ‘controlled by HQ’, click on unit and move waypoint circle to a loc.) … and in MC you can do also with setting unit destination/objective in units properties.
-
Thank you for your detailed explanation. I often see in BFB that patriots have shifted the clearance of radar, but I didn’t find it in North Korea. Please tell me how to do it in the screenshot MC.
-
Patriots move on their own as any other unit when they have a reason to , campaign engine relocates every unit as it sees fit. (sometimes maybe not so strategically, but is another thing)
So in campaign you’ll see every unit is moving on their own, which is not so in TE (tactical engagement) single-mission files , where you have to define a path for every unit.
For that you must understand difference between single mission (TE) , and campaign mode of Falcon.In falcon map screen you can manually send your own units to a different location (to manually control ground unit, turn off ‘controlled by HQ’, click on unit and move waypoint circle to a loc.) … and in MC you can do also with setting unit destination/objective in units properties.
As it’s so interesting, white_fang, would you kindly let me know if in your experience did also Soviet mobile SAMs (SA-11, SA-17, Tunguskas…) behave the same? I seemed to argue that, at least.
Thanks in advance! With best regards,
-
Thank you for your detailed explanation. I often see in BFB that patriots have shifted the clearance of radar, but I didn’t find it in North Korea. Please tell me how to do it in the screenshot MC.
Look the ‘Travel to’ (wide string field in the middle) entry in main properties , not in the advanced options. Changing that will make the unit to move to that location. But which way unit will move to said location will always be auto-calculated by the game engine.
Good luck -
As it’s so interesting, white_fang, would you kindly let me know if in your experience did also Soviet mobile SAMs (SA-11, SA-17, Tunguskas…) behave the same? I seemed to argue that, at least.
Thanks in advance! With best regards,
No prob!!. They move just fine, on they own or manual. (actually checked that 100% with, sa-11, sa-10, sa-17). Only fixed sam’s will not move, sa-2 , sa-5 …BUT, in Campaign , not TE.
As said in TE you must edit waypoint for GU’s yourself, in mission editor.
If there is some problem regarding movement of any ground unit in campaign, I’m not aware of it… eh?
-
New version released, see first post.
Lots of new goodies.
Enjoy,
Falcas
-
Is it feasible -in the future- to change flags from a family of objectives? Just like you can change now fuel and supply levels. I use Terrain Editor to do this right now.
-
This request has been in the table for some time already. Partially implemented with the select area in the map by the mouse. However, much more important features have higher priorities.
Even if it doesn’t look like it, much more is happening under the hood than the changlog impliesWhen time permits, this will be implemented more and more.
Gr Falcas
EDIT: pretty all the flags for a campaign are set correctly when you use the advanced objective feature reset OBJ.
-
"Objectives
- Changed, Obj Adv option, renumber Objectives. You can set a range where CampId is not used.
The numbers NOT used are random in the range."
GOD Bless , Falcas Thank you.
-edit: Falcas, when setting default skin for sq, what when there are no any stars (//) , what does that mean then? I cant figure out why (in TE) it defaults to skin no.2 out of 3 , I don’t think it is the squadron name 14007 , it is not defined in camo.cfg., and I don’t believe it is hardcoded for kc135 tnkr.
Are there any other way to force skin 1 of 3. , not 2. ?
Thanks-edit: ok, skin changes as you change sq name (no.) on the fly … cool
- Changed, Obj Adv option, renumber Objectives. You can set a range where CampId is not used.
-
The info about the “*” is in the squadron page
Which skin is set depends on the name of the squadron.
Can be overrulled by hardcoded Sq names, the CAMO file or the Skin File.
As soon as you start changing the skin in BMS itself, you will be messing it upGr Falcas
-
issue when the menu POL/PAL is open
-
What are you trying to do and what file are you looking at??
Normally that tab/page should be empty.
C9
-
It should be empty for the clean campaign file, saveX.cam or TE, but not later for eg. autosaves … it will get populated as objectives are occupied/changed.
But yes, this seems as a little bug, no big deal, just variable.
‘Buffalo soldiers’: ’ I think we squashed a beetle…’ ~ 2m00s
-
How do you change the status of a bridge with Mission Commander in a TE (100% operational to destroyed ) ?
-
New version released, see first post.
Lots of new goodies.
Enjoy,
Falcas
Mission Commander V 0.5.6.334 crashing always when trying to Clone Flight. Created a new TE from scratch also to try if it’s anything about it, no change. Installed BMS version: 4.33U5.
Crash does NOT happen with an older version of Mission Commander (V 0.5.1.239).Reproduce:
- Units-Tab: Right click on flight -> Clone Flight
Stack-Trace:
************** Ausnahmetext ************** System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt. bei MissionCommander.fclsMain.CloneFlight(VU_ID FlightToCloneID, Boolean CreatePack) bei MissionCommander.fclsMain.cmsUnits_ItemClicked(Object sender, ToolStripItemClickedEventArgs e) bei System.Windows.Forms.ToolStrip.OnItemClicked(ToolStripItemClickedEventArgs e) bei System.Windows.Forms.ToolStripDropDown.OnItemClicked(ToolStripItemClickedEventArgs e) bei System.Windows.Forms.ToolStrip.HandleItemClick(ToolStripItem dismissingItem) bei System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e) bei System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e) bei System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met) bei System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met) bei System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea) bei System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea) bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) bei System.Windows.Forms.Control.WndProc(Message& m) bei System.Windows.Forms.ScrollableControl.WndProc(Message& m) bei System.Windows.Forms.ToolStrip.WndProc(Message& m) bei System.Windows.Forms.ToolStripDropDown.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.7.2633.0 built by: NET471REL1LAST_C. CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll. ---------------------------------------- Mission Commander Assembly-Version: 0.5.6.334. Win32-Version: 0.5.6.334. CodeBase: file:///D:/Games/Falcon%20BMS/Mission%20Commander/Mission%20Commander.exe. ---------------------------------------- Microsoft.VisualBasic Assembly-Version: 10.0.0.0. Win32-Version: 14.7.2556.0 built by: NET471REL1. 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.2556.0 built by: NET471REL1. 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.2633.0 built by: NET471REL1LAST_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.2556.0 built by: NET471REL1. 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.2556.0 built by: NET471REL1. 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.2556.0 built by: NET471REL1. 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.2612.0 built by: NET471REL1LAST_B. 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.2556.0 built by: NET471REL1. 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.12. Win32-Version: 1.6.1.12. CodeBase: file:///D:/Games/Falcon%20BMS/Mission%20Commander/BMSUtils.DLL. ---------------------------------------- System.Windows.Forms.resources Assembly-Version: 4.0.0.0. Win32-Version: 4.7.2556.0 built by: NET471REL1. 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. ---------------------------------------- dbwdp Assembly-Version: 1.5.0.0. Win32-Version: 1.5.0.0. CodeBase: file:///D:/Games/Falcon%20BMS/Mission%20Commander/dbwdp.DLL. ---------------------------------------- mscorlib.resources Assembly-Version: 4.0.0.0. Win32-Version: 4.7.2556.0 built by: NET471REL1. CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_de_b77a5c561934e089/mscorlib.resources.dll. ---------------------------------------- BMSLocation Assembly-Version: 1.0.3.0. Win32-Version: 1.0.3.0. CodeBase: file:///D:/Games/Falcon%20BMS/Mission%20Commander/BMSLocation.DLL. ---------------------------------------- LzssManaged Assembly-Version: 1.0.0.0. Win32-Version: 1.0.0.0. CodeBase: file:///D:/Games/Falcon%20BMS/Mission%20Commander/LzssManaged.DLL. ---------------------------------------- Accessibility Assembly-Version: 4.0.0.0. Win32-Version: 4.7.2556.0 built by: NET471REL1. CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll. ----------------------------------------
-
Need to take a look at it. Too much going on.
Gr Falcas
-
just wondering if anybody knows how to get the High res MFD 's and know how to put your avatar on the back of your cockpit seat. thanks.