Nix Mills

Thanks. And no, the intent was to have the carrier on an ideal course for recovery up against the wind. Are you experiencing this in all missions or in a particular one?

All, I feel your frustration. It is however not a campaign mission bug, as we don't have any control over weapons effects and delivery. I am not aware of any DCS bugs related to the accuracy of JDAMs and LGBs for either player or wingman. If you're experiencing this across different types of missions, it might be a related to unlicensed mods installed. See General Advice in this post: If you're not already a super user on JDAMs and LGBs, check out the Tips and Tricks post here: Here are a few more points to the latter: - if you're targeting a tank or a moving target, use laser guided bombs (LGB) because you need it to hit perfectly (JDAMs might hit right next to the target, which is real enough, however IRL that would have damaged an old T-55 beyond repair) - for LGBs and JDAMs (in TOO) mode, make sure you have assigned/locked the target on your ATFLIR in A/G mode - for LGBs and JDAMs make sure EFUZ is set to INST (otherwise dud) and make sure delivery method is set to AUTO (not CCIP) - for LGBs make sure right panel switches are set: LTD/R up to ARM and LST/NFLR up to ON (we've all forgotten this at least once) - for LGBs make sure ATFLIR is set with the correct laser code - it's default is 1688 (training mode), but your LGBs are looking for a laze on 1711 - for LGBs make sure you are also lazing the target - either automatically by having boxed 'TRIGGER' on the ATFLIR screen ahead of release, or manually with your gun trigger - LGBs must be dropped with your crosshairs aligned when the countdown reaches zero - JDAMs must be dropped when you're IN ZONE and on an approximate heading to target Most of these things are also mentioned in your fence in checklists. Good luck and never give up

Yes, you're right. Little errors snuck in as things got changed and a few spots were missed despite all the proofing and testing. Following departure, you will of course arc right towards the coast and your first waypoint. As for Marshal stack upon returning, Mother will always order you to orbit at 3,000 ft to stay clear of the other flight(s) that are already recovering (IRL they'd fill up the stack starting at 2,000ft). Neither of these would affect your score, though. And yes, please don't microwave the tanker crew.

The channel switching is a bit tricky there because you had to monitor Israeli and Jordanian airspace controllers also. If you switch AUX back to channel 1 (305AM), you can order wingman to tanker. To communicate with tanker (request rejoin), call Shell on channel 19 on PRI. When you're done refueling, switch back to channel 7 on PRI so that you can monitor Image and keep AUX on channel 1 so that you can communicate with wingman.

The sweet spot to avoid wingman AI bugs is a mile or two behind the tanker at a about same altitude and heading. You need to use normal wingman commands on COMM 2 (F1 Flight or F2 Wingman --> F3 Go To --> F3 Fly to Tanker). Wingman then responds "2, Roger". If not, check that you calling on COMM 2, not COMM 1.

Try now

Thanks for reporting this. Had a similar report on Discord. For the update that just came out today, I see that I made a mistake in updating M14 in an attempt to delay start up, taxi and departure of 307 and 309 a bit. Do this (just go with it): When you taxi out to the catapults and facing down the carrier deck (heading between 210 and 220, or so). Pull the hand brake, then release it again. 307 and 309 should now have pilots and be starting up.

Investigating. We’ve not had this issue before.

Located 15nm east of Bastion. The common spelling in English of this town is "Gereshk", which is also what the map shows. However, in Sat/Alt view, it has been spelled "Girishk". Absolutely love this map. It is so beautiful and real.

I know. I'm waiting also. The updates were submitted a month ago.

I think the default gun settings are fine, as long as you're in A/G mode and CCIP mode. Try to also make sure to have my radar altimeter on (ALT switch down to RDR), set your minimum altitude (e.g. to 500ft) and then select the HUD with Sensor Control Switch 'up' - the switch on your stick that you also use for selecting left, right and bottom DDIs. From what I understand, this enables your gun sight to accurately calculate distance to target and elevation, and all you need to do is point straight at the target and fire. Do however make sure to come in on a ~30 degree angle - too low makes it difficult to hit the target, too high makes it difficult to pull up in time. Let me know how you go.

I don't think you're dealing with a mission bug here. Your task is to scan the ROZ from WP5 all the way up to WP6, and back. You will of course pick up a lot of ground moving targets around the al-Walid border post - this is where all the legitimate civilian traffic is crossing the border. Your wingman is kinda telling you that. The APC patrolling the south side of the border post is an Iraqi Army M113, which is a friendly. So continue up to WP6 and scan for anything that might be trying to cross the Iraqi-Syrian border away from any checkpoints. For inspiration, you can also search YouTube. There are some that have already made full recordings of them completing each mission. While their playthroughs may not be flawless, at least they'll give you an idea to where it is you got stuck.

I haven’t quite figured this out yet but you should be able to just ignore the DTC page and the mission will override it anyways.

Not at all. You had a perfect score there but the points for destroying the truck park weren’t being added in the backend. That has been fixed and will be part of the next patch.

No worries. Wingman is not a part of your score. It was originally but because of too many issues with AI wingman reliability we took it out. Will make sure to remove or replace the mission fail message. For a perfect score in M03, do correct departure procedure, follow corridors and do check ins, destroy all four planned targets (own and wingman) and destroy full truck column, and recover back on carrier. If you can send me or post a screenshot of your debriefing (the one you get with F10 before exiting mission), I can have a look.

There is actually a failsafe on each target and maybe it is related. Unfortunately I’m traveling atm but will have a look end of month. Stand by.

I’ll do my best to respond as you’re raising a couple of different questions. So during Case 3 departures, each aircraft will make calls to let everyone know where they’re at. Departure itself will only call or respond if they need to intervene for safety reasons. As you know, the KC-135 has a race track orbit in one leg of the transit corridor. Its altitude is between the altitudes assigned to traffic in either direction. If you’re heading east, you simply pop up to FL250, and if you’re heading west, you just come down. You then return to assigned altitude once done. This is also explained in the campaign guide. The targets assigned to you are the truck park and the fuel tanks, one GBU-32 each. I’m not sure why or whether your fuel tanks target would be destroyed before impact. The column of trucks trying to escape comes from the facility about 1km south of your target. As the UAV on station there is engaging with a Hellfire first you can look for the smoke from the burning AAA truck. I think there are five trucks for you to take out with guns, but you can call it off before that. There are a couple of YouTube videos up already with this mission. You could have a look and see how they are working their targets.

Hi A. The freeze is because it is removing/destroying map objects and spawn groups in your target. We have spread these out so as not to cause a major freeze (or crash) at the beginning of the mission.

As mentioned by pete-auau and Kurnass1977 above, make sure you're calling wingman on COMMS 2 (AUX). Assuming you are using the radio switch on a HOTAS throttle, you can activate the radio menu either with switch up (COMMS 1) or switch down (COMMS 2) - otherwise check your key bindings. You can also order wingman attacks using the F10 radio menu options (here it doesn't matter whether you're using 1 or 2, as it'll automatically call wingman on 2). For more about radio options, have a look in the included campaign guide. You can find it in this path: (your drive or Steam folder)... \DCS World\Mods\campaigns\FA-18C The Rampagers\Doc Hope that helps - otherwise let us know.

Not at all a stupid question. This has been updated now, should be included with the next patch. Thank you for noticing and reporting. In 2016, these two squadrons (VFA-25 and VFA-143) had Super Hornets, so the liveries for these are not meant to draw attention.

Unfortunately these issues with AIs not connecting to the refueling drogue as well as the radio menu with carrier approach options appearing are not related to this campaign, but are core DCS bugs. I occasionally encounter them myself in any given mission, not just these ones. The other day I created a simple mission for video footage with two Hornets refueling at a KC-135. During the first run, they connected and refueled. I made a few adjustments to fuel levels so that it wouldn't take as long, and ran it again twice - first time they were hanging above the drogues, second time below, for no apparent reason. If you have trouble refueling your wingman in The Rampagers,

Thanks. I've moved WP1 giving it 5 min more, which will come out in the next patch. A little trick here, though. If you are spinning up your navigation instruments (GPS) all the way, it takes 8 minutes or so. So do this instead: - Set INS switch to CV - When your middle DDI screen comes on, press to box STD HDG at the bottom in the HSI screen - Continue your other start-up procedures - When the CV calibration timer has passed 1 min and 30 sec, it'll say OK - Set INS to NAV or IFA

Sure. There was another tiny issue that I've fixed which was that if during departure you are speeding above 300 kts, climbing above 500ft (CASE I only) or heading off in the wrong direction, it would be noted against airspace controls instead of departure procedure. So if you did one of those here, it would say "Issues recorded with airspace controls". Other issues include flying outside corridors without AWACS clearance or flying at the wrong altitudes in corridors. "General communications procedures followed" is good - it means you did all or most of the necessary checks ins/outs. "Compliant with Rules of Engagement" is also good, because if (for example) you started engaging targets without clearance, you would not have received the mission scores from those ones.

Ah thanks, I was gonna ask if you could give me that. I have found the mistake now. There was a manual error in the conditions that activate the 10 point score for destroying the truck park. I have fixed this now so that it can get out with the next patch. Really appreciate you taking the time to report this - you made it very easy to find and fix the issue.

If you had another AI Hornet overtake you during a CASE 3 approach, it may have been because you didn’t start at the time you were given by Tower. As for your wingman, don’t order it to RTB during carrier recovery. If it’s a CASE I you only need to use “kiss off” before entering the break. If it’s CASE III just let it do its thing, it’ll start its approach after you have trapped and sometimes it’ll just hang in the marshal stack until you end the mission (I think it’s a bit bugged).