ChillNG

HI thanks, I'm glads you're enjoying and thanks for the feedback! IIRC the intention was for you to backtrack up the runway, just an omission in the comms.

+ Note - in response to several requests colored dot labels are now available in the campaign.

Alpha and Bravo are your approach routes, nothing to do with the pattern, just arrive at whichever is specified and at the altitude instructed. You'll then be moved from Alpha/Bravo to the pattern. The pattern is for holding overhead until the runway is available (there's usually stuff happening below, you just might not have seen it) I've never found it too tight, fly 5 miles parallel with runway on down/up wind then make a turn to the opposite leg, you don't have to be directly over the base to do so, just make sure you're offset (north or south is fine) from Ruwaished if below 7500 feet. If above 7500 feet you don't need to worry and you can be less precise. Once cleared to exit the pattern and contact tower, break out the pattern however you wish and land as you see fit. I try not to dictate the exact landing method as some like doing OH break, some like going straight in. I normally extend back towards Alpha/Bravo as I descend then turn back in for a straight in landing.

Thanks very much, great to hear you enjoyed!

Shouldn't make any difference that it's in a mission, the CDU is the CDU, that's not something we can change through the mission making process. Is it an issue you're having with changing the info already in the CDU maybe, assuming on a free flight mission there's no waypoints in there already?

These coordinates are provided in MGRS (also called UTM) format, the Harrier will let you input them as a waypoint, you just need to change the format on the ODU. I'm a little hazy on the steps involved but this video shows you how at around 7:45 ish

Thanks for the feedback and glad to hear you enjoyed the campaign!

Hi, thanks for the thoughts! You are correct, the choice of FOB Juliet + FOBS later in the campaign prevent the AI using them for takeoff/landings - just no way the AI Harrier can handle them unfortunately. And Datalink with JTACs is again a DCS limitation, which is a shame. Both choices were compromises, but I think more is gained then lost in both cases.

Thank you!

It's designed for use of the ADF function to home in on the radio signal, my A-10 knowledge is extremely hazy so I can't give you a how to but I'm sure the internet will be able to assist - just search for ADF.

Thanks very much!

Campaign updates 16/11/23 DCS: A-10C Operation Persian Freedom Campaign by Ground Pounder Sims All missions - added new data link settings. Mission 5 - Fixed - Mono crashing as you land at Al Minhad. Mission 6 - Fixed - Davy engaging SAMs uncommanded. Mission 7 - Fixed - Striker doesn't fire HARMs. DCS: F/A-18C Operation Cerberus North Campaign All missions - added new data link settings. DCS: F-16C First in Weasels Over Syria Campaign by Ground Pounder Sims All missions - added new data link settings, unlocked coloured dot labels. Mission 3 - Rare possibility for player to break comms by missing a step in start up - fixed Mission 7 - Amended kneeboard error

To be honest there's a bit of randomization at play so there's not always a 'set' way to approach these missions.

Hi thanks for all the feedback, option to have coloured dot labels has been added for next update. Regarding HDD, actual mission memory size is pretty small, around 25mb IIRC, but as all these missions are quite big and complex I think you're system specs are causing you a few issues, although you're within the minimum RAM requirements for DCS, the recommended specs are really where you need to be for good performance, think most users would say 32GB is the ideal starting point these days, DCS likes lots of RAM. Couldn't work out from what you said if you were on a HDD or SSD, but again recommended specs is SSD and if you are on a HDD think that will give you very slow loading times. Would always recommend multi thread version as well if you can get it working ok, again these are big, complex missions with a lot going on so every bit of extra performance you can squeeze out will be beneficial.

Thanks for the detailed review!

Just to update you all... Darkstar comms issues were caused by radio updates to the A-10 causing the AM preset to change to FM. Whiplash comms - radio was working fine, but for some reason the signal from the units broadcasting was very weak so wasn't getting picked up. Fixed by moving the unit closer. Please let me know if you come across any more missions with issues from the update. Fixes will probably land in the December update now.

Yeah that's just an annoying AI quirk, they're all set correctly in the editor but never quite fly at the assigned altitude.

Thanks so much for the detailed feedback, really appreciate it!

Thanks, appreciated!

Most likely your SPI is still set to wherever you (presumably) boresighted your mavs, 2.9 introduced new SPI/SOI logic. Go back onto TGP/WEP and TMS down a few times to clear it.

Brilliant, glad you got to the bottom of it. Thanks for the info!

Thanks very much! Great to hear you enjoyed.

The campaign is fairly heavy in performance demand as it's very detailed, but having said that it sounds like you're having a bigger impact than most, most issues I'm aware of (pre multi threading) were in VR. Few things worth mentioning to check and be aware of. Incirlik, especially the shelters, are not a great area for performance...that's just a Syria map thing. Once away from the base things settle down a lot more. Hopefully you're running the multi threading version, if not I would advise to do so as the high unit counts in the campaign benefit from this. If you use TACVIEW then try disabling it, TACVIEW takes CPU resources and this is made worse with the amount of things it has to track in the campaign. Finally if you have any Win-wing devices then disable the scripts they use in DCS as these are real performance hogs.

You can align once airborne without any issues, I'm currently doing it once at cruise altitude and on the way to the mission area.