TerminallyIrish

This worked. Thanks. Was able to make the edits this time successfully; and the missions worked as intended! On to mission 3!

Anyway to redownload the Reforger II campaign? I was trying to edit Mission 2 as suggested, and must have messed something up. When I continue the campaign (on mission 2), I enter the mission in free camera mode, and NO units are present. Thanks!

Any word/plans to fix the Reforger II campaign? (Specifically, mission 2!)

Getting the same issues on mission 2 (playing MT.) Arrive on CAP station. Fulcrum V/O triggers, turn to directed heading, never see them. Return to CAP station. MiG21's show, Jester doesn't engage. Can't control radar to self-engage (Jester slews it all the way to the left and leaves it there.) Eventually fly southern CAP legs about a dozen times. Directed to hit tanker, but tanker TACAN disappears (reading through this, I'm guessing he landed.) Run out of gas about 30 miles from Base.

Trying to play this, and I splash the first Flankers. Get a call to go after a MiG, but another flight gets there and destroys them first. Then…nothing. Flew between WP 2 and 3 until I hit bingo fuel. Landed. No Mission Complete and only a score of 50. Reading about the issues from a few years ago, it looks like this missionp may just be borked (to be honest, this whole campaign has sort of had issues for me.)

@NineLine I think the non-functioning FLIR is pretty self evident at this point. Is DCS honestly trying to tell me a METAL vehicle sitting in an open field in the summer is not hotter than the surrounding grass!?!? I love DCS, and want it to be the best it can, it’s just the A/G role in so many airframes is just borked right now due to thermally camouflaged targets!

Flying this mission last night, and Blade would not engage bandits. He flew a route over the peninsula headed back to the carrier.

Was able to complete the mission, albeit with some slight work arounds (and knowing how the mission is supposed to act.). Steps I took to complete below <SPOILERS> Meet up with flights at WP1. After all 4 Ravens were up, lead called push. Flew formation with lead until call regarding bogies to intercept. This too awhile. I flew with lead to his target, and then returning to the boat. Intercepted and splashed bogies (be careful here, as it’s easy to stray into SAM coverage). Received call regarding radar targets from Harriers. Entered target coordinates as WP 8 in HSI. Designated WP 8 as target - its was NOT on a radar site, but I could see SAMS in the ATFLAIR pod just off of it. Used F10 comms menu to notify wingman I would attack target. JSOWS to TOO mode, designated what I thought was a radar, turned out to be a launcher, and pickled weapon. Shack. Radio call of missed target, and new coordinates. Entered these as WP9 and designated as target. Same as before, coordinates were not in a target, but close to one. I could easily make out a radar rotating this time. Designated and dropped JSOWS in TOO mode as before. Received radio message of good hit on target and new coordinates. Received and entered these as WP10. As I was out of JSOWS, I used F10 to have my wingman attack. He DID NOT and would not ever attack, and stayed in formation with me. Low on gas, so I returned to the boat using normal radio procedures. Case III landing with 1000 lbs fuel left. Received MISSION COMPLETE message and a score of 70. Enough to advance to the next mission. <END SPOILERS> not pretty, and certainly not as BD intended, but enough to get me to progress (looking forward to playing this one again once ED fixes the bug issues.).

Just updated and tried it out, same result. First flight stays orbiting WP1. <spoilers> If I push to WP2, 3 and so on; eventually the other flights catch up. I get the message that 3-1 drops thier PIGS, so I proceed to drop mine. On the way back to the carrier I get the message about the contact.

I think we have to wait for the next update. Baltic said (in that thread) that’s he’s already let ED know. Sucks! I really want to finish this - so far - excellent campaign, and I dont want to skip a mission!

So can the player manually edit the waypoint, or do we have to wait for the next update?

Any fixes in the meantime, or work around?

Same issue here. I eventually get him to join me, intercept the F-4’s and all. When I tell him to engage the other targets though, he launches his pigs at the original target(!?) or doesn’t launch then at all.

Did the same thing I’ve been doing, but it worked this time. Dodge 5 didn’t land, but kept on with the mission and intercepted the Fencers.

So I didn’t see any mentions of this campaign in today’s update. Any word?

Were the fixes included on today's update? I didn't see anything about it in the patch notes.

Awesome! Thanks!

I tried again last night, and same thing happened (just later in the mission.) This time I was able to get back to WP2 to anchor, and had several messages to be on standby and Lizard flight was starting an attack run, etc. Then the ROE Mission Failed. Post-mission screen showed a Fencer crashed again. I forgot to save the track file though. I’ll give it another go and - if the same thing happens - make sure I save that TF.

Mission 15. thanks!

***spoilers*** After my wingman and I took out the Flankers, we were headed back to anchor at Gori (WP 2) when after a few minutes I got the message that we had violated our ROE and MISSION FAILED message. Looking at the log after the mission, it appears a Fencer (Fencer 3) crashed on its own. Did this cause the mission failure? I don't know what else could have. No other shots were fired after we downed the Flankers. Bug? Fix coming, I hope.

Works now after the patch! Through mission four so far, loving the campaign!

Flying mission two, push from waypoint 3. Get the AWACS call to turn nose hot on incoming MIGS. So I head NW and close with them. A lock one up, but I get the jamming indicator (line of dashes) on my radar. A few seconds later I get a MISSION FAILED for violating rules of engagement. I never fired, but was getting locked by the Mig-29 (I think he fired just before I got mission fail.) Any suggestions/ideas? Thanks all - loving it so far, but I don't want to glitch out on the second mission!

Is anyone else having issues with radars, across a variety of airframes (14, 15, 16, 18, Jeff) not detecting, and then not being able to maintain a lock on targets since the update? Especially under 20 nm. Couldn’t get an F-15 to lock in boresight under 5 nm last night.

I've saves several track, but all of them are over 5MB. I can't get them any smaller to show the issue and under 5 MB. The TPOD itself (FLIR page on right DDI) appears to be working fine. TPOD stays locked on moving target and follows it. However the "on the ground" target designator box IS NOT tracking the moving target and remains fixed on one place. Highly annoying! Is there an e-mail address I can send the track file to? The only mods I have installed - aside from airframes purchased from ED - are SRS radio and TACVIEW. Thanks!

The TPOD does not actually track the target on the ground (moving target, using point track) even though it appears to be tracking on a DDI. This obviously affects the ability of IR MAVS to lock on to a target, as an uncaged MAV moves to the point tracked location on the ground - which is several feet behind the actual moving target by the time it slews. Track file was larger then 5 MB, so could not post; but should be easily replicable. Have tried it multiple times with same result. Lock up a moving target with the TPOD using point track. The DDI FLIR page shows that it is locked on the target and tracking it. Now fly your aircraft toward the target designator diamond is in the HUD or HMD. The target diamond on the ground will be behind the target and not moving, fixed to a location on the ground where the point track was first designated. Yet the FLIR DDI will indicate that the target is being tracked. Please address as a priority as this makes the TPOD all but useless to properly designate, track end employ guided weapons against a moving target. I tried this with laser MAVS and GBU's as well, but since the TPOD isn't actually tracking the moving target, same result.