feefifofum

The AI will crank and perform defensive maneuvers in a BVR environment. After a merge they will attempt to force a 1 circle or 2 circle fight depending on the aircraft they are flying and their skill level. They are susceptible to G-forces and can GLOC and crash. Most of the other behavior is configurable. You can set them to bug out when they run out of A-A ordnance or at a certain fuel level, set paramaters for their radar usage, limit their engagement and/or weapon launch ranges, etc. They do, however, use a simplified flight model vs. the player aircraft which is sometimes more apparent than others. For the most part, however, it is a solid experience especially with recent AI updates.

Enjoy! Tips for mission 2 -

Hi Odessa! The campaign should progress as soon as you are cleared to RTB, regardless of whether or not you go home and land. You should be rewarded with a higher score for a successful landing, and some times other factors in more dynamic/complex missions...did you use the F10. radio option to request to divert to Kutaisi? If you don't specifically ask, I believe the logic of the landing trigger is looking for your aircraft at Vaziani. Regardless, however, the campaign should still progress to the next mission. Let us know if you continue to experience issues!

Thanks for the heads up! I'll get a fix together ASAP. Rassum frassum AI pathing....

Under "conditions" you will find "TIME MORE." The value is set in seconds. I.E. if you want your fireworks to happen 30 minutes into the mission- 1 ONCE (Fireworks, NO EVENT) -> TIME MORE (1800) -> *your fireworks plan*

You may be shocked to learn that "SAP" is an acronym with extensive use across multiple industries. As is usually the case, one can determine the meaning from the context. Pretty apparent we're not talking about financial software here, on the WinWing controls subforum of a flight simulator board.

Understood. The issue then is likely the MiGs crashed before they could be "scored" as kills. I'll see if I can whip those guys into shape, staying on top of the AI is a constant battle If you happen to have a track or an .ACMI of the prior attempt where the Foxhounds crashed, I'd love to take a look.

Hi trevo - Indeed your wingman is not quite smart enough to land in formation with you. The best option, as draconus suggests, is to tell him to RTB using the radio menu as you begin your approach. It should also be noted that all victory/scoring and almost all dialogue triggers for this campaign are looking for the player aircraft's position; there is never any need to wait for your wingman to land. Enjoy the rest of the campaign!

Hello суховей! The "RTB" message is considered "mission success" as far as the scoring is concerned. I will double check the text message again however. In order to score 100% (perfect score) the player must shoot down all eight red helos as well as the pair of MiG-31s, if memory serves. The campaign should progress with any score higher than 50%.

The engines must be running to power the hydraulic system. Prior to engine start, you can expect caution and advisory items for pretty much every airframe. In FC3, these should clear automatically after engine start. In full fidelity systems models, you will typically need to reset the system.

I have submitted multiple requests. Apologies for the delay, I'm not sure why this keeps getting missed in the shuffle.

Here is an official explanation of what each of the types of flight and systems modeling means -

Give this a whirl - https://www.digitalcombatsimulator.com/en/files/3304383/

LCTRL + F11 will transition to free camera from any other view, including the F10 map.

Acronym hell is real and generally airframe-specific. For general radio brevity, you can usually reference this- https://en.wikipedia.org/wiki/Multiservice_tactical_brevity_code

We'll be sure to include the .PDFs in the relevant subfolder for the next update, thanks for bringing it to our attention. This campaign pre-dates a lot of those standards, and little details like that can slip through the cracks.

Hi yongkh. the issue should be resolved now in Open Beta if you care to update! The stable release should see the corrected version shortly as well. Apologies for the delays, the file got lost in the shuffle a couple of times during the submission process.

You'll need to contact the tanker and call "intent to refuel" ; he'll lower the boom for you. Once you are close, call "ready pre-contact" he will either call "return pre-contact" (you must be within specific paramters to be cleared in) or "cleared contact" at which point you can approach the boom. Note that after disconnecting, you will need to press the nosewheel steering button to reset the refueling gate.

Dooley has it. I also recently enabled AWACS datalink across the campaign for the AC swapper crowd. Enjoy!

Unfortunately, no, the mission appears to have been lost in the shuffle. I have resubmitted it, apologies for the delays!

I made some proactive tweaks to the Fencers' flight plan that seems to have corrected the issue on my end; I also discovered a few other problematic behaviors in the process that have been corrected; the updated mission should be included with the next patch! EDIT: Unfortunately these fixes didn't make it into today's OB patch, but it should be in the next!

Two times in a row definitely doesn't inspire confidence...I will give this a go on my end this evening! Thank you for your diligence in reporting issues!

Thanks for the report. Hopefully this was a fluke (the AI can be extremely wonky at times) The ROE violation did come as a result of the Fencer crash, most likely; I don't want to spoil the rest of the mission by explaining what happens next but them dying early would be problematic. I'm going to give the mission a run myself when I am able, please let me know if this happens again on your end if you replay it. Should you experience the issue again, please try to send me a .TRK or .ACMI so I can see exactly what happened.

Hi TI, which mission is this referencing?

Long have we sought to manipulate the state of the AI's lighting....no such luck for now.