MOOSE - Mission Object Oriented Scripting Framework

[Habu_69]

I will post here a MOOSE code fragment based on the Menu method. This works to create a SIMPLE F10 Other menu item on a schedule, and delete it after use.

 

 

F18_Grp = GROUP:FindByName( " Player" )

Target_Zone = ZONE:New( "Target" )
EnfieldReply = "Colt 1, Enfield 1. Roger On our way."

HelpMsg = " Enfield 3, Colt 1. Request Assistance"
EnfieldResponse = "Colt 1, Enfield 1. Roger, on our way."

 function EnfieldMsg ()     -- Enfield response timer function
   MESSAGE:New( EnfieldResponse, 15, nil ):ToAll()
 end

--  These function commands are executed on F10 item invoke. 
 function ReqHelp()
    MESSAGE:New( HelpMsg, 15, nil ):ToAll()
    trigger.action.setUserFlag( '10', 1 )
    timer.scheduleFunction( EnfieldMsg, {}, timer.getTime() + 15 )  -- Delays Enfield response 15 sec.
    BanditsHot:Remove( 10, nil )   -- Removes the F10 menu item
  end     

MenuScheduler = SCHEDULER:New( nil,   -- F10 menu item scheduler
 function()

   if F18_Grp:IsPartlyInZone( Target_Zone ) then
       BanditsHot = MENU_COALITION_COMMAND:New( coalition.side.BLUE, "Bandits hot. Request Help", nil, ReqHelp )
       MenuScheduler:Stop()
    end

 end, {}, 10, 15 )

[goestrip]

You can try the code in this thread.

I used it for more or less for the same thing you are trying with excelent results.

 

Thanks, that's perfect :thumbup:

[Wizard1393]

So I just got into MOOSE a little bit and set up a simple GCI test mission modded a little from the example mission "AID-013 - AI_A2A - Intercept Test".

 

Now when/if friendly CAP reaches the airbase where RED GCI spawns, they will engage them on the ground. Now I got 2 damaged and idle (pilots standing outside aircraft) red GCI aircraft blocking the taxiway.

 

Is there a built in function to handle these situations, like "if standing still and not taking off for xx seconds then despawn"?

 

EDIT: I found the CLEANUP_AIRBASE class but I don't want to disable blue AI engaging anything around the airbase. I just want to remove spawned AI aircraft that has not moved for a certain amount of time since spawn.

Edited June 27, 2018 by chrisofsweden

[ScottyBS]

Hi,

Starting to get into this - some fantastic community work and support. I am very interested in the RANGE concept and have read and watched the videos. Is the mission in the video available anywhere to examine/use??

 

 

Thanks

Scott

[Haukka81]

So I just got into MOOSE a little bit and set up a simple GCI test mission modded a little from the example mission "AID-013 - AI_A2A - Intercept Test".

 

Now when/if friendly CAP reaches the airbase where RED GCI spawns, they will engage them on the ground. Now I got 2 damaged and idle (pilots standing outside aircraft) red GCI aircraft blocking the taxiway.

 

Is there a built in function to handle these situations, like "if standing still and not taking off for xx seconds then despawn"?

 

EDIT: I found the CLEANUP_AIRBASE class but I don't want to disable blue AI engaging anything around the airbase. I just want to remove spawned AI aircraft that has not moved for a certain amount of time since spawn.

 

 

 

Can you share your script ? Would help me out.

 

Thanks.

 

 

Sent from my iPhone using Tapatalk

[Swany]

Instead of this -

local AH64 = RAT:New("RAT_AH64")

AH64:SetCoalition("sameonly")

AH64:Spawn()

 

 

Would this be advisable -

 

local AH64 = RAT:New("RAT_AH64"):SetCoalition("sameonly")

AH64:Spawn()

 

or even

 

local AH64 = RAT:New("RAT_AH64")

AH64:Spawn():SetCoalition("sameonly")

 

End goal - Trying to tighten my code up. This, above, isn't big, regardless of the three chosen, but, when using the 1st one (which is how my script is), and I have a LOT of aircraft, I see a LOT of wasted space, just in the :SetCoalition() section (needless to say every other section).

 

As I learn things, I like to spell them out, step by step, but once I start getting them down, I like to make it smaller and smaller, executing only exactly what's needed.

 

And I posted this here instead of in the RAT area because it's more a LUA/MOOSE question than it is a RAT question, I was just using that as my sampe

[Wizard1393]

Can moose be used Persian Gulf?

 

Since AIRBASE has .Caucasus .NTTR and .Normandy I tried using the line

 

A2ADispatcher:SetSquadron( "HDR", AIRBASE:FindByName('Havadarya'), { "RED GCI MIG-23" } )

 

but MOOSE throws error "attempt to concatenate local 'AirbaseName' (a table value)" in the DCS.log

 

Help!

[shagrat]

Can moose be used Persian Gulf?

 

Since AIRBASE has .Caucasus .NTTR and .Normandy I tried using the line

 

A2ADispatcher:SetSquadron( "HDR", AIRBASE:FindByName('Havadarya'), { "RED GCI MIG-23" } )

 

but MOOSE throws error "attempt to concatenate local 'AirbaseName' (a table value)" in the DCS.log

 

Help!

Needs to be integrated in Moose, I guess.

[eric963]

Needs to be integrated in Moose, I guess.

 

 

 

Just use “airbasename” where airbasename is the exact name of the airbase on the f10 map screen.

 

 

Sent from my iPhone using Tapatalk

[ECV56_Polten]

Swany, IMO, the coding style is kind of subjective; it will depend on how do you like it most. The first example takes more lines to write, but is easier to follow if you want to debug or analyse the code. The third one is more compact, takes less lines; in a more complex code, this style will require less CPU and/or memory, but, if you get an error, it will be more difficult to read it and follow the logic.

 

Take this code I used in a mission as an example

ZonaEstaticos01 = ZONE:New("ZonaEstaticos01")
PointVecZ01 = ZonaEstaticos01:GetPointVec2()
PosX1 = PointVecZ01:GetX()
PosY1 = PointVecZ01:GetY()

 

I could make it smaller and use less variables, like this

PosX1 = ZONE:New("ZonaEstaticos01")PointVecZ01:GetPointVec2():GetX()
PosY1 = ZONE:New("ZonaEstaticos01")PointVecZ01:GetPointVec2():GetY()

 

As you can see, I reduced the code from 4 lines to 2, and 4 variables to 2, so it has a better performance and less use of memory, but is harder to understand and debug in case of problems

Edited June 28, 2018 by ECV56_Polten
correcting a typo

[funkyfranky]

Instead of this -

local AH64 = RAT:New("RAT_AH64")
AH64:SetCoalition("sameonly")
AH64:Spawn()

Would this be advisable -

local AH64 = RAT:New("RAT_AH64"):SetCoalition("sameonly")
AH64:Spawn()

Advisable... maybe. Depends on how you can read your code better :) Is it possible - no, not yet!

In the next version of RAT it will be :) In other MOOSE routines you can already do it. Depends if the self object of the class is returned by that function or not.

or even

local AH64 = RAT:New("RAT_AH64")
AH64:Spawn():SetCoalition("sameonly")

A big, red NO ;)

All API functions which define parameters need to come before the Spawn() call. Otherwise things can - they must not, but can - go terribly wrong.

[Swany]

Ok, I didn't think so on the last one ;) and I didn't realize it wasn't available in RAT yet. I made the assumption that because it was within MOOSE it could already do that.

 

My RAT file is huge with little one line code and was just hoping to tighten it up, kind of define everything in one shot/on one line ;)

 

Once again appreciate the help (and the RAT!)

[Wizard1393]

Just use “airbasename” where airbasename is the exact name of the airbase on the f10 map screen.

 

 

Sent from my iPhone using Tapatalk

 

Thats what I'm doing isn't it?

 

A2ADispatcher:SetSquadron( "HDR", AIRBASE:FindByName('[b]Havadarya[/b]'), { "RED GCI MIG-23" } )

 

Edit: Nevermind, I just got what you meant. Changed it to this works:

 

A2ADispatcher:SetSquadron( "HDR", 'Havadarya', { "RED GCI MIG-23" } )

Edited June 28, 2018 by chrisofsweden

[eric963]

MOOSE - Mission Object Oriented Scripting Framework

 

Thats what I'm doing isn't it?

 

 

 

A2ADispatcher:SetSquadron( "HDR", AIRBASE:FindByName('[b]Havadarya[/b]'), { "RED GCI MIG-23" } )

 

 

 

A2ADispatcher:SetSquadron(“HDR”,”Havadarya”, and the rest

 

 

Sent from my iPhone using Tapatalk

[Wizard1393]

A2ADispatcher:SetSquadron(“HDR”,”Havadarya”, and the rest

 

 

Sent from my iPhone using Tapatalk

 

Yeah, I got it (see edit) but thanks!

[Swany]

As you can see, I reduced the code from 4 lines to 2, and 4 variables to 2, so it has a better performance and less use of memory, but is harder to understand and debug in case of problems

 

 

Which is kind of what I was after, but I see your point. Your first example I read once and got it, your second I had to re-read it because I thought it was wrong but see where it's right, and also see your point ;)

 

Pick your battles is what it boils down to ;) Appreciate the advice!

[Wizard1393]

Can anyone shed some light over what "A2ADispatcher:SetIntercept( number )" does?

 

I'd like to have a certain interval where GCI would spawn.

As it is "by default", the GCI logic "replenishes" up to the overhead value right away when an active GCI is shot down, if the GCI target is still detected.

[ECV56_Polten]

Your first example I read once and got it, your second I had to re-read it because I thought it was wrong

 

Well, as a matter of fact, it is wrong, I fogot a ":" between ("ZonaEstaticos01") and PointVecZ01, the correct one wold be

 

PosX1 = ZONE:New("ZonaEstaticos01"):PointVecZ01:GetPointVec2():GetX()
PosY1 = ZONE:New("ZonaEstaticos01"):PointVecZ01:GetPointVec2():GetY()

Edited June 29, 2018 by ECV56_Polten
Typo

[eric963]

Can anyone shed some light over what "A2ADispatcher:SetIntercept( number )" does?

 

I'd like to have a certain interval where GCI would spawn.

As it is "by default", the GCI logic "replenishes" up to the overhead value right away when an active GCI is shot down, if the GCI target is still detected.

 

 

 

I’m pretty sure that’s the number in seconds the a2a dispatcher uses to determine where the detected target will be based on its speed and direction. It then decides which airfield to launch the gci intercept from based on that projected location.

 

 

Sent from my iPhone using Tapatalk

[Wizard1393]

I’m pretty sure that’s the number in seconds the a2a dispatcher uses to determine where the detected target will be based on its speed and direction. It then decides which airfield to launch the gci intercept from based on that projected location.

 

 

Sent from my iPhone using Tapatalk

 

Ahah! Thanks! You don't have knowledge about the "spawn delay" I'm asking about? :)

[RedeyeStorm]

Hi all,

I am trying to setup Eclipse but damm it is testing my skills allready. I think I finally got it where the map 'Moose Development' is noted as a source. When I press ok I got five errors about 'Build Modules' with the following java error: An internal error occurred during: "Build Modules".

java.lang.ArrayIndexOutOfBoundsException

 

SOS...SOS...Iceberg

[kunterbunt]

Hi all,

I am trying to setup Eclipse but damm it is testing my skills allready. I think I finally got it where the map 'Moose Development' is noted as a source. When I press ok I got five errors about 'Build Modules' with the following java error: An internal error occurred during: "Build Modules".

java.lang.ArrayIndexOutOfBoundsException

 

SOS...SOS...Iceberg

 

 

Same problem I have. Help appreciated.

[Pikey]

Fixed in Dev, it's due to the changes in DCS with finding parking spots. DCS added a method to obtain a free parking spot and we updated dev branch to use it. It's mainly been written by FunkyFranky who authored the RAT module and had a lot of problems here.

 

 

In the dev branch the aircraft will still take off airborne if they dont have a valid parking spot (eg you get a C130 to try take off from parking at a small airbase, or other more obvious problems liek them being full) But this avoids the issue with Spawn happening on runways that DCS introduced in 2.4 or 5.

 

 

Please help :)

 

I try to use simple intercept script:

 

So far red planes spawn if Blue side plane is seen in ewr radar. This works.

 

But no mater what i do i cant get those alert intercept planes to start from ramp in airbase, they always spawn air.

 

Can someone show me custom script for this.

 

All i need is ground alert intercept : when Blue plane is spotted in ewr radar > spawn red fighter ramp hot > takeoff and intercept and return base after that.

 

Thanks

 

 

Im bit lost

 

 

I load moose first. Here is my gai file that i load after moose:

 

A2ADispatcher:SetSquadronTakeoffFromParkingHot( "SQUADRON Red" ) > this wont work. Planes wont spawn land or air, if i delete this planes spawn air.

GCICAP_Red = AI_A2A_GCICAP:New( "EWR Red", "SQUADRON Red" ) > this part works fine.

 

 

Yes, its simple but i try to learn and make it simple as possible.

 

 

Help please :)

 

Sent from my iPhone using Tapatalk

[Pikey]

Unless you guys are wanting to immediately update and sync from the Dev branch and contribute to coding at your desktop using Github desktop, then setting up LDT has very little gains for all the effort. Just download moose, get notepad and write something. Too many people hung up on this and it's killing new uptake. This was designed this way as a dev environment so more people could contribute to the codebase, but there's only a handful of people that actually do that.

 

Hi all,

I am trying to setup Eclipse but damm it is testing my skills allready. I think I finally got it where the map 'Moose Development' is noted as a source. When I press ok I got five errors about 'Build Modules' with the following java error: An internal error occurred during: "Build Modules".

java.lang.ArrayIndexOutOfBoundsException

 

SOS...SOS...Iceberg

[funkyfranky]

Hi all,

I am trying to setup Eclipse but damm it is testing my skills allready. I think I finally got it where the map 'Moose Development' is noted as a source. When I press ok I got five errors about 'Build Modules' with the following java error: An internal error occurred during: "Build Modules".

java.lang.ArrayIndexOutOfBoundsException

SOS...SOS...Iceberg

Could be an incompatibility between the Java version and the LDT version. Which Java and LDT versions do you use?

I have Java 8 Update 131 and LDT 1.4.1. You might want to try LDT 1.4.2RC2 for newer Java. Just an idea...