Gilligan

Would this allow me to chaff and flare independently? That's something I can set via the DED or in the new DTC system?

Start with a good boresight on the mavs. IIRC there's a building on the hill at the west end of Akortiri that is pretty close to 7 or 8 nm out that you can use to boresight. I put the HAD on the left MFD, the TGP also on the left MFD with a different OSB button, and the WPN page for the MAVs on the right MFD (PRE Mode). Get the emitter on the HAD MFD and lock it from >10nm out, ideally between 10 and 20. Then find it on the TGP, save it's position as a markpoint, and set that markpoint as your current steerpoint. Zoom out with the TGP until you have a sight picture similar in size/appearance to what the MAV is seeing and try to collate the images (IE - okay so it's the centermost dot in the middle of the circle of dots, OR, okay it's 3rd from the left in this line of dots, etc.) Finally lock that dot that you've picked out on the TGP as your target with the MAV when you're nose hot and in range. Don't forget you can zoom the mav in a little bit with the FOV EXP button if you have it mapped.

I'm not sure what changed, but AI flights now employ harms as directed/planned.

Second.

mods probably. There is no way in game that i'm aware of. You should post in the wish list though, because I'd love to see it some day.

Yes. Start up the Jet like Normal. Turn the AMG 65's ON as soon as the avionics power up so they can start their power up procedure. Set Ground Jettison to ON. Set Master arm to SIM (On works too but is a little sketchy lol). The most difficult part is choosing an appropriate object to align on, ideally you want to choose something a few (5-8) NM away from you to use to align the TGP and MAV Seekers, but that's not always possible. It's primarily for this reason I prefer air alignments, but sometimes it works out. Once you've picked something to align them on, align the same way you would in the air: In AG mode, set one MFD to the TGP, and the other to the WPN screen with the MAV selected in the SMS page. Set the TGP MFD as SOI and slew the TGP cross hairs on the intended object & press TMS up short The WPN MFD will become the SOI, slew the crosshairs on the intended object, press TMS up short, if lock is achieved press the OSB for BSGT. If you have MAVs on both wing stations 3 and 7, press the OSB button to switch to the other side and repeat the process. There is always going to be some parallax to deal with when using Mavs unless you're consistently locking targets at the same distance you bore sighted them, which is going to mean some displacement from where the TGP is looking and where the MAV seeker is looking. I never use the auto-hand-off feature, generally preferring to lock the mavs up manually. The Mav's are pretty fiddly. Just the way it is.

I had the same issue. You're not alone.

Things may have changed in recent updates, but at least in the past, the SAMs were always on (unless scripted otherwise), even if your HTS pod is not getting a fix on them. For example, even if you didn't have a sam emitter on the HAD display indicating the HTS pod was picking it up, you could launch in POS mode at a steerpoint co-located with the emitter, and the HARM SHOULD still track that emitter. Remember that SAM's require both a search and track radar to function Optimally (though they can still function with Just a track radar to some degree), and sometimes these show up separately on the HAD (EX: Snow Drift Search Radar and SA 11 TEL Track Radar vs SA 6 Straight Flush Search/Track Radar vs SA 2 Fan Song + Separate EW Search Radar like a Spoon Rest). Track Radars are generally directional and might not be looking in your direction until you are picked up by the search radar, or may be tracking other threats, which would mean your HTS pod isn't seeing that track radar beam to display it on the HAD screen. At least that's my understanding of it.

If a threat goes inactive or is no longer detected by the HTS sensor, after about 2 minutes the symbol in the HAD display will turn green, and then disappear after another couple of minutes. If the radar emitter goes inactive and you launch on it before the symbol goes green, or if it goes inactive while the missile is in the air, it is more likely than not that the missile "goes stupid" and flies right on into the bozosphere. However, without custom scripting, SAMs typically do not behave this way in DCS, and emit until they are destroyed. That said, the emitter you were tracking/launched on could have been destroyed before your missile got there, which would have the same effect. In my experience the HARMs in DCS do not remember the location of threats and just go ballistic once tracking is lost. Sometimes they also just miss. To have the best chance of hitting your intended emitter, launch when the symbol turns red (indicating that you are being tracked by the track radar) and try to keep the radar track active as best you can.

I had a similar issue with my original input setup. The MAV definitely slews at a different rate than the TGP/other sensors (Radar), and I had trouble making fine enough adjustments to use them effectively. Not disputing if this is an accurate recreation or not, but I did find it difficult. My personal solution may not suit everyone, but I bound a second input for TDC slew with a much slower curve. I have a TM 16000M throttle with a "Coarse/Fast" TDC slew curve on its joystick, and a WingWing F16EX with a "Fine/Slow" curve on it's thumb joystick. If you are limited to once TDC slew input then this may not work, but if you have second input option this may be worth a try.

Yes you can use the TGP to look at the ground with no AG Weapons loaded. In NAV or AG master mode, set the desired MFD as the TGP display. Hit the STBY OSButton and select AG You can slew the SPI from here, or create a new Markpoint/Steerpoint with the JHMCS on the ground and the TGP will focus there. To create a Markpoint (Steerpoints 26-30) with the JHMCS, in NAV or AG master mode press "7" on the ICP to enter Markpoint Mode. Use the Dobber (Right) to cycle the first field in the DED until it shows HUD. If it says HUD already, leave it there Hold TMS up long and you will see a large circle appear in you JHMS display. Look at where you want to create a new Markpoint/Steerpoint and hit TMS up Short once. This will "Drop" the SPI indicator on the ground where you are looking. You can slew the SPI box from here to refine the location if desired. When you are satisfied with the location of the marker, hit TMS Up Short again and it will save the coordinates at that point, you will see the coordinates update in the DED display. Hit "0" on the ICP to set this markpoint as the current steerpoint. Dobber left to exit Markpoint mode. If you do not have a JHMSC installed you can put the intended location in the HUD and slew the circle to where you want it and follow the steps from there.

Possibly. I have successfully contacted Tusk in the past on that mission tho, and as far as I can remember, the AI wingmen never hit their targets, so I'm not sure. I think there's also an issue presently with any AI aircraft being unable to use HARMs without some sort of script directing them to, so the AI SEAD flights are completely ineffective in this campaign. If you have tac-view I would check that and be sure that Tusk isn't just being hit by a SAM early on.

IIRC you need to be using the "alt" comms menu ( "Ctrl" + "\" ). Sometimes he gets shot down before you're at the point in the mission where you're supposed to contact him.

There's a "Village" on Saipan Named Puerto Rico, which is where the PLA troops land on Saipan in the campaign.

Finished the campaign earlier today, and I gotta say, incredible work. Groundpounder Sims continues their streak of highly polished, high quality, immersive campaigns with incredible depth & world building.

Seems like a pretty rare/niche occurrence and that it will be difficult to nail down exactly what is going on. I appreciate you guys taking a closer look at it, however.

This could also be a result of the modeled "INS Drift" feature, which accumulates error over time in the mission. More aggressive maneuvering tends to accumulate drift faster. I have found that over longer missions, the SPI indicated location for steerpoints tends to drift by a couple hundred meters one way or another, especially if I've had to do some hard maneuvering. CZ'ing does not reset the SPI to the "correct" location. Hard to believe this is true-to-life behavior (post GPS and with GPS Correction) as it renders pre-planned JDAM strikes (without TGP correction) basically impossible, however this is supposedly modeled correctly.

I've seen at least one other thread on it happening in multiplayer. I agree they are likely connected, since the HTS can command the slew of the TGP, if the HTS is malfunctioning and directing the TPG to slew somewhere weird then that makes sense. When I turned both of them off to egress from the target area my Steerpoint SPI's stayed where they were supposed to be instead of jumping around like they were when both sensors were powered on. So at least that "Fixes" the Steerpoint SPI from moving. I didn't try powering them back on to see if that would change anything as far as getting the sensors working again, however. Interesting, if it ever happens again I'll have to try that. I agree it seems like the HTS bugging out is commanding the TGP to slew at "nothing" or whatever defaults the HTS reverts to when it is failing to lock. That is unfortunate, as this bug seems to be relegated to longer or more scripted flights/missions. The issue being caused by threats activating/deactivating makes sense, as a major part of the Weasels over Syria campaign are scripts that try and simulate more realistic SAM behavior by having them power on at specific points/ranges and then off again to spoof HARM shots. So it's possible I was locking/attempting to lock the Snow Drift during one of these scripted power on/off cycles, which caused the HTS to wig out. If it happens again in a shorter track I'll be sure to save it. I've sense completed that mission and one other long mission which used the HTS and TGP pods heavily over a longer, scripted mission with similar SAM behavior but did not experience the bug again.

Bind it to the input: "Paddle Switch - Depress"

Finally cleared this one with the 100 score. Man, that was a tough one.

I know what you mean. For now I have submitted the track file on the main viper bug reporting section and its being reviewed. I'm sure if it's something I did they'll tell me, though I have read other threads about the HTS pod suddenly failing mid flight on people. The TPOD issue is new, however I have a feeling it might be tied to the HTS issue. When I turned both off to egress and land it stopped moving my SPI/steerpoint diamond and left it where it was supposed to be, which makes me believe it was definitely something going on with one or both of those sensors. Thanks, I have no doubt I'll be able to find it so long as the TPOD is working correctly. it was just tough to make out details when the tpod was jumping around like it was. Unfortunately we only get so much resolution on the MAV screen, but it was at least holding a lock for me at the time.

No, I didn't have it on that attempt, but I know what you're talking about. I was able to lock and find the SA6 sites prior to the HTS going down. so it was working initially, as was the TPOD. I wasn't in markpoint mode, or any other sub-mode that would inhibit it from locking, as far as I am aware.

Got the clear finally, but missed the command center. I had some DCS bugs that really took the difficulty up a few notches. Both the HTS and TGP bugged out on me - HTS stopped locking anything when I was going after the SA11 site, and then the TPOD started jumping off the selected steerpoint/locked SPI and just looking north. reported both with trackfile so I guess I'll see what comes of it. Still managed to drop the 105's on the three TELs, but mistook a Shilka for the command center with the mav sensor and took it out instead. Ill probably try for the 100 score again.

Was flying mission 11 in the new Ground Pounder Sims Campaign for the Viper, Last Out: Weasels Over Syria, and while I was trying to knock out the final set of mission targets I encountered a set of bugs that were new to me and made completing the mission exceedingly difficult. 1st the HTS pod stopped locking targets. I was not in Markpoint mode, nor did I, to my knowledge, change any settings or do anything that would cause the HTS to stop locking targets, but I could not lock any radar emitters on the HAD screen. Specifically I was trying to get the Snow Drift Radar but I couldn't get any of the others I tried either. Possibly related to this, maybe not, the TGP would not stay on the currently selected Steerpooint or locked point/area/INS track SPI. It continually popped off where I wanted it looking and, as far as I can tell, just started looking dead north of its own accord. I could CZ it back to the steerpoint for a moment, but it would jump back off to the north after somewhere between 0.5 and 5 seconds. Sorry for the very large trackfile, it is a very long mission. https://www.dropbox.com/scl/fi/pr7kpe1gzdqk096bcdllc/Weasels-Last-Out-M11-Vipers-1.trk?rlkey=4xb78i7n24trubcuhz6qszcp7&st=b0i4ry0y&dl=0 I start experiencing the bug after the first two SA6's are gone and while trying to engage the SA11 site. Should be about 1 hour in.

Thank you. Sounds like I'm on the right tack and getting closer. Some more patience dealing with the 11 once the 6's are clear and I might just have it. Appreciate the advice. And again, stellar work with this campaign.