MOOSE - Mission Object Oriented Scripting Framework

[Habu_69]

Different opinion. I am a complete scripting neophyte and I found that using Sven's recommended LDT setup to be quite helpful for developing LUA scripts. The Intellisense provides a ready, context-relevant reference to MOOSE framework and the MOOSE example scripts and missions are a click away.

[Mikkall]

You really don't need the LDT setup if you just want to use the framework and have fun. Download the base MOOSE lua (there's one that someone pared down to minimum size for faster loading), download the script examples and download Notepad++ to edit .lua files, enjoy yourself. Sven and his compatriots have a hell of a tool there but Sven's "setup" is geared more towards experienced developers.

 

Ya, but that Intellisense thing is pretty dang helpful when you're an idiot.:pilotfly:

[dooom]

quick question... has anyone succeeded in getting detection to work within the AI Balancer? My AI spawned units do not seem to detect any Opfor and I cannot seem to get the detection to work'

[Delta99]

quick question... has anyone succeeded in getting detection to work within the AI Balancer? My AI spawned units do not seem to detect any Opfor and I cannot seem to get the detection to work'

 

Doom, you probably saw my response on Discord about this right? If you use something like AI_CAP along with AI_BALANCER the detection should work just fine. AI_BALANCER on its own with AI_PATROL I don't think does much of anything for detection and attacking the enemy.

[fargo007]

Ya, but that Intellisense thing is pretty dang helpful when you're an idiot.:pilotfly:

 

You don't have to be a beginner to benefit from it.

 

Being in technology, I was capable without it using only notepad++.

 

Once I set the environment up as recommended, my productivity increased easily fivefold.

[mwd2]

With MOOSE i can set a TACAN Ch. to an air unit - but why not to a ground unit?

[shagrat]

With MOOSE i can set a TACAN Ch. to an air unit - but why not to a ground unit?

Because Ground units in DCS don't support TACAN. You can't address things through MOOSE that are not accessable in the DCS script engine.

[AwesomestMaximusTheFifth]

Hello,

 

I am following the instructions to setup the LDT, but I keep on getting the following error when I add the Moose_Framework project.

 

Any ideas on what I'm doing wrong?

[FlightControl]

Hello,

 

I am following the instructions to setup the LDT, but I keep on getting the following error when I add the Moose_Framework project.

 

Any ideas on what I'm doing wrong?

 

I vaguely remember that issue. I had it too.

 

Are you sure you are using the 32-bit or the 64-bit versions of JAVA RTM and Eclipse?

 

Because when you mix them, I think you get this issue.

 

FC

[FlightControl]

quick question... has anyone succeeded in getting detection to work within the AI Balancer? My AI spawned units do not seem to detect any Opfor and I cannot seem to get the detection to work'

 

Which version of DCS and which version of MOOSE?

[FlightControl]

Works like a charm! Many thanks!

 

You're from Belgium?

[AwesomestMaximusTheFifth]

Hi FlightControl,

 

I have both Java 32 and 64 installed. And using the 64 bit LDT.

 

I'll uninstall them and only reinstall the 32 bit, hopefully that'll fix the problem

 

Regards

[AwesomestMaximusTheFifth]

Well I couldn't download the 32bit LDT, so I tried to reinstall the 64bit but still getting the same problem. but this time only 2 errors appeared

 

EDIT:

 

I managed to get Java and LDT 32 bit installed

 

Even though the errors appear, the InteliSense in LDT is working correctly.

 

I think this is something that can be ignored

 

TIME TO SCRIPT IN MOOSE, looking forward to making great missions

 

Thank you FC

Edited February 13, 2018 by AwesomestMaximusTheFifth

[reise_caparzo]

Hi, first of all thanks for this awesome tool

 

Im a totaly rookie with lua, but i've been able to do great things with moose!

 

I could make a group or groups, repeat his own route over and over again to simulate a patrol.

I've used these lines:

 

Patrol1 = GROUP:FindbyName ( "GroupName" )
Patrol1:PatrolRoute()

 

And works!

 

and if i want to make more thant one groups just repeat this lanes changing Patrol1 for Patrol2,3,4....etc

 

And my cuestion is if its possible using FilterPrefixes make Moose understand that all Group Names started by "Patrol" do PatrolRoute(). I mean put 50 diferents groups and they repeat his own routes just naming them Patrol #001,Patrol #002,#003.......#050....

 

I tried using Moose Prefixes

 

Patrol =SET_GROUP:New()
Patrol:FilterPrefixes( { "Patrol" } )
Patrol:FilterStart()

But i cant make it work.

I tried

 

Patrol =SET_GROUP:New()
Patrol:FilterPrefixes( { "Patrol" } )
Patrol:FilterStart()

P1 = GROUP:FindbyName( "Patrol" )
P1:PatrolRoute()

and

Patrol =SET_GROUP:New()
Patrol:FilterPrefixes( { "Patrol" } )
Patrol:FilterStart()

P1 = GROUP:FindbyName( Patrol )
P1:PatrolRoute()

 

I used GROUP:FindByName, SET_GROUP:FindByName but didnt works for me. So if someone knows how to did works and can share the lines I'll be very greatful

 

Thanks and sorry if my english is too bad, not my native language

Edited February 13, 2018 by reise_caparzo

[Pikey]

If the SPAWN method is the same for all these units then you want the OnSpawn() function http://flightcontrol-master.github.io/MOOSE/Documentation/Spawn.html##(SPAWN).OnSpawnGroup

then tell them what to do as they pop in.

 

If you aren't spawning (then why not? :) ) you can iterate through the set with this: SET_BASE:ForEach(IteratorFunction, arg, Set, Function, FunctionArguments)

 

Demo missions in the repository for that here: https://github.com/FlightControl-Master/MOOSE_MISSIONS/blob/Release/SET%20-%20Data%20Sets/SET-101%20-%20Group%20Sets/SET-101%20-%20Group%20Sets.lua

Edited February 13, 2018 by Pikey
incomplete answers

[reise_caparzo]

Wow! So now i got it!!! Really thanks man, i use ForEachGroup and then PatrolRoute().

 

I use

 

ContinuousPatrol = SET_GROUP:New():FilterPrefixes("PaCo"):FilterStart()

ContinuousPatrol:ForEachGroup(
function( GroupObject )
   GroupObject:E( { GroupObject:PatrolRoute()} )
 end )

 

Now all grups who names start by "PaCo" do continuos patrol!

 

Again THANKS!!!!

[rassy7]

Having a heck of a time getting zones to work properly. Ultimately trying to get any of the Is(Completely, Partly or Not)InZone conditions to work. Tried following the tutorials, copied and pasted every snippet I could find from the test missions or this an other threads and even typed character-for-character from the YouTube tutorials, but nothing is working. Tried with Zones and Polygon Zones. Tried using groups found by name as well as group sets.

 

I know MOOSE and the mission files are loading because I am able to spawn objects and if I add RAT script to the mission file, it works. After a couple days of trial and error, I loaded up the test mission and when that didn't work, I knew something was wrong. Does MOOSE not work with 2.5? I'm testing on version v2.5.0.14304? I hit a wall. What am I missing here?

 

(my test begins at 1:57)

[Delta99]

Having a heck of a time getting zones to work properly. Ultimately trying to get any of the Is(Completely, Partly or Not)InZone conditions to work. Tried following the tutorials, copied and pasted every snippet I could find from the test missions or this an other threads and even typed character-for-character from the YouTube tutorials, but nothing is working. Tried with Zones and Polygon Zones. Tried using groups found by name as well as group sets.

 

I know MOOSE and the mission files are loading because I am able to spawn objects and if I add RAT script to the mission file, it works. After a couple days of trial and error, I loaded up the test mission and when that didn't work, I knew something was wrong. Does MOOSE not work with 2.5? I'm testing on version v2.5.0.14304? I hit a wall. What am I missing here?

 

(my test begins at 1:57)

 

Which demo mission are you having an issue with? Most everything works in Moose for 2.5 as far as we have discovered.

[rassy7]

It's ZON-100 Normal Zone. I loaded the same one from the tutorial video

[Delta99]

It's ZON-100 Normal Zone. I loaded the same one from the tutorial video

 

Looks like there is something wrong with the Smoke functionality. Likely something that ED changed in DCS. Always look at your dcs.log file as it will help to point out errors that are thrown.

 

If you can, try commenting out any of the smoke commands and see what happens. I don't have time to try that right now but I will be that the main functionality is working fine.

 

Thanks for pointing this out. I will enter it as a bug (OR DCS BUG) on the Moose issue tracker.

[rassy7]

If you can, try commenting out any of the smoke commands and see what happens.

 

Will do. Thanks for taking a look.

[FlightControl]

Move of MOOSE documentation pages

 

Guys,

 

The documentation pages have moved to:

 

http://flightcontrol-master.github.io/MOOSE_DOCS/

 

So _DOCS is added to the URL!

 

There is an automatic redirect on the old utl to the new location, but any detailed pages won't be accessible anymore.

 

FC

[PVI_Eagle]

multiple zones (CAZ)

 

Is it possible to have multiple capture zones in one mission?

I found a workaround and in the attached mission I start a new lua file for each captured base...

But in this way my radio menu is filled with old missions that I can not erase via moose...

Please Help me

 

 

BATTLE_ZONES_1bis.zip

[FlightControl]

You mean, for TASK_CARGO_TRANSPORT? Yes you can! Get onto discord and we can discuss!

[FlightControl]

The main GITHUB web page readme section of the MOOSE repositories have been updated (and are still in revision).

 

Have a look as it may contain some new info for you. Mostly is done for the development optimization. Note that now the MOOSE framework is composed out of a number of repositories which are edited or generated. The generated ones contain artefacts.

 

https://github.com/FlightControl-Master/MOOSE

 

You can still download the latest version from the MOOSE release page.

 

kind regards,

Sven