Rokkett

You can try this: F-14B Campaign | Operation Reforger - The Iron Heel (Super Carrier eddition) But it looks like it may have some bugs too, so you may have to play around in ME.

Same with AI F-14's - once tasked to refuel, they will not leave the tanker even if there is a stop command.

Having played around in the ME a bit, it seems, for this current version of DCS, successful AI F-14 tanking is a function of both the mass of the F-14 and its speed. A more heavily laden F-14 will require the tanker to be travelling faster for it to successfully plug the drogue. Finding this right speed is a bit of trial and error, which is annoying and time consuming. For reference, a heavy'ish F-14 at 20 000ft will need the tanker to be flying at least 360knots (as set in the ME).

I have the tanker speed set at 330knot at 20 000ft. IAS is around 260knots, which is about 480km/h. I'll try speeding the tanker up a bit more and see if there is any improvement.

Since the latest update, AI F-14s of both variants again are unable to place their refuelling probes within the S-3b tankers drogue, and so can never complete their refuelling evolution.

As of most recent patch, this seems to be happening again: F-14 AI refuelling probe not making proper contact with the drogue.

Yes, it seems this mission is bugged again. Try this fix: ReforgerII_m4_shock and awe.miz

So, I got WMR working again after following this Reddit thread of other WMR users also being affected by the recent Win10 KB5052077 update: Seems WMR becoming non-functional was an unintended outcome of the update. In my case, neither uninstalling the update nor doing a system restore, fixed WMR. I had to download and run the mediacreationtool as described in the reddit thread. This repairs/reverts to an earlier Win10 version. Then, when you run WMR, it updates itself, and, voila, works again. Make sure you prevent KB5052077 from installing itself again, or you may have to do it all over again (as I did!).

Sadly, I'm in the same boat as you. WMR was working fine yesterday. After performing a Win10 update (KB5052077), I now also get a WMR "couldn't be installed" and "needs an update" message. Tried uninstalling the Win10 update, as well as uninstalling and re-installing WMR and OpenX, all without success.

SA-10?

Simplest way is to ask Jester to set it up for you: Jester Menu -> Navigation -> TACAN -> Select Tanker Callsign In front cockpit, lower right PDCP panel, look for STEER CMD, and select TACAN button. HSD should now show direction and distance to selected tanker.

As far as I know, in these missions, registering of the landing is not itself a trigger required for mission completion. Did you do the carrier break at the field?

Yes, the mission favours returning to base via the tanker track, to intercept the landing trigger zones. If you RTB directly after engaging the MiGs, unfortunately the vector you get from ATC causes you to miss the landing trigger zones. Even if you do not want or need to AAR, I would still head out to the vicinity of the tanker before RTB, so that the vector you get at least puts you in the right ballpark for the landing triggers.

BFM being highly dynamic, yes, sometimes Jester's calls are a bit after the fact. However, the problem you are describing is that Jester thinks the ejected aircrew swinging under their parachutes are still threats/bandits, so continues to call them as such. I believe HB are aware of this, and a fix is still awaited.

For your first question, see here:

On my Winwing F16EX stick, I use the secondary trigger which you can flip up and flip down. Each position is a key press, so I flip down to engage NWS, flip up to disengage.

After you get the 800ft approach call, you need to do a left carrier break into the pattern to trigger the remaining triggers.

You left out the most important one: wing sweep - use bomb mode or a manual sweep angle of your choice to prevent the wings from auto-sweeping. This prevents pitching of the nose up and down that occurs with the variable sweep. Also, don't focus on the basket. I like to watch the refuelling pod, but people have different frames of reference to assist with lining up the basket and then maintaining contact.

If you're flying current DCS stable/open beta then, yes, you will have the most current mission files. All the triggers in R2M3 do work, BUT you do have to follow instructions closely. Also, the Hinds are difficult to locate - they spawn in around the new WP 1 that Jester creates for you, but it's dark and they fly low enough that you may not pick them up on radar. Purists may not like it, but "labels on" in this case will help give you a tally.

Are you playing the most up-to-date mission file, and if so, where exactly in the mission are you getting stuck?

Just re-flew Mission 4: Shock and Awe and it worked fine for me. After AAR, WP 3 was about 120 miles away. Upon arrival at WP 3, I received vectors to land at Incirlik for a Mission Complete.

You can use the Jester wheel to command Jester to give you control of either chaff or flares. This can be cumbersome to use in the heat of battle, but you can bind keys to the relevant command to make it easier. Personally, I use VoiceAttack with Bailey's profile, then you can just say: "Jester, give me chaff" or "Jester, give me flares" Works pretty well for me.

Hmm not sure what has happened to your mission file, but my mission file shows Lead 2 to also have (<current> -3) and (<current> -4) as per Rick_NSX. Also, the vector zones can be a bit tricky to find if your position is a bit off when you RTB, and may require you to hunt around a bit by flying around the base. You could try enlarging the vector zones if you are comfortable doing that in ME. Anyway, here is my copy of Reforger II Mission 3 if you like. ReforgerII_m3_the raid.miz

For those not comfortable playing around with the Mission Editor, Reforger II Mission 2 can be downloaded here... ReforgerII_m2_proportional response.miz

Thanks, IronMike! Have updated the Reforger II -Mission 5 file above to resolve a trigger clash that prevented Uzi group from forming up as briefed if the player taxied too soon at the start of the mission.