JGS

Hi Baltic Dragon, I just finished the campaign and wanted to thank you for an excellent job. I found it really interesting and immersive. Thanks, James

I just played this again on 2.9.3.51704. Killed the helicopters and made it all the way home. Last message was at 800 ft on approach. Landed. No messages after that. Parked where I thought we started from, ended the mission and failed the mission with 0.

I played this after playing the Basic and Advanced Flight Training campaigns as well as the excellent Iron Flag Part 1. Red flag is clearly an old campaign and doesn’t come with the kinds of bells & whistles that you might have become accustomed to, like custom ATC, or recorded banter with other characters. Note this campaign is for the A-10C, not the A-10CII. Apart from wind, weather effects (clouds/rain) are non-existent. Apart from a few basic recorded messages reporting thinks like SAMs being taken down, it is basically you and your AI wingmen, AI radio messages and the standard radio menu commands. The story is portrayed in the PDF mission documents, but unfortunately these are not integrated into the in-game knee boards, so you will need to print them out, or alt-tab out of the game (if you have a single monitor). Besides a couple of night missions and a downed pilot extraction, the missions are all pretty similar and involve destroying armor and artillery columns. The loadouts are typically Mavericks and CBU-97/105s. The surrounding AI flights do a good job at suppressing larger SAM systems and enemy aircraft, leaving you to concentrate on tank busting. After you take out any nearby mobile air defense systems, it’s like clubbing seals. Dealing with moving targets and the JTAC attack headings is the only challenge. After getting used to the basic nature of the campaign I still enjoyed it enough to complete it, and I didn't experience any game-breaking bugs that affect some of the fancier campaigns. If you can get it on sale and aren't expecting too much then it's certainly still playable.

I'm experiencing the same thing on the A-10C (I haven't tried II yet). I've noticed the flaps come down by themselves which doesn't help. After dropping the gear I end up plummeting to the ground, sometimes with the jet on its back (ejecting towards the ground). I created my own mission with left and right hydraulics failures, it wobbles a lot but I can land it. So it's something peculiar to the mission.

I've played Mission 3 The Raid twice. After rejoining with Lead following the attack he goes and lands at the nearest base in grid DV09. I carry onto the tanker, refuel and proceed to Incirlik. The last message I receive from Tower is to turn to heading 230, descend to 4000 and keep speed not above 350 knots. There are no further messages after this point (the first time I carried on until I was over the ocean). I have landed in either direction and parked at the usual spot but it does not register. TacView and track file links here https://drive.google.com/file/d/1Hn4OBBWLX6129LC7NNJxnP4ob793-WzU/view?usp=share_link https://drive.google.com/file/d/1-qLBFWwZtUZf5h09EW4VMkIoY0Ti6_7F/view?usp=share_link 2.8.4.39259.1 Open Beta

Come in fast and stay low after the show of force. Throttle to idle, get behind some trees. When the SAM call comes release flares and bank. Don't climb out until you are a few miles clear. My flare program is 2 flares, 0.5 s interval, repeat 5 times.

I can confirm this also. Open Beta 2.8.2.35759 Track file https://drive.google.com/file/d/1Ik-ptR_j7TSZjyRii88yGDnVtVJ_fek3/view?usp=sharing Log file: dcs.log floatingwands.mp4

tgpstby.trkI've noticed this too. Track file attached. TGP is in the open position, and doesn't move or close when selecting standby or switching power off to the pod.

Thanks IronMike. All good now.

Tomcats are not launching TALDs on Operation Reforger Mission 5. They turn back to the carrier at waypoint 3 and the Hornet SEAD flights do not engage. Tested 3 times. Tacview file attached. DCS-F-14B_Campaign_Mission5_SC.zip.acmi

Cage the Bear seems to be fixed for me now. I finished the campaign. Operation Reforger BARCAP (Mission 2) froze for me on two attempts just after completing the intercept of the first transport aircraft. I9, RTX3080 Ti, 64 GB RAM, Winging Super Taurus, Super Libra, Takeoff Panel, Thrustmaster rudder pedals, Track IR5.

Sorry! Wrong forum post. Was meant for the Cage the Bear Campaign. I've deleted the post.

Great campaign! Loved the detail put into the radio messages (takeoff checks etc). The final mission was fun. Textures and audio loaded quite slowly for me on mission start, so I usually didn't hear the briefing messages. But that's probably due to my hardware. My only critique would be that the environment sometimes felt quiet for a war situation, but on the other hand adding too many assets can have adverse effects on performance.

Great campaign thanks! I was a bit nervous about flying a primarily A-A jet (particularly with Fox 1's), but I found it quite manageable and learned a lot. Now I'm a bit sad that it's over. The characters were great. Would have loved the chance to use the M2000's runway busting BAP-100 munitions.

Mission 13 appears to be bugged in Open Beta 2.8.0.32235. The F-15 CAP flights do not depart from their holding patterns. Enemy F-4's end up engaging the Tornado flights, preventing them from destroying the SA-3 site. Tacview-20221117-222550-DCS-M2000 NTTR M13 trim.zip.acmi

Updated to 2.8 and it froze for me again on Cage the Bear campaign mission 6. I was about 40 nm from the carrier and it froze when I called ATC and received the response from mother. I avoided F2 views, but did use the map view throughout. GeForce GTX 1660 Ti, driver 462.31, i7-9750H 2.6 GHz, 16GB RAM

I can confirm I'm having freezes while playing Cage the Bear. Notably on missions 5 and 6, on my way back to the carrier after getting mission complete. Version 2.7.18.30765

It's freezing (not responding) for me while flying the Tomcat on Cage the Bear campaign missions 5 and 6. Annoyingly while flying back to the boat after completing the mission. Version 2.7.18.30765 Update: Have tried not using F2 or other external views but it still froze on mission 7. Log attached and a cropped tacview file in case it helps. GeForce GTX 1660 Ti, driver 462.31, i7-9750H 2.6 GHz, 16GB RAM dcs.log CTB CS5 crash cropped.acmi

Same for me. Helo's didn't finish their jobs so I went in anyway and continued the misison.

Ok, great. I just played mission 8 tonight and it went OK up until we had to regroup at waypoint 6. After that I didn't get a debrief or approach messages. So I'll move to another campaign in the meantime. Thanks, and appreciate your hard work.

Replayed the mission. The AI Blue flights still took off before my taxi time, but this time they formed up with me after I took off. The mission proceeded as planned after that. So perhaps the departure times of the blue flights need tweaking. Open Beta 2.7.17.29493

Flew mission 6, got to the part where the weapons engagement range and targets (F-4's, F-5's and F-14's) are assigned to AI friendly flights. However none of those enemy aircraft spawned. AWACS reported picture clear. A while later two low flying F-5's appeared and were successfully engaged. Nothing after that, until later when Sunray reported that all enemy flights had bugged out and we could RTB. Landed back at Nellis with a score of 80, so at least I can move on to the next mission. Might try it again tomorrow. I also noticed that Metal and Monster flights took off before my taxi time. Open Beta 2.7.17.29493

I just replayed the mission using today's update 2.7.11.22041 Open Beta, and it seemed to work fine. I couldn't defeat the Flankers though, so I just ran for home instead.

The first time I flew this today the mission seemed to work (unfortunately flankers shot me down). The tornadoes flew in a wedge formation. On replaying the mission the Tornadoes chase each other in a circle (i.e. they don't form up) and they don't continue onward to the tunnel after I down the MiG-31's.

Just played the campaign through. Great job. I hope the full campaign is still on the cards. To get Mission 5 to work I had to enter the Strike frequency manually.