Jump to content

Recommended Posts

Posted

Hi guys, im looking at the best way of generating automated CAP, but I only want a certain type of aircraft, so red has MiG-21 AI CAP and Blue has F-5 AI CAP only.

 

How would I go about this guys?

 

Thanks

Posted
Hi guys, im looking at the best way of generating automated CAP, but I only want a certain type of aircraft, so red has MiG-21 AI CAP and Blue has F-5 AI CAP only.

 

How would I go about this guys?

 

Thanks

 

Check these example missions:

 

https://github.com/FlightControl-Master/MOOSE/tree/master/Moose%20Test%20Missions/CAP%20-%20Combat%20Air%20Patrol

 

Cap tutorial videos here:

 

 

Let me know if this fits with what you were looking for.

For more info, look in my signature...

 

 

 

Kind regards,

Sven

[TABLE][sIGPIC][/sIGPIC]|

[/TABLE]

Posted

I guys, sorry I forgot all about this thread!

 

Flight control I am aware of your excellent MOOSE framework, unfortunately im not the one with the brains, and my colleague has been talking about re-doing our mission in MOOSE as its currently running MIST, for now though I will look at Gcicap thanks guys.

Posted
I guys, sorry I forgot all about this thread!

 

Flight control I am aware of your excellent MOOSE framework, unfortunately im not the one with the brains, and my colleague has been talking about re-doing our mission in MOOSE as its currently running MIST, for now though I will look at Gcicap thanks guys.

 

That was not my intention of my post :-) but thanks for the feedback. I think honestly the GCICAP script will still suit you the best solution for the moment.

 

Some more juice is needed in the MOOSE framework to level to that kind of process automation. Slowly this will come though and the API will become more accessible. It will work different though, I mean, it will provide more flexibility and the approach will be different.

 

Sven

[TABLE][sIGPIC][/sIGPIC]|

[/TABLE]

Posted

Hey instead of the panic about coding or such, why dont you just put a plane in your mission called 'Plane', give it a route that you want, add the MOOSE.lua to your mission then a DO script and paste the following into it?

 

local Spawn_plane = SPAWN:New("Plane"):InitLimit( 2, 0 )

Spawn_Plane:InitRepeatOnEngineShutDown()

Spawn_Plane:SpawnScheduled(300,0)

 

That's it. It will respawn every 300 seconds, and after it lands and shuts down, 2 of them, for infinity. That's not coding thats copy and paste buddy, give it a go!

___________________________________________________________________________

SIMPLE SCENERY SAVING * SIMPLE GROUP SAVING * SIMPLE STATIC SAVING *

Posted

Ragnar Da (I think) had quite a nice simple CAP script that relied on aircraft already on the map - so depending on your viewpoint - was actually better for small co-ops than the infinitely spawning GCICAP etc as it didn't knock your frames around so much and also the player group's kills made a real and fairly immediate difference to the mission outcome. Do a search for safe harbour or perhaps safe harbor as I seem to recall that was the mission name.

Posted
Ragnar Da (I think) had quite a nice simple CAP script that relied on aircraft already on the map - so depending on your viewpoint - was actually better for small co-ops than the infinitely spawning GCICAP etc as it didn't knock your frames around so much and also the player group's kills made a real and fairly immediate difference to the mission outcome. Do a search for safe harbour or perhaps safe harbor as I seem to recall that was the mission name.

 

Moose can do all that and more with just changing a few parameters. If you don't want infinite spawning piece of cake. If you only want a few enemy planes in the air at any given time piece of cake.

Posted

Some really good suggestions here chaps. Thank you so much for your input.

 

For what its worse I tried GCICAP and it wasn't working. it works in the example.miz so I must of screwed something up!

Posted

Will be the classic naming issues of the template aircraft, the double underscores. or number of zones or number of template aircraft or similar. any mistake and it doesn;t work, but often gives you the reason in the logs.

Some really good suggestions here chaps. Thank you so much for your input.

 

For what its worse I tried GCICAP and it wasn't working. it works in the example.miz so I must of screwed something up!

___________________________________________________________________________

SIMPLE SCENERY SAVING * SIMPLE GROUP SAVING * SIMPLE STATIC SAVING *

Posted
Will be the classic naming issues of the template aircraft, the double underscores. or number of zones or number of template aircraft or similar. any mistake and it doesn;t work, but often gives you the reason in the logs.

 

I will check the logs, good idea.

 

I have just double checked the mission, all templates look to have the right name. I put in the .lua no GCI so I just have two templates for each side __CAP__blue1 and blue2 and same for the red. Have 3 zones called BlueCAPzone1,2,3 and same for red.

Posted (edited)

This is in the logs over and over again

 

00358.181 WARNING SCRIPTING: GCICAP| No airbase for red found

00358.182 WARNING SCRIPTING: GCICAP| No airbase for blue found

00358.182 WARNING SCRIPTING: GCICAP| No active aircraft for blue found

 

is this whats going wrong? I have them set to air start so not sure whats going on!

 

It also says no active EWR for blue, despite there being two EWR's on blue

Edited by Wright_GR1
Posted

So at a guess (and from memory so apologies in advance if I get it wrong) you haven't set up a zone for each blue and red airbase you want GCICAP to use. The EWR units need to be those the script knows about. 55G6 EWR, 1L13 EWR, Hawk sr, Patriot str are the ones it knows by default.

Posted

You are right I havent set any airfileds up, I read the documentation and I do not remember any requirement to do so! Thats probably my issue! I will look at the example.miz again. I have them set to air start and assumed they would make their way back to nearest friendly base once they were low on fuel/ammo

 

I have two georgian 1L13's on blue! And two Russian ones on red, its only complaining about the blue one though.

 

Can i just say thanks for all the help on this chaps, its awesome

Posted (edited)

Yep caps starting airborne should head to a nominated GCICAP base when they are low on fuel and/or ammo. New ones should take off to replace them when this happens. One bit of advice when building a mission with GCICAP, build in layers and do GCICAP early and confirm it is working before adding the next layer of complication. On the documentation........are you using the notes lukrop included or the pdf I wrote for the old version of the script? I think lukrop links to my pdf but hasn't really done much himself.

The pdf definitely mentions putting a trigger zone over the airfields you want GCICAP to use, note though that lukrop's version is different to the version that the pdf is written for so there are small things that are different now and in that regard the pdf is out of date. Still probably useful as a general guide though and it walks you through the process of setting up GCICAP with screenshots etc.

Edited by Stonehouse
Posted

Easy to help easy questions we feel passionate about. Having CAP is a must have.

You are right I havent set any airfileds up, I read the documentation and I do not remember any requirement to do so! Thats probably my issue! I will look at the example.miz again. I have them set to air start and assumed they would make their way back to nearest friendly base once they were low on fuel/ammo

 

I have two georgian 1L13's on blue! And two Russian ones on red, its only complaining about the blue one though.

 

Can i just say thanks for all the help on this chaps, its awesome

___________________________________________________________________________

SIMPLE SCENERY SAVING * SIMPLE GROUP SAVING * SIMPLE STATIC SAVING *

Posted
Easy to help easy questions we feel passionate about. Having CAP is a must have.

 

Good news, its working!

 

I didn't have the airfield trigger zones, the blue EWR was a red herring! I was originally working from lukrops documentation but as soon as I read Stonehouse's I got it working.

 

Again guys, thank you very much for all the help. Much appreciated.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...