Nix Mills

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).

We definitely love the idea and did also look into it. There were however are a couple of challenges. When you are in campaign mode, you don't get the option to launch a mission in multiplayer mode. You can only do this when running standalone missions in mission mode. Also, even if you attempt to run a mission from the campaign folder in mission mode, it will not run properly. To redesign the campaign missions so that they could accommodate two or more players would require a rework of most of the conditions, triggers and scripts. It would be a lot of work, but well, perhaps sometime later.

Check your kneeboard page 10 "Recovery Procedures" point 9. When you've been given 'Charlie' from tower, approach the carrier and fly over it at 800 ft / 350 kts. Your wingman will fly really tight with you now. When you're 1/2 to 1 mile ahead of the carrier, kiss off your wingman, then make your hard left turn pulling 3.5G initially. Your wingman will continue straight, then break into his left turn a bit further out. null

I checked the ship's log and it confirmed that the carrier did indeed make a hard port turn at 0646 hrs local time - so 16 minutes into your mission. The bridge have agreed to extend this a bit with the next update, although I did get some sass from the airboss who complained about camera crews, players and more holding up his launch window.

Yep, set ATFLIR to 1711. As for JDAMs missing target make sure to drop only when well inside the range window - max range often results in it falling short. Perhaps take a look at these two posts and see if any of it applies to your situation. https://forum.dcs.world/topic/371121-common-issues-and-solutions https://forum.dcs.world/topic/371252-a-few-tips-and-tricks

Thanks for reporting this. Odd, we’ve never had that happen before, carrier is not set to turn for quite a while. Will look into it. are you using STD HDG to align your GPS or taking the full 8 minutes to spin up?

Thanks for letting me know. Did the loop start by itself or when you requested fuel state?

Probably need a bit more information to figure out what's going on. Tank is not immortal and has been destroyed by others. If bombs are not exploding, check fuze settings (set to INST). If laser guided bomb is not hitting, check that you've lazing with your ATFLIR set to the correct code (1711). Hope some of this helps.

Thanks for all these reports, IceyJones. Sorry your mission got messed up by those things - this is quite an important one. We'll look into the second element crashing into the water. Not something we'd ever experienced before when testing. We'll update the instructions to make it a clearer who's doing what and the F10 options available. That's really important. The script issue is because your wingman was supposed to be talking to you here. The script is looking for the wingman unit to transmit a message but can't find it because it's dead. It's usually conditional on the wingman being alive but was missed in this particular script. We'll make sure to have that fixed for next patch.

Thanks for that. I'll update accordingly. Interesting project, I've looked up other things there before - we should chat later.

Thanks for letting me know, wuffer84. I'm not sure, it seems you somehow didn't get the radio option to call Magic on 255. Do you have any mods running in DCS that might have caused this? There is a video here of a mission 6 playthrough by another player. Try and watch and see if they are doing something differently: Let me know how you go.

Hi all Here are a few tips and tricks for those still learning the many intricate details of the instruments and weapons systems in the F/A-18C Hornet. DIFFICULTIES ENTERING CORRECT GRID COORDINATES Check that you've entered coordinates in the correct format - either six digit format, or ten digit format (PRECISE). Remember, target points given to you by JTAC can not be expected to be precise, but they'll usually be good enough for you to focus your sensors so that you can look in the right place. For example: Grid DA 1212 (this is a square kilometre box to look in). Convert to six digits: DA 120340 or, to look in the middle, DA 125345. Grid DA 12341234 (eight digits). Either convert to six digits: DA 123123, or box PRECISE and enter as ten digits: DA 1234012340. DIFFICULTIES HITTING TARGETS WITH LASER GUIDED BOMBS The laser code for laser guided bombs (like GBU-16, -12, -10) is set manually by the flight crew and cannot be changed in flight. Remember to set your ATFLIR to laze with the same code as your bomb is set to. If you are lazing a moving target, then it's usually best to attack from behind so that your bomb drops in the same direction as the target is moving. DIFFICULTIES USING GROUND RADAR AND ATFLIR TOGETHER When using the ground radar in Ground Moving Target (GMT) Mode, you can move your cursor on the radar screen and lock to a target (brick). Your ATFLIR will automatically lock to the same target. When switching to a new target, make sure to reset (undesignate - pinky button on stick) both you radar and your ATFLIR. ATFLIR often stays in the same place if, for example, you changed mode to look around and track a target with this. DIFFICULTIES GIVING ORDERS TO WINGMAN Wingman will respond to orders such as formation, engage ground targets, hold position, rejoin, go to tanker etc. However, you can only give orders on COMM2 (AUX) (usually 305.000). Make sure to activate the radio menu for COMM2 (throttle thumb switch down). TAKING TOO LONG TO START UP FROM CARRIER If you're waiting on your navigation instruments to spin up all the way to ready, this can take you more than 8 minutes. Instead, make sure to set your INS switch to CV. When your middle screen comes on, select and box STD HDG at the bottom of the HSI screen. The NAV (GPS) will now calibrate to the carrier and will reach OK after 1:30 min. Then set your INS switch to NAV or IFA. NOT SURE HOW TO SET DELAY FUZE ON GUIDED BOMB UNITS Try and follow these four steps on your DDI page for weapons settings:

Thank you so much for that, IceyJones. I have corrected the orbit reminder popup to say that you should be on 275.500 on COMM1. I have increased the trigger zone over Deir ez Zuir to a radius a little over 9 nm (it was 7 nm) and I removed a single insurgent in the town that could cause the AI wingman to return to attack that instead. We'll do our best to get this included next time they run a patch update. I'm impressed that you're up to M12 already.