Tactical Turns - Flying with an AI Wingman.

[DCSFonzie]

hace 9 minutos, oz555 dijo:

Maintain speed throughout the turn at 3.5g- 4g. Usually up to full MIL power required until the turn opens out. I made a video a while back which roughly covers the procedure. I have skipped it to the relevant point. 

Thank you @oz555!

Nothing new under the sun and standard procedure then

[Cab]

12 hours ago, PeneCruz said:

It was added in the last vaicom update v3.0.0.0, see pages 63 and 64 of the Vaicom Pro maual.
At the moment it has the same commands as the DCS menu, and additional ones for Flow East, South, West etc. I will add US phraslogy in a future update. As it is only me coding I have only so much bandwidth to make additions.

It's been a while since I've had to fiddle around with VAICOM, but can't players create alias command phrases to use U.S. terminology for the tac turns?

Great job with VAICOM BTW.

[Avenger31]

I remember a time when this forum community was very helpful to us who encountered a certain problem that was not that common, and even when others did not have the same problem and could not reproduce it, they tried to help. Now certain issues simply go completely unnoticed and without any desire to help each other.

[draconus]

15 minutes ago, Avenger31 said:

I remember a time when this forum community was very helpful to us who encountered a certain problem that was not that common, and even when others did not have the same problem and could not reproduce it, they tried to help. Now certain issues simply go completely unnoticed and without any desire to help each other.

I can't agree with that. Maybe the aircraft and problem is very unpopular? Maybe it's some other language subforum? Maybe the poster had specific attitude? You can't know if it the issue was noticed since there is sometimes no feedback and there are no public bug trackers but we're assured devs read the posts.

[PeneCruz]

4 hours ago, Cab said:

It's been a while since I've had to fiddle around with VAICOM, but can't players create alias command phrases to use U.S. terminology for the tac turns?

Great job with VAICOM BTW.

Yes that’s correct, users can assign any alias they want to a keyword in the editor tab of Vaicom Pro. So you could add whatever branch/nations phraseology you want. O will add the US Airforce/Navy terms into the next release. 

[Smashy]

1 hour ago, Avenger31 said:

I remember a time when this forum community was very helpful to us who encountered a certain problem that was not that common, and even when others did not have the same problem and could not reproduce it, they tried to help. Now certain issues simply go completely unnoticed and without any desire to help each other.

It's a two-way street.  The forum is still a useful resource provided you make the effort to post questions with clarity and provide as much detail as you can.

[Sn8ke]

This latest OB update did not implement this cool new feature. Did you guys forget to add it in?

[Sn8ke]

18 hours ago, cesarferrolho said:

Same here!!

I have no mods installed except Tacview, and flying lead on a 2 ship. And i can see other (Very good) changes like the corrections to the S-3B Tanker.

Same! This was not implemented on my DCS

[bephanten]

hotfix loading...

[NineLine]

Sorry all there was some confusion on this one and its only available for the F/A-18C right now, coming soon for the F-16 and more after. Thanks!

[Dragan]

I think there is a problem with the wing AI with this latest update, everyone can check it themselves, specifically I mean the commands echelon right and echelon left when we are flying only in pairs. My wing AI now does not respect altitude, he is very low below me, for example: the set flight altitude is 19,000 feet, he is at least 2,000 feet below me, I gave him the command echelon right he executed echelon left, when I called him for echelon left then he just went right, he mixed sides. I also think it would be good to change the voices of the AI pilots as well as the voice of the leader after many years, there were no new voices like we have, a refresh would be nice.. Big regards 

[oz555]

The AI also does not remain in correct battle formation following a left Tac-Turn that it has initiated. It returns to line abreast right regardless once the manoeuvre has been completed. 

The radio menu seems to be populated with numerous commands that either don’t work or conflict with each other.  

Perhaps the new Tac feature would  be better suited to an entirely separate menu. 

[KoleTang]

I agree the radio menus are way too long.  If mapped to HOTAS, scrolling down 9-10 times is not effective and frustrating. 

[SDsc0rch]

need to be accessible via single keybind

[oz555]

With further testing, I have found much of the process to be automated. The AI will perform a Tac-Turn by itself, provided the lead (player) is on the outside before the turn. If the AI is on the outside, the Small Tac-Turn commands in the radio menu must be used. Unfortunately this currently introduces problems with the formation as mentioned earlier in this thread.

I have created a runway start .miz out of Kutaisi (attached) with a Tac-Turn practice flight plan if anyone is interested. If you follow the instructions, the lead aircraft will always be on the outside running into the 45 and 90 turns, so you won't need to use the radio menu or interact with the AI other than the initial line abreast setup following take-off and a couple of shackles to regain the outside line.

On the runway:

Select the SA page. Box WYPT and SEQ1 with a range scale of 5nm.

Turn on DL (127).

Switch Rad Alt.

Rad Alt set to 150ft.

Select WP1.

Brakes on, throttles to 80%. Release brakes and slowly advance to full burner, then back off 5% so Wingman can keep up.

Following gear up - Accelerate to 420kts@250ft. Open Comm 1 radio menu - Flight/Formation/Line Abreast, then Large Tac Turn Menu/close up x3 to get our AI in Battle Formation@1nm on the right.

Continue at 420kts, left of track with your wingtip symbology touching the track line on the SA page@5nm scale.

At 1.5nm before WP1, select WP2 (or use AUTO) as you proceed with the first 90° right turn, pulling a level 3.5-4g throughout and using up to full mil power (or use ATC) to maintain 420kts. Your AI wingman will perform his Tac-Turn automatically and you should both exit the turn on the opposite side of the track to the ingress. If you've maintained the correct speed and G's, your wingtip on the SA page will be touching the track line again, and you should both be in a perfect 1nm line abreast.

Repeat for all turns up to and including WP10 with a Shackle (swap sides) - Radio Menu/Large Tac Turns/Shackle - between WP5 and WP6 and again between WP6 And WP7 - so lead can regain the outside line.

WP11 and WP12 are set up for your approach to land at Kutaisi R/W 25@WP13. 

Tac-Turn Practice.miz

[Dragan]

It has definitely become problematic flying in pairs where my wingman does not respect the heights for echelon right and echelon left formations, he usually flies 2000 to 3000 feet below me after issuing the command, finally matching my altitude as leader after a long time, anyone interested can check this, I think this worked normally until the last update.All the other formations we have in the radio menu for the A-10 I specifically fly with it function as before.It definitely became problematic for the pair to fly the wingman in the echelons to the right and left due to the late connection to the leader's altitude.This is all very easy to check.Thanks

[Dragan]

I don't know if it can be seen like this, here is my entire mission in the Caucasus, where there is clear evidence that the AI wingman does not respect the heights for the echelons left and right on my commands, only after a long time of flying below me does it start to align with me at the same height...

Data entry before the start of the mission was echelon left.Later, after the mission was completed and I returned to the airbase, my radio commands went out to the aforementioned disputed echelons.Here is also another in a series of crashes of Mirage F-1Bs flown in pairs, this has also been disputed since the last update, last night in one of the missions both crashed and did not even reach the target area.

LastMissionTrack.trk

Edited March 3 by Dragan