CVN operations - Githubissues

Gabykhan commented 6 months ago

As a requirement for CVN operations, I would say:

Mandatory:

Average distance from main operation airfield without hampering with its airspace (60-80Nm?)
Recovery tanker during departure/recovery operations
Cyclic ops

Important:

Ability to order the beginning of a new recovery cycle

Nice to have:

Ability to select cyclic ops lenght: 01h00 / 01h15 / 01h30 / 01h45

132ndArtur commented 3 months ago

Agree to above with:

Cyclic ops 25min as standard
Ability to order the beginning of a new recovery cycle <- this can cause issues if we have two separate flights, packages and their departure time will be forced individually causing confusion.
Ability to select cyclic ops length: 01h00 / 01h15 / 01h30 / 01h45 Right now we have optional "Training cycle" 01h30 length. Would be nice to have those options

132nd-Entropy commented 3 months ago

Happy to work on this and implement all suggestions

here are some variables that are in the script, please comment here if you want to see any of them changed:

Carriername (GROUP NAME IN ME) = CVN-73

RecoveryStartatMinute = 20 -- Minute at every hour when recovery starts RecoveryDuration = 25 -- Time in Minutes for Recovery Window to stay open ActivateICLS(13, "C73") ActivateTACAN(13, "X", "C73", true)

right now, we can manually start a cycle if the carrier is currently not recovering, the manually added cycle window will be one hour.

Thats basically how it is implemented in the ATRM.

Do we have really a benefit if we add the option to manually start a cycle that lasts 1 hour, or 1h15, or 01h30 or 01h45

I can put that in, but would a manually added 1 hour cycle not be enough?

(happy eitehr way, just making sure)

132nd-Entropy commented 3 months ago

also, recoverytanker is a must, ofc, like in the ATRM. do people want the rescuehelo that hovers next to the boat during active recovery? its a cool feature to have, but ofc not really needed,

132ndEvo commented 3 months ago

I agree with what you said Entropy. The manually added 1 hour should be good enough. I do have one request can we have an option in the F10 menu to select CASE 1 or CASE 2? For CASE 1 we can have 25 min recovery cycles and for CASE 2 we can have 40 min recovery cycles. Thanks

132nd-Entropy commented 3 months ago

Sure ! Also shall we do it as jonde suggested on discord and automatically end the manual cycle when a normal cycle would start ?

132ndNeck commented 2 months ago

also, recoverytanker is a must, ofc, like in the ATRM. do people want the rescuehelo that hovers next to the boat during active recovery? its a cool feature to have, but ofc not really needed,

I know this might be a stretch, and hard to code or even implement, but... Would it be possible to script the AI so the tanker launches 5 min prior to cycle start (Carrier need to turn an be ready to launch), and then have the tanker again land as the latest AC in the cycle? Ideally the recovery tanker would not show up mid-air, but I understand it might be hard to implement a AI activity on deck at the same time as human activity is taking place.

Regarding the rescue helo, it is not very realistic as it is implemented right now. They rarely fly as close to the CVN during the actual cycle. So I would suggest to remove it all together, as they are not that visible as you fly the pattern for real (If it is only for show. If it serves a purpose, then it ofc should be included and not left out).

132ndNeck commented 2 months ago

Also, a second request for the CVN: Can you script it so that the carrier turns opposite direction of the launch/recovery course outside cycles? In theory, where the carrier start on a 12 hour day of flying, it is at the same location when it ends.

132nd-Entropy commented 2 months ago

sure !

132nd-Thatch commented 2 months ago

ILS is set to 1 instead of 13 TCN is 73 as there is no confliction with PG map

132ndNeck commented 2 months ago

Also see #33

132ndNeck commented 2 months ago

ILS is set to 1 instead of 13 TCN is 73 as there is no confliction with PG map

The carrier in the .miz is not yet setup. It is there just as a placeholder for now.

132nd-Entropy commented 2 months ago

Also, a second request for the CVN: Can you script it so that the carrier turns opposite direction of the launch/recovery course outside cycles? In theory, where the carrier start on a 12 hour day of flying, it is at the same location when it ends.

I tried this and it's not as easy as I had thought. What is easy is to have a U-turn function enabled. That means that after a cycle ends, teh carrier turns around 180° and sails to the point where it was before the recovery started. This is then more or less what you suggested I think.

132ndNeck commented 2 months ago

Also, a second request for the CVN: Can you script it so that the carrier turns opposite direction of the launch/recovery course outside cycles? In theory, where the carrier start on a 12 hour day of flying, it is at the same location when it ends.

I tried this and it's not as easy as I had thought. What is easy is to have a U-turn function enabled. That means that after a cycle ends, teh carrier turns around 180° and sails to the point where it was before the recovery started. This is then more or less what you suggested I think.

Yes, that is perfect!

jonde99 commented 2 months ago

The biggest issue with a manual trigger recovery window is that is messes up others that are expecting the standard window. Therefore I suggest the following:

Allow window extend from now until next close.
always announce close with 5 minute warning.
Allow retrigger inside :50-:55 to skip close to next event.

jonde99 commented 2 months ago

LSO and BOSS slots should be enabled on the carriers. Although allowing airmen to steer the ship could be dangerous :)

jonde99 commented 2 months ago

ecoveryStartatMinute = 20 -- Minute at every hour when recovery starts RecoveryDuration = 25 -- Time in Minutes for Recovery Window to stay open ActivateICLS(13, "C73") ActivateTACAN(13, "X", "C73", true)

activate ACLS as well.

132nd-Thatch commented 2 months ago

Have the darker deck selected in the ME.
Do some testing for static aircraft and airfield 'furniture' to see if this effects fps as the carrier is very sterile. Have a plane guard ship nearby as well have the Carrier Strike Group showing.

MatteoN74 commented 2 months ago

Not .miz related, but...

In general, CV ops are good as they are (all of the comments above are good as well)
We need a bit more clarity on when to use different 309.XXX frequencies, sometimes it is confusing
All CASE I should be ziplip, also in training, unless requested (use a codeword?)

132nd-Entropy commented 2 months ago

I suggest to post this on the CV ops discord channel this is not so much for SOP discussion but for building the mission file (see carrier SOP doc for procedures, there comms, frequencies and what to say and not to say is stated) :)

132ndEvo commented 2 months ago

Great point. I’ll make a post about this.

132nd-Entropy commented 2 months ago

ok the first (very very basic and rudimentary) version is implemented.

Carrier freq, TACAN, ILCS etc all set via script
Same for recovery tanker
carrier will open a 35 min cycle at min 20
when the carrier is recovering, at any time can a 5 min extension of the present cycle be ordered
carrier status gives information about cycle start, end, BRC, current heading (so you see if its turning) and FB.
Tanker will take off first and (hopefully) land last

132nd-Entropy commented 1 month ago

Have the darker deck selected in the ME. Do some testing for static aircraft and airfield 'furniture' to see if this effects fps as the carrier is very sterile. Have a plane guard ship nearby as well have the Carrier Strike Group showing.

I cant select any paintjob in the ME other than 'default' how do you get the darker deck, is that a mod ? if so, we'd need to add it to OVGME? statics and other ships could have a perf impact I suggest we leave those for now until we know the mission is ok

132nd-vWing / TRMA

CVN operations #7