FlightControl-Master/MOOSE
1
0
Fork 0
mirror of https://github.com/FlightControl-Master/MOOSE.git synced 2025-10-29 16:58:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

New code

Browse Source
This commit is contained in:
FlightControl_Master 2018-03-15 11:41:52 +01:00
parent 650f16084b
commit c5c437fa50
4 changed files with 18 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Moose Development/Moose/Functional/Designate.lua
View File

@ -1,7 +1,5 @@
--- **Functional** -- Management of target **Designation**. Lase, smoke and illuminate targets.
--
-- ![Banner Image](..\Presentations\DESIGNATE\Dia1.JPG)
--
-- ===
--
-- DESIGNATE is orchestrating the designation of potential targets executed by a Recce group,

2
Moose Development/Moose/Tasking/Task_A2A.lua
View File

@ -1,7 +1,5 @@
--- **Tasking** - The TASK_A2A models tasks for players in Air to Air engagements.
--
-- ![Banner Image](..\Presentations\TASK_A2A\Dia1.JPG)
--
-- ====
--
-- ### Author: **Sven Van de Velde (FlightControl)**

2
Moose Development/Moose/Tasking/Task_A2G.lua
View File

@ -1,7 +1,5 @@
--- **Tasking** - The TASK_A2G models tasks for players in Air to Ground engagements.
--
-- ![Banner Image](..\Presentations\TASK_A2G\Dia1.JPG)
--
-- ====
--
-- ### Author: **Sven Van de Velde (FlightControl)**

21
Moose Development/Moose/Tasking/Task_A2G_Dispatcher.lua
View File

@ -1,5 +1,7 @@
--- **Tasking** - The TASK_A2G_DISPATCHER creates and manages player TASK_A2G tasks based on detected targets.
--
--
--
-- ====
--
-- ### Author: **Sven Van de Velde (FlightControl)**
@ -21,6 +23,8 @@ do -- TASK_A2G_DISPATCHER
--- # TASK\_A2G\_DISPATCHER class, extends @{DetectionManager#DETECTION_MANAGER}
--
-- ![](..\Presentations\TASK\_A2G\_DISPATCHER\Dia1.JPG)
--
-- The TASK\_A2G\_DISPATCHER class orchestrates dynamic **A2G Task Dispatching** based on the detection results of a linked @{Detection} object.
-- It uses the Tasking System within the MOOSE framework, which is a multi-player Tasking Orchestration system.
-- It provides a truly dynamic battle environment for pilots and ground commanders to engage upon,
@ -61,6 +65,8 @@ do -- TASK_A2G_DISPATCHER
-- CC |Gori| is controlling Mission "Alpha", "Beta", "Gamma".
-- CC |Gudauta| is controlling Missions "Overlord" and "Desert Storm".
--
-- ![](..\Presentations\TASK_A2G_DISPATCHER\Dia1.JPG)
--
-- ## 0.1. Mission Menu (Under the Command Center Menu)
--
-- The Mission Menu controls the information of the mission, including the:
@ -70,6 +76,8 @@ do -- TASK_A2G_DISPATCHER
-- - **Create Task Reports**: A menu to create various reports of the current tasks dispatched by the A2G dispatcher.
-- - **Create Mission Reports**: A menu to create various reports on the current mission.
--
-- ![](..\Presentations\TASK_A2G_DISPATCHER\Dia6.JPG)
--
-- For CC |Gori|, Mission "Alpha", the menu structure could look like this:
--
-- Radio MENU Structure (F10. Other)
@ -88,8 +96,6 @@ do -- TASK_A2G_DISPATCHER
-- Note that the Mission Briefing is not the briefing of a specific task, but rather provides an overall strategy and tactical situation,
-- and explains the mission goals.
--
-- [picture]
--
--
-- ### 0.1.2. Mark Task Locations Menu
--
@ -234,10 +240,17 @@ do -- TASK_A2G_DISPATCHER
-- F1. SEAD.001
-- F2. SEAD.002
--
-- An example from within a running simulation:
--
-- ![](..\Presentations\TASK_A2G_DISPATCHER\Dia7.JPG)
--
-- Each Task Type Menu would have a list of the Task Menus underneath.
-- Each Task Menu (eg. `CAS.001`) has a **detailed Task Menu structure to control the specific task**!
--
-- An example from within a running simulation:
--
-- ![](..\Presentations\TASK_A2G_DISPATCHER\Dia8.JPG)
--
--
-- ### 0.3.1. Planned Task Menu
--
@ -266,7 +279,9 @@ do -- TASK_A2G_DISPATCHER
--
-- **The Join Task is THE menu option to let a Player join the Task, and to engage within the Mission.**
--
-- [Picture]
-- An example from within a running simulation:
--
-- ![](..\Presentations\TASK_A2G_DISPATCHER\Dia9.JPG)
--
--
-- ## 0.4. Assigned Task Menu