Jasonmoofang

Just finished the mission and scored 80, which seemed odd. The scoring guide says its 40 points if player shoots down the helo, and 20 points if Tails does, but it seems when I played it, I was only instructed to strafe the front of the helo, and when Strike says to shoot it down, 1-3 told me to hold high while he went for the shot. He then shot down the helo. So it seems I wasn't supposed to shoot it down? Or did I mess up something else that triggered this chain of events? Had a great time regardless, but just curious!

Hey Sedlo! Following up from my comment on user files. I'm consistently getting crashes on mission 7 sometime around the actual bombing over Bandar Abbas. Redownloaded the latest files on latest DCS version and tried it again last night and sure enough it crashed as I'm pulling into the dive over the target. Attaching logs! Not sure what's going on dcs.log-20240901-182713.zip

For most missions contacting marshal means calling inbound to the usual DCS carrier ATC, so no F10 actions needed. There should probably be some helper text telling you to contact the regular DCS AI ATC as well.

Yeah I'm also hung on this mission. It's a known issue, there is a thread in the bugs subforum. Unfortunately ED hasn't fixed whatever's causing this, and BD I think is swamped with other stuff at the moment.

I just replayed this mission fully on latest OB and everything seemed to work. Did you get to the points where you need to lights on, and then to fire warning bursts?

I read through the other big thread on Mission 6 and decided to start a new thread since, at least for me, a lot of the issues there no longer applied. I survived the Tomcat issue on deck, had proper comms all the way through, and passed the mission fine. There were still a few non-breaking issues. It seems like tapes still don't count for final score if it is set to MAN, which is what I did, and I got 90. Also, the instructions for recovery were confusing: the kneeboard said to follow the regular DCS marshal instructions except ignore the push time and adopt Cajun's timing - 1, which in the briefing was listed as 39. However, in the mission, Cajun's push time was 44. Also, the DCS marshal instructed me to 23 DME Angels 8, but Irish also got assigned 23 DME Angels 8. I kind of put 2 and 2 together and figured that no one was assigned 21 DME Angels 6, and it would make sense for me to be there if I'm supposed to push 1 min before Cajun - so I completely ignored DCS marshal and did what made the most sense, but yeah that was confusing. Also, I suppose this is probably just DCS AI being DCS AI, but Cajun flew like a drunk UFO He'd slow down until almost falling off the sky, and then suddenly go full burner, which for AI seems to accelerate him way more than it does me, forcing a long chase. Hanging on his wing was a sweatbath! Just wanna say also that for all the issues, that was an amazing experience. The custom Case III comms are truly an immersion game changer.

Thanks. No problem at all if it's just DCS as usual, but I'm just worried that I'm not doing something right. Do I need to do anything other than turn on DL? If things were working correctly, what am I supposed to see and where?

How is Dolly/Datalink stuff supposed to work? The missions are doable with just call outs from Knight, but it's bugging me that nothing seemed to have happened with the Datalink.

I passed the mission fine because the primary target was like the 3rd ship I checked after freelancing, but how are you guys doing SSSC? I feel like I'm behind the curve on everything, and Olive pretty much did all the important callouts which was pretty embarassing (I never spotted the fast mover that was supposed to be with the primary). How are you guys keeping track of the piece of sea you're supposed to be searching and how are you scanning it? I tried keeping a 90 degree line from mother and then mentally imagine a 30 degree slice northwards, but everytime I lock something for the FLIR the line goes away. Just keeping track of the piece of sea I'm supposed to scan feels like a constant tussle. I feel like I lucked out being instructed to RTB after stopping the primary and don't have to continue the actual SSSC lol.

Additional feedback here as well: it seems that WP6 is not in fact the DMPI, and if this is intentional, then I'm wondering if it might be worth clarifying this in the brief. Since the DMPIs are precise pre-planned targets, and especially since we don't have good visual on the airfield coming in low, I assumed that the target waypoint would be on the DMPI for an Auto release, but I was pretty shocked to see a blank on my FLIR. I still received full score for releasing Auto on WP6, but that can't be right. Perhaps the intention is to manually visually acquire your target and hit it on CCIP? Or is WP6 placed incorrectly? If the former, I feel like a note on the briefing would be useful. Oh also I was surprised the ToT wasn't on the kneeboard, but that's just a minor inconvenience

I feel better reading this thread Just did this mission first try and it was certainly the most stressful DCS I've ever flown. Lost Cajun and the tanker in the goo and and hopped around like a headless chicken only to be told by Cajun to come off right as I was finally about to plug. I've flown plenty of Case III's and had my misses and (manual) go arounds, but this is the first time I've experienced being at the mercy of approach - while being able to see absolutely zilch in the goo and with the velocity vector hopping all over the place at the slightest touch. Brief said 2.9 bingo and I got sent off at 2.2 which stressed me out even more so I bungled the profile and went too high and wasted even more fuel. Came in for the landing at Cypress and was absolutely flabbergasted. I've done only a little crosswind landing practice before, and this is probably twice the degree of wind I practiced with. Gave up the first approach in utter shock, flew around, nervously eyeing the IFEI. Got tires on the runway with my nose probably 45 degrees off, couldn't rudder it under control, and did the donuting into the adjacent taxiway. Thank god there wasn't any obstacles or vehicles to run into. Jet seemed to have come off the ordeal mostly unscathed, meekly got back on the runway to exit at the other end. Found the little truck, cursed at Knight for making light of my hellish near death experience... and then, to my horror, after taxiing for a few minutes the engine died with about 100lbs of fuel left, leaving me dark and stranded on the taxiway. Thank god that still counted as a pass for the mission. I think I'd need some time to recover before attempting the whole thing again. Talk about night in the barrel! (also almost-grudging appreciation for the degree of detail and realism. Truly next level even compared to the original R1)

This isn't exactly a breaking bug since you can still complete the mission, but Sweeps and Trons orbit mother throughout most of the mission on mission 10, only pushing around the time I am recovering. I know this didn't used to happen - first time I played, during the ingress I could see Sweeps streaking above me in formation through NVG, and it was a pretty awesome experience. This has happened twice, both recent. Tacview of most recent attempt attached. Tacview-20230709-004033-DCS-R1 M10.zip.acmi

Finished the campaign last night. Just wow, what a massive upgrade from Eastern Friendship, which I already greatly enjoyed! Almost felt a little bad at the end when the campaign said "thank you for deciding to purchase". Did you ever set up something for us to be able to buy you a beer? Some more detailed feedback: Overall again thanks and congratulations on an excellent campaign. I shall definitely be reflying some of the missions!

I just replayed this mission couple days ago. Waypoint 2 is the IP not the target, that's waypoint 3. Which comms did you miss on aux? Iirc you'd start on channel 1 (tactical) and stay there until halfway through the mission where you'll switch channel 3 for your element. Seemed to work fine for me.

Much appreciated @baltic_dragon . Looking forward to flying the fixed versions in the next update