MOOSE - Mission Object Oriented Scripting Framework

@BoneDust

What about EWR_Red ?

As I understand it, the error you're getting says that your A2ADispatcher global variable is invalid (so it can't be indexed):

A2ADispatcher = AI_A2A_DISPATCHER:New( EWR_Red )

Are you sure that EWR_Red is a valid detection object?

Are you sure it exists while the script is running?

@BoneDust

 

What about EWR_Red ?

 

As I understand it, the error you're getting says that your A2ADispatcher global variable is invalid (so it can't be indexed):

 

A2ADispatcher = AI_A2A_DISPATCHER:New( EWR_Red )

 

Are you sure that EWR_Red is a valid detection object?

Are you sure it exists while the script is running?

Yes for both :thumbup:

91 should be the line number.

Thanks man.

I couldn't get it to work, so I started from scratch again and its working now.

I'm running this respawn script for a KC130. It respawns no problem, but it doesn't perform its task of refueling; it just reaches the steer point and then RTB.

I would like it to stay on station to refuel clients.

What am I missing?

SpawnTanker1 = SPAWN:NewWithAlias("KC130 Tanker","TEXACO")
SpawnTanker1:InitRandomizeRoute(0,0,15000,3658)  --steer point start, end radius in meters, and height in meters
SpawnTanker1:InitRepeatOnEngineShutDown()
SpawnTanker1:InitLimit(1,6)
SpawnTanker1:SpawnScheduled(300,0)
SpawnTanker1:SpawnAtAirbase( AIRBASE:FindByName( AIRBASE.Caucasus.Kobuleti ), SPAWN.Takeoff.Hot )
)

@BoneDust

I'd try it without route randomization (in case it's messing with ME wp tasks, somehow).

If it still doesn't work, I guess you could script the tanker enroute task instead.

I'd use :OnSpawnGroup() combined with :EnRouteTaskTanker(), with some sort of logic to decide when to push the task.

@BoneDust

 

I'd try it without route randomization (in case it's messing with ME wp tasks, somehow).

 

 

If it still doesn't work, I guess you could script the tanker enroute task instead.

I'd use :OnSpawnGroup() combined with :EnRouteTaskTanker(), with some sort of logic to decide when to push the task.

Cheers man. I'll give that a try.

Lots of dead links on OP.

Hope all is well.

Looking forward to getting back to mission editing, and learning Moose.

Your best bet is it join the MOOSE Discord, it is much more active and up to date.

UH1 radio guidance

Hello

Maybe someone has a solution. There is a problem with UH1 and navigation to the ground unit. I know that this can be done, the script CSAR sends a signal to be traced by UH1. How to do it so that the soldiers could also send such a signal. Turning off after seeing the helicopter.

Thank you

I have a question whether it is possible to enable AI_A2A_GCICAP once. The idea is that he would send only one hunter for one purpose without respawning after destruction? Of course, being included for new purposes.

I have a question whether it is possible to enable AI_A2A_GCICAP once. The idea is that he would send only one hunter for one purpose without respawning after destruction? Of course, being included for new purposes.

A2ADispatcher:SetSquadron( "Mozdok", AIRBASE.Caucasus.Mozdok, { "SQ CCCP MIG-31" }, 1 )

Inviato dal mio CPH1877 utilizzando Tapatalk

I have a question as a new user thinking about learning MOOSE. On the first page of the thread you mention having 2 lua files:

Moose.lua

Moose_.lua

When I go to the downloads (https://github.com/FlightControl-Master/MOOSE/releases) I see MOOSE Patch 2.4.13 and it does not have a zip download available and only the one Moose.lua file. Is that all I need to get started besides the code editor and some coffee?

Thanks

I have a question as a new user thinking about learning MOOSE. On the first page of the thread you mention having 2 lua files:

Moose.lua

Moose_.lua

When I go to the downloads (https://github.com/FlightControl-Master/MOOSE/releases) I see MOOSE Patch 2.4.13 and it does not have a zip download available and only the one Moose.lua file. Is that all I need to get started besides the code editor and some coffee?

Thanks

Good question. I look forward to a direct link to the DL.

Guys, that is the link.

Moose.lua = include version of MOOSE that you'll need to add to every mission (if you plan on using MOOSE scripts in it)

Source code (zip) = files needed to set up MOOSE in LDT (the zip contains a different Moose.lua, which is NOT meant to be included in your missions)

Watch

In fact, I recommend that you watch the entire YT series.

Guys, that is the link.

 

Moose.lua = include version of MOOSE that you'll need to add to every mission (if you plan on using MOOSE scripts in it)

 

Source code (zip) = files needed to set up MOOSE in LDT (the zip contains a different Moose.lua, which is NOT meant to be included in your missions)

 

 

Watch

to set it up in LDT.

 

In fact, I recommend that you watch the entire YT series.

I tried it 3 times and when I click FINISH I get an error message about "An internal error occurred during: "Build Modules".

Edit: I tired again and it seems to have worked. :thumbup:

Thanks

We all get those internal error messages, just ignore them.

The important thing is that you get intellisense working.

We all get those internal error messages, just ignore them.

 

The important thing is that you get intellisense working.

Intellisense is working. I just tested it. Now for the studying...:D

Thanks

Hi folks,

I'm new to mission development using the moose framework and over the past couple of weeks have immersed myself in learning and applying it. Recently I ran my first coop mission using Moose and tested it alongside the group I'm involved with. One thing I'm interested in is finding a technique for balancing the mission such that any opposing Ai that spawn can be scaled, based on the number of players in the mission on the Blue side.

I understand that the ai balancer can be applied for aircraft on the players side, but is there a way to begin a scheduled spawn by monitoring how many players take a cap role? The current mission implements scheduled spawning such that there is always a potential of 10 Ai Cap in the air on the Red side. The problem was that it wore our CAP players down, as they felt they weren't making much progress.

thanks in advance

@Tonmeister

Off the top of my head (without having actually tested it), I'd start by doing the following:

In Mission Editor:

- Create a bunch of late activated AI CAP groups (4 units each). If you want to, give them waypoints and tasks as well.

- Give all relevant clients a common prefix in their unit names (EDIT: No need to do this, just ignore it)

In the MOOSE script:

- Define a set that targets all relevant clients (you can use a prefix filter for this).

- Define the AI CAP groups as SPAWN objects

- You can then use a scheduler to periodically check the number of relevant clients that are currently active

- Create a scheduled spawn logic for the AI CAP groups, based on number of active clients

- You can use :InitLimit() in order to limit the number of AI CAP units spawned (it can also be used to make them respawn)

- Decide how do you want to trigger the scheduler (for instance, you could use a coalition F10 menu for this)

Script example:

As I said, this is just off the top of my head, there might be simpler/better ways of achieving the same goal (using AI dispatchers, for instance)... also, it's pretty raw, you'd need to polish it.

EDIT: After some testing, looks like the prefix filter is causing problems with the unit count, so use the active filter only (it seems to work fine). Also, use SET_CLIENT instead of SET_UNIT.

Thanks, HardCard.

I'll look into your suggestion and thanks for the example code and comments, I didn't think of that approach. There's still much to learn from moose, it seems quite a powerful and flexible approach to mission design and balancing the mission can quite a challenge when player numbers change. I'll see how I go with it.

thanks!

Hello

Since i am running the dedicated serverversion of dcs i am not able to get my ratscript running.

Missions that run well on my pc won`t run on my server pc. (running, but whithout the script)

Maybe someone can point me in the right direction ?!

Ups ! Sorry .

Problem solved !

Found the problem between the headphones :music_whistling:

Hi, I am having a bit of trouple with the PseudoATC module. It looks as though I was able to instatiate MOOSE and the PseudoATC correctly via:

pseudoATC=PSEUDOATC:New()
pseudoATC:Start()
pseudoATC:DebugOn()

However, I do not get any F10 menu entry, and I also see the following in the log:

2019-06-02 03:32:51.022 INFO    SCRIPTING: Error in SCHEDULER function:[string "C:\Users\Jeff\AppData\Local\Temp\DCS\/~mis00000B75.lua"]:66433: attempt to index field '?' (a nil value)
2019-06-02 03:32:51.022 INFO    SCRIPTING: stack traceback:
   [string "C:\Users\Jeff\AppData\Local\Temp\DCS\/~mis00000B75.lua"]:6062: in function <[string "C:\Users\Jeff\AppData\Local\Temp\DCS\/~mis00000B75.lua"]:6058>
   [string "C:\Users\Jeff\AppData\Local\Temp\DCS\/~mis00000B75.lua"]:66433: in function 'PlayerTakeOff'
   [string "C:\Users\Jeff\AppData\Local\Temp\DCS\/~mis00000B75.lua"]:66338: in function <[string "C:\Users\Jeff\AppData\Local\Temp\DCS\/~mis00000B75.lua"]:66323>
   (tail call): ?
   [C]: in function 'xpcall'
   [string "C:\Users\Jeff\AppData\Local\Temp\DCS\/~mis00000B75.lua"]:6360: in function 'onEvent'
   [string "Scripts/World/EventHandlers.lua"]:13: in function <[string "Scripts/World/EventHandlers.lua"]:11>

I am using the latest version of MOOSE from git.

@Q-Ball

Could you attach the full script + mission?