Jump to content

Cancel cover command...?


Recommended Posts

Posted

I have La5s covering IL2s, after they have completed their ground attack and move on to next couple of way points back to airfield(IL2s that is), how do I get the La5s to break covering them?

 

I assume it would involve a "force complete" and a "Trigger counter" and a "timer" and "command cover" set up to disable it, or am I way off?

 

Also!... Having trouble with some planes not wanting to land and just circle the final waypoint, anyone else having the same trouble?, same set up for other aircraft on same mission and they will land, is it a bug with some Airfields...any tips?....extra commands or add event or add report commands that I can add to force it to land?

 

Any help greatly appreciated.

 

 

 

 

capture_001_21122021_214253.jpg

Posted (edited)


Correct Monty using a Force Complete (High) will cancel out the CMD: Cover.

Any Event can trigger this logic stream or perhaps use the last IL2 WP to cancel the original CMD: Cover.

 

Last IL2 Waypoint or Event
|
Timer (2s) --- FC (High) Target Linked to the La-5s
|
Timer (2s)
|
New La-5 Waypoint or other CMD: MCU Object Linked to the La-5s

 

As far as the Landings or lack thereof.
There are alot of factors which may prevent AI from landing. Here are a few.


1) Objects too close to Runway approach and along the Runway itself.
2) Airfield Object placed incorrectly if not setting up Taxiways, Take-offs and Landing Spots within its Properties
3) Airfield Object Runway not set up properly within its Properties if using Taxiways, Take-off and Landing spots.

4) Landing MCU incorrectly placed, targeted or activated.

 

IIRC JimTM posted a primer on the do's and don't of setting up the Airfields long ago.
*Perhaps submit the mission here so someone can take a look at the landing logic you've got set up.

 

Good Luck with you Mission design.
Tip

Edited by [DBS]Tx_Tip
Whups
  • Thanks 1
  • Upvote 2
Posted
8 minutes ago, [DBS]Tx_Tip said:


Correct Monty using a Force Complete (High) will cancel out the CMD: Cover.

Any Event can trigger this logic stream or perhaps use the last IL2 WP to cancel the original CMD: Cover.

 

Last IL2 Waypoint or Event
|
Timer (2s)
|
FC (High) Target Linked to the La-5s
|
Timer (2s)
|
New La-5 Waypoint or other CMD: MCU Object Linked to the La-5s

 

As far as the Landings or lack thereof.
There are alot of factors which may prevent AI from landing. Here are a few.


1) Objects too close to Runway approach and along the Runway itself.
2) Airfield Object placed incorrectly if not setting up Taxiways, Take-offs and Landing Spots within its Properties
3) Airfield Object Runway not set up properly within its Properties if using Taxiways, Take-off and Landing spots.

4) Landing MCU incorrectly placed, targeted or activated.

 

IIRC JimTM posted a primer on the do's and don't of setting up the Airfields long ago.
*Perhaps submit the mission here so someone can take a look at the landing logic you've got set up.

 

Good Luck with you Mission design.
Tip

 

I'm not sure that the timer in bold above is necessary because the last waypoint at the top is not triggering any other commands or waypoints that require the FC (high) to wait 2 seconds.

 

My "primer" on airfield logic is really just notes that I made while testing. Read the entire thread for any corrections and note that AI behaviour may have changed since I wrote the notes. Sorry, I have not been actively testing this stuff for a long time.

  • Thanks 1
Posted (edited)

Following @[DBS]Tx_Tip's here's a visual representation. In my logic, I have both the cover command and the attack area command set to High priority. So when I use the force complete, I set the priority to low. I'm not sure why that works, but it does. After the force complete, I have a 1 second timer, and then I tell the cover planes to go to X, and the attack planes to go to Y.

 

image.thumb.png.d199f9913087a677aa03bdf4b7bddf4c.png

The Attack Craft move to their target, attack the target, and once 2 of the four craft are out of bombs OR if the "just in case" timer ends, then the force complete fires. The Cover Planes and the Attack Craft receive the force complete, and then one second later the Attack Craft follow their egress waypoints, while the Cover Planes follow their egress waypoints.

 

 

--------------------------------

 

Regarding landing craft, you must make sure you have an Fakefield MCU, and that you setup the taxi/landing chart correctly for that field. The location of the fakefield MCU does not matter, but the taxi chart does. See image:

 

image.thumb.png.742fa52daf5b9d425f7a33bba598ddb9.png

Here we have the taxi/landing chart for Yantar Airfield. Now planes will land Eastward (as long as we place the cmdLand MCU correctly)

 

Here is a visual of what the logic looks like for making a plane land. Make sure you position and rotate the cmdLand at the same location and rotation as where the taxi/landing chart for that airfield starts.

image.thumb.png.629359d21c580caf62a4119d89a5ea05.png

Here we have four i16s, that follow an egress waypoint. Once they reach that waypoint, they'll attempt to land. Once two of the four planes land successfully, a subtitle message will appear saying "i16's have landed successfully!" The key is to have an fakefield chart for the airfield, and the cmdLand positioned and rotated the same way or the planes will not land correctly.

 

Here are the mission files to reverse engineer:

Example Ending Cover Command.zip

Example Landing Command.zip

Edited by Sketch
  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...