MOOSE - Mission Object Oriented Scripting Framework

New updates have been released in 2.2.0.pre:

• Fixed the Status Report format in TASK_A2G and TASK (acessible through the Mission Menu).
  
• WARNING! Fixed the way functions can be called from waypoints. Modified the :TaskFunction() method in CONTROLLABLE! Cleaned up a lot of noisy code. Now it is very nice and clean. :TaskFunction gets now 2 parameters, the function in a string, and variable arguments, which are set to the CONTROLLABLE and given as variable parameters when the function gets called. I don't think anybody used this method yet in their code, so I don't think this is a (big) compatibility issue.
  
• WARNING! Renamed method :RoutePointGround() of COORDINATE to :WaypointGround(). I don't think anybody used this method yet in their code, so I don't think this is a (big) compatibility issue.
  
• WARNING! Renamed method :RoutePointAir() of COORDINATE to :WaypointAir(). I don't think anybody used this method yet in their code, so I don't think this is a (big) compatibility issue.
  
• Added method :RouteGroundTo() in CONTROLLABLE to route ground groups towards various COORDINATEs.
  
• Added method :RouteAirTo() in CONTROLLABLE to route air groups towards various COORDINATEs.
  
• Modified the way :RouteTo() works. Much nicer code now.
  
• Added REPORT in new Report.lua in Core.
  
• Reworked DESIGNATE class... Improved performance, added a limit of maximum detections in scope, better distribution of targets and recces, menu system is much improved.
  
• Optimized DETECTION_BASE and derived DETECTION_ classes in various ways.
  
• Optimized MENU_COMMAND_GROUP to handle changing function and parameters without having to change the menu text!!!
  
• Implemented nearest DESIGNATE distance, which is set by default to 12000 meters (both ground and air).
  
• Added a maximum markings per designated target group in DESIGNATE. So not all FACs are occupied.
  
• Optimized the designation report in DESIGNATE. Move the horizontal line.
  
• Ensured in DESIGNATE that when targets are ordered to be smoke or designated, that this also will happen. Was issue with the scheduler, which got garbage collected before actually being executed, resulting in an obsolete schedule.
  
• Fixed the TASKING, coordinates are now updated when enquiring a task report.
  

Some of these fixes will greatly improve your game play! Like the coordinates now being updated in the planned task reports.

You can download the latest release from: https://github.com/FlightControl-Master/MOOSE/releases

FC

Interesting :book:

• Added method :RouteGroundTo() in CONTROLLABLE to route ground groups towards various COORDINATEs.

Thanks Sven, integrated into my mission and hosting it on the server

Some more fixes, ensure you have the latest version.

Especially when using AI_GCICAP in DCS 2.1.1. in NTTR.

(DCS 2.1.1. behaves differently than DCS 1.5.7. on route point settings).

• Fixed problem with waypoint actions for DCS world 2.1.1.8244. This version behaves differently than DCS world 1.5.7. in terms of waypoint actions for airborne units. Fixes had to be done in AI_A2A, AI_A2A_GCI, AI_A2A_CAP, AI_A2A_PATROL.
  
• Fixed problem in SCHEDULERDISPATCHER with the GetClassNameAndID not existing for some objects.
  

You can download the latest release from: https://github.com/FlightControl-Master/MOOSE/releases

FC

I think I'm blind here. This code gives Index error on first line.

VehicleGroup = GROUP:FindByName( 'REDConvoy' )
local ToCoord = ZONE:New('SafePoint'):GetCoordinate()
VehicleGroup:RouteGroundTo(ToCoord, 11, 'Vee', 1)

Mission have a convoy of tanks "REDConvoy" and a Zone "SafePoint".

Gives error: attempt to index global 'GROUP' (a nil value)

I think I'm blind here. This code gives Index error on first line.

 

VehicleGroup = GROUP:FindByName( 'REDConvoy' )
local ToCoord = ZONE:New('SafePoint'):GetCoordinate()
VehicleGroup:RouteGroundTo(ToCoord, 11, 'Vee', 1)

Mission have a convoy of tanks "REDConvoy" and a Zone "SafePoint".

Gives error: attempt to index global 'GROUP' (a nil value)

Your Moose.lua file is not correctly loaded. Check if MOOSE is loaded.

Ensure you set a trigger at mission start, loading Moose.lua in a DO SCRIPT.

Oops, will check that.

That was it. Works perfect now, tanks! :thumbup:

Guys, I'll be off for a few days.

Thanks to all

Before I go away a few days, allow me this.

Got this little object in a box a few weeks ago delivered at my home.

Was thinking what would be the best way to say thanks, and decided to say

Thanks to all the users and the contributors!

Most of you knew about my situation, and you stayed and supported the project. It kept me busy while recovering from a severe illness.

You guys are amazing.

thank you!

Sven

Just an open question, what do I need to do with this object?

Is it a trophy that is sent around year by year?

Yep. More or less. The idea is to honor a member of the community for his/her contribution each year and initiate a poll for the community to vote. Then send it to the "winner".

Have a look at the original nomination thread to get an idea.

https://forums.eagle.ru/showthread.php?t=187597

Congrats, Sven! You deserve it!

Congrats Sven , you deserve it

Nice trophy Sven!!!

Is there any chance someone could have a little check of this basic template? I seem to be having issues with groups despawning.

Some groups despawn fine, others seem to just land and shutdown but remain on the airfield. Sometimes in their original 2 ship, others seem to detatch into singles but again remain on the airfield. Inevitably this leads eventually to the runway becoming blocked with the dodgy AI pathfinding.

As far as i can see, it should be set to despawn when the groups are near the airfield.

Might be worth noting, i was testing and running on 10x time compression, as it seems to take a while for the problem to start.

Here are the two mission files i'm running for the two areas.

TemplateBuildNew.miz

Hi Shadow, there is a known issue with some of the planes just landing and not de-spawning. The root cause will be somewhere hidden in the logic. I'll find it but I just need to look for it or discover what isn't working properly. It will take time to find the cause.

Just use the modules as they are great. As time goes fine tuning will happen.

Thank you for reporting.

FC

Is there a module or a way to check an airfield for idle aircraft and remove them? that could be run once in a while.

Is there a module or a way to check an airfield for idle aircraft and remove them? that could be run once in a while.

+1 good idea

Aye it's been core to Moose for many months. Depending if you want it as part of your SPAWNed aircraft then it's :InitCleanup(number of seconds at idle) http://flightcontrol-master.github.io/MOOSE/Documentation/Spawn.html##(SPAWN).InitCleanUp

There is also an entire cleanup class http://flightcontrol-master.github.io/MOOSE/Documentation/CleanUp.html

I'd suggest looking through those help files to get an idea what it can do.

Is there a module or a way to check an airfield for idle aircraft and remove them? that could be run once in a while.

Spending hours making a missions just to fly it by myself is counter productive. I will already know the mission too well to enjoy it.

I need to grab this thought and say something. This was the exact reason I hated the ME and mission design, it destroyed my immersion. But this is also the EXACT reason why I learned MOOSE, because I could make a mission I did not know what was going to happen in.

The secret to good mission design (amongst many other things) is replayability and good, but managed random events/placement. Having an engine randomly position a random unit, with a random course achieves that, and MOOSE is one of those tools (amongst others) that can be used to achieve it more easily than just the ME, or pure scripting.

The challenge is to make "random" not too much so the replayability then fits the basic structure of the mission and doesn't break what you need the AI to do, but the human can react and perform enough to overcome such randomness.

Or a simple example, you want random air defences. You create a template of choices in it, that template needs to be realistic, you don't want a SA-3, SA-6 template with an SA-10 or SA-15 in it. There comes your experience as a deisgner and an understanding of military assets and their relative performance both in real life AND their adjusted performance in the game.

CLEANUP_AIRBASE? Just not sure if I built this functionality in the module.

If not, it is a good idea to have this function included.

Look guys. Am right now away from home.

When I get back, which is in a week, I can look at this issue. This can be fixed.

Hope you understand.

Hey FlightControl and the Moose guys.

I have a knoob question.

I have Moose working, and when I load my mission lua file at mission start, the items begin spawning immediately.

I want to control them and have them spawn according to triggers.

What's the simplest approach here?

I tried calling the second line in a trigger DO SCRIPT but it didn't work.

Thanks,

lua contents:

Spawn_Vehicle_Limited_Scheduled_RandomizeRoute = SPAWN:New( "Spawn Vehicle 1" ):InitLimit( 4, 20 ):SpawnScheduled( 10, 0 )

Spawn_Group_1 = Spawn_Vehicle_Limited_Scheduled_RandomizeRoute:Spawn()

/Fargo007

Instead of do script file

use

do script

then copy paste in the first line into it

In the condition column use a flag value

then set that flag somewhere else and hey presto the code will execute

Type (ONCE) Condition ( Flag X = 1 ) Action Do script (paste your first line into text)

x = choose your own number

Thank you, I started with a fresh mission and have this generally working.

When I enter a trigger zone, a flag gets set, and the units start spawning.

I need to figure out how to get them to stop spawning though. Once that code gets switched on, it keeps running. Resetting the flag with a different trigger doesn't stop it.

I have been playing with the following, just to create some ai flights to test my air defenses:-

BlueSpawn1 = SPAWN
 :New( "RT NATO 1" )
 :InitLimit( 2, 10 )
 :InitRandomizeTemplate( { "SQ NATO F-15C", "SQ NATO F/A-18", "SQ NATO F-16C" } )
 :InitRandomizeRoute( 0, 0, 30000 )
 --:InitDelayOn()
 :SpawnScheduled( Frequency, 0.4 )

I have been running this just on a Do Script trigger.

Is there something within MOOSE that i can insert into that script call, to allow me to randomise the number of flight members. I currently have the aircraft templates set with just one aircraft, but ideally would like to be able to place just the one template aircraft in the editor, then let the script define how many are spawned in a flight, from a single ship up to a four ship.

I am looking through the documentation to sort this out, but figured i would post here incase it was something quick.

Thanks in advance for any help.