[NON-TECHNICAL, WAD] Mision EMCON Settings

Matrix Games Forums

Forums Register Login Photo Gallery Member List Search Calendars FAQ

My Profile Inbox Address Book My Subscription My Forums Log Out

[NON-TECHNICAL, WAD] Mision EMCON Settings

View related threads: (in this forum | in all forums)

Logged in as: Guest

Users viewing this topic: none

Printable Version

All Forums >> [New Releases from Matrix Games] >> Command: Modern Operations series >> Tech Support >> [NON-TECHNICAL, WAD] Mision EMCON Settings

Page: [1]

Message

<< Older Topic Newer Topic >>

[NON-TECHNICAL, WAD] Mision EMCON Settings - 8/26/2015 8:32:24 AM

LuckyJim1010

Posts: 260
Joined: 7/6/2010
Status: offline

Hi all,
Just getting back into the game and a few things have come up
Do mission EMCON settings override all other inherited setting?
It looks like it to me and I assume that the 'Parent' becomes the mission
Thanks

< Message edited by emsoy -- 8/28/2015 9:35:43 PM >

Post #: 1

RE: Mision EMCON Settings - 8/26/2015 10:05:28 AM

Tomcat84

Posts: 1952
Joined: 7/10/2013
Status: offline

Basically the EMCON/Doctrine has a hierarchical flow:

Side -> Mission -> Unit

The side is the highest level you can go. There is nothing above side to inherit from.
If a unit is not on a mission then it starts out with these settings unless you manually change them. And after a manual change, if you select the unit and go to the EMCON window for example (Ctrl-F9) and hit Reset EMCON (use inherited settings) it erases whatever manual change you made and goes to what is currently set in the side doctrine window.

If a unit is assigned to a mission then it goes with the mission EMCON, not the side EMCON. Now these might be the same (if the mission EMCON is set to inherit from the side) or different (if mission is set to something custom).

Note that if a unit is on a mission and obeying the mission EMCON, if you then unassign it from the mission it will go back to the side EMCON. (as long as it is set to inherit from parent. It makes sense, if you change the parent (by unassigning from mission the parent changes from mission to side) it changes the setting.

Another note: if you give a unit that is not assigned to a mission a manual EMCON setting (thereby disabling the "inherit from parent" setting, it will not suddenly adapt the mission EMCON. It will stay on its previous setting until you tell it to go to an inherited mode, and then it will inherit from the mission setting.

Hope this helps. A lot of text and maybe written a bit confusingly.

Maybe I'll try to write something more concise on this subject in the future.

If you have further questions fire away!

_____________________________

My Scenarios and Tutorials for Command

(Scenarios focus on air-warfare :) )

(in reply to LuckyJim1010)

Post #: 2

RE: Mision EMCON Settings - 8/26/2015 12:14:49 PM

LuckyJim1010

Posts: 260
Joined: 7/6/2010
Status: offline

Superb explanation that clarifies what I was seeing in practise.

To be frank to a noob it may sound, and probably is, a little confusing but in practise it gives you fantastic control over a unit's ROE, EMCON etc.

I've been using the Uncle Mark's Tutorials to get back into the game and number 1 is superb for mucking about with things like this

Again my thanks.

(in reply to Tomcat84)

Post #: 3

RE: Mision EMCON Settings - 8/28/2015 8:24:07 PM

ComDev

Posts: 5735
Joined: 5/12/2006
Status: offline

Copy-paste from design documentation

Normal path for doctrine inheritance is unit - group - mission (if any) - side
NOTE! Have changed the below logics slightly from 1.07 onwards, and units in groups will evaluate group's doctrine before mission. This was done to allow the player to set the Quick Turnaround and Air Ops Tempo on the group/base instead of mission.
Examples:
Grouped unit not assigned to mission: unit - group - side
Grouped unit assigned to mission: unit - mission - side
Single unit not assinged to mission: unit - side
Single unit assinged to mission: unit - mission - side

For landed aircraft's Air Ops Tempo and Quick Turnaround settings we need to use the host's doctrine, so that bases can have different operational tempos. The doctrine inheritance path is aircraft - host unit - group - mission (if any) - side
Examples:
Aircraft on ship in a group not assigned to mission: aircraft - host unit - host unit's group - side
Aircraft on ship in a group assigned to mission: aircraft - host unit - group - host unit's mission - side
Aircraft on single ship not assigned to mission: aircraft - host unit - side
Aircraft on single ship assigned to mission: aircraft - host unit - host unit's mission - side

Aircraft on some mission types may be escorts and have their own separate doctrine / EMCON / WRA settings as these may be very different from the main body settings.

< Message edited by emsoy -- 8/28/2015 9:24:47 PM >

_____________________________