Possible to make S3 orbit around a moving carrier?

[PSYKOnz]

Hey there, does anyone know if it’s possible to make an S3 do an orbit (circle or racetrack) around a carrier? Would be very helpful on those longer missions. 
 

I know how to orbit it around a waypoint but is it possible to make the waypoint a moving vehicle rather than a map waypoint?

[Nealius]

+1

 

We need the ability to set a recovery tanker at 1500 orbiting the boat. Currently this is only possible with MOOSE or other lua scripting, which is too complex for most regular users who have zero coding experience or knowledge. 

[PSYKOnz]

I have a plan….

 

I’ll check back when I’ve tried it out, hopefully I can get it to work and if I do I’ll upload a mission with it

 

Before I start I need to know a few things.

 

what altitude should the S3 be at

what speed should the S3 be at

how wide should the circle be

What speed should the cv be going

does it orbit directly over the boat or to the side?

circle or racetrack?

Edited August 6, 2021 by PSYKOnz

[Amarok_73]

This can be achieved for recovery tanker as well as for carrier based AWACS with just few lines of really simple code, using the MOOSE and it's actually waaaay more easy than coding it from scratch.

https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/Ops.RecoveryTanker.html

 

 

BTW, recovery tankers ususaly orbiting at around 6000+ ft.

 

EDIT:

 

Try this script:

CVN7Tkr = RECOVERYTANKER:New(UNIT:FindByName("CVN71"), "CVN71 Tanker")
	:SetTACAN(10, "T71")
	:SetRadio(260)
	:SetCAllsign(CALLSIGN.Tanker.Shell)
	:SetSpeed(290)
	:SetAltitude(7000)
	:SetRacetrackDistances(10, 10)
	:Start()

Create file named somehow (CVNTanker.lua can do the trick), and paste there code from above.

In ME, create the trigger and load the MOOSE with it, then create next trigger that with some delay will load the file You've just created.

Still in ME add the carrier group, name it anyhow, then name the unit "CVN71", and add to it the tanker S3 group named "CVN71 Tanker" setting it as late activated and standing cold/hot on parking.

And that's it. You should have the carrier with S3, that will depart, then infinitelly circling on racetrack around the carrier, occasionally landing for refueling then departing again.

All the commands are pretty selfexplantatory, except the SetRacetrackDistances, where first parameter is length (or diameter perhaps?) of bow part of the racetrack, and second parameter is length of straight part of it.

Edited August 6, 2021 by Pipok

[PSYKOnz]

I’m hoping that my idea will be a script free option, but good to know there is a sticky based option!

 

Thanks for the tip about the height!

 

[PSYKOnz]

NAILED IT!

 

no scripts, no extra work just using the triggers and setting available in the ME.

 

its still very crude and needs a lot of tidying, but it works. chuck it in the editor or in sp missions, go to the f10 map, time advance (x20 seems to be good) and check it out

 

again its not very refined at the moment but as a proof of concept its good

 

CV71 operating with an S3B on a circular orbit at 6000ft overhead the boat and an E2D running racetracks around the group at 20000ft.

 

no playable spots on deck at the moment, add them in if you like, make any changes you want, make it better, up to you, once I have it tidied up ill upload it to the user files

 

I have text explaining what's happening when something happens so sit back and enjoy....

Recovery Gas and E2.miz

[Amarok_73]

As I can see, as this is strictly dependent of the waypoints and You need to have multiple of them moved in the case of any change this is rather not flexible.
I prefer to have it simple, and flexible, and if used with ops.NavyGroup from Moose, You need just two waypoints for carrier to have him run between them infinitely, with obstacle avoidance and no waypoints for tanker or AWACS, and turning the carrier into wind when the recovery window is created with F10 menu.
 

And I have it all with just couple of easily understandable lines of code.

 

Sand Devil 16_2(Day).miz

Edited August 10, 2021 by Pipok

[Nealius]

On 8/6/2021 at 5:28 PM, Pipok said:

In ME, create the trigger and load the MOOSE with it, then create next trigger that with some delay will load the file You've just created.

 

What specific triggers/settings do we need for these two triggers? That's my biggest issue with the MOOSE documentation. They give you the lua code but they don't show how to appy it in the mission editor. Do I need a "no event" trigger or a "once" or a "at mission start" trigger? Do I need flags? There's a gazillion permutations possible and typically only one combination actually works. 

Edited August 23, 2021 by Nealius

[Amarok_73]

First of all, all scripts should be wirtten so they're triggered only once, then any further retriggering will come from scheduled calls from within the script itself. It's because continuous triggers set in the ME (game engine internal triggering) are called every second, so in case You have the function that doesn't require such frequency and may be called sparsely, this generates unnecessary load on the server.

Then, about the Moose, what I do, I trigger the Moose load for the mission beginning, and all other script calls I set to triggered "once" after some short delay like 3-5 seconds. If I have higher number of scripts, then I plan execution in sequence for up to 10 seconds.

I am trying as much as possible to stay within the scripts also when it comes to checking the flags, as this have also to be scheduled and I can set the frequency other than one second, but usualy, instead of flags I am using just variables, as in vast majority of situations I am not using the internal triggering.

If You'd look into my mission I've attached, You'd have answer for all Your above questions.

I know that starting the scripting may be confusing and there's so many possible ways to mess up the solution, but by asking in forum then trials and errors sooner or later You'll get a grip over it.

[PSYKOnz]

Im Just going to put it out there that I’m really happy with my way of doing it, it’s simple as,

 

ive built it into a few of my missions and it work great.

 

found that the a 7nm racetrack is the perfect size for my way of doing it, so if you follow along what in mission file I uploaded and just use a 7nm racetrack it works awesome, no script needed, just waypoints, trigger areas and triggers.