thodre

I can't believe nobody reported this and it still isn't fixed with the patch. Shrikes are utterly broken in MP. They track in SP and as soon as i play the same mission on my server (or any mission on a MP server) they don't track at all. This has been the case since the last patch. Can you please look into it?

Try shrikes - it's a close call vs an sa-2, but it can be done and you are well inside the range of a Vietnam scenario tech-wise. Go high and fast, they'll usually launch some seconds before you can, loft the shrikes then haul ass while still presenting yourself as a target - nothing more satisfying than a burning Fan Song

Okay, now i did A LOT of testing, i'm pretty certain the fault was mine here. Believe it or not - that's what happened: After a long time my new stick from virpil arrived (yep, only the stick, not the base which already was a virpil) the very next time i fly the Phantom the problems are GONE. At first i couldn't believe it. I did more than 30 flights with the same setup and the radar acts like it always did. Now how can that be? Well, my old warthog stick has a bit of a play where it connects to the base. Maybe that was the problem but i doubt it. Being someone who needs to know i disasembled the stick and measured all the switches in there. Lo and behold, one of the 4-way switches gave back random impulses without even touching anything. Now, like i said the problem is gone - but i still would like to know. Could this cause the weird radar behaviour in the trackfiles?

Nope. Mk49 tracks the 'low blow' just fine. This was in loft mode. germany.trk

None taken. The thing is, it worked fine for some months now and suddenly it doesn't. Two tracks attached. On one i lock once and hold it until the bandit passes, second one i try to lock multiple times with no luck. multiple_locks.trk one_lock.trk

I don't know when it happened, but right now it's almost impossible to get a viable lock on planes. Speed is jumping like crazy, missiles won't even come off the rail without INTLK set to 'IN' - Speedgates don't seem to work for boresight (well, at least not the way they did before). Is it just me or does someone else have that kind of problems?

Looking good now! Thx!

So no sightseeing today... good thing is tomorrow is a holiday here

Exactly this! Give yourself a bit wiggle room, don't be too slow. Jester will love you for it "This landing was almost as beautiful as Meg Ryan..." "Yep, if the runway was bread, you'd be the butter..." "Man with a landing like this you could park it in suburbia..." "I hope the squad was watching..." "Are... are we down yet? I didn't feel a thing..." Which ones did i forget?

Right now the shrikes for me only work on the larger AA installations (SA-2, SA-6 etc.) On SA-8 / SA-15 they seem to track only while a missile fired at you is in the air. I don't think that's the right behaviour - as long as the radar tracks you the shrikes should be guided. edit: Just did a few tests - with the MK50 (loft) seeker the Shrikes guide fine for SA-15 in WRCS, so i was wrong. I used the wrong seeker. The table in Klarsnow's guide should be updated then. Tacview-20250106-094845-DCS-shrike.zip.acmi Tacview-20250106-095632-DCS-shrike.zip.acmi

I don't know about the seeker, but it starts correcting it's course below 18000. It's clearly visible on the missile-cam. I haven't. I usually use wrcs which works pretty well for everything up to a range of about 20nm.

In a different thread a user posted a story about a B-52 that got hit by a AGM-88 which targeted the tail gun radar. So i guess it's possible, since the HARM should be the smarter of the two missiles. Fun fact: After the accident the B-52 got the name "in HARM's way". Don't know if the story is true or not, at least it's entertaining https://www.twz.com/10314/the-time-a-f-4g-wild-weasels-anti-radiation-missile-blew-apart-a-b-52s-tail

Not sure if it is a bug - maybe it's working as intended. Is it possible that back in the days shrikes also went for planes? Scenario: I'm high up going for an SA-6, WRCS, Shrikes with Mk. 36 seeker set to loft attack. There is a Fishbed at 12 which my buddy will take care of. As soon as the shrikes came off the rail they went for the Fishbed. Buddy fires a sparrow, the fishbed goes cold and the shrikes spiral down to the fields... Tacview track included. Now there are several questions 1. Am i misinterpreting the behaviour of the shrike? 2. If they really went for the Fisbed - are they supposed to do that? Tacview-20241124-165500-DCS-Cold_War_Syria.zip.acmi

Oh, so even the HARM did it... at least once. Thanks! Thanks, i'll ask. Not sure if it's a bug at all right now

Have to ask here before reporting a bug - maybe it's working as intended. Is it possible that back in the days shrikes also went for planes? Scenario: I'm high up going for an SA-6, WRCS, Shrikes with Mk. 36 seeker set to loft attack. There is a Fishbed at 12 which my buddy will take care of. As soon as the shrikes came off the rail they went for the Fishbed. Buddy fires a sparrow, the fishbed goes cold and the shrikes spiral down to the fields... Tacview track included. Now there are several questions 1. Am i misinterpreting the behaviour of the shrike? 2. If they really went for the Fisbed - are they supposed to do that? Have a nice Sunday! Tacview-20241124-165500-DCS-Cold_War_Syria.zip.acmi

I should have checked here earlier - same for shrikes with no tone and no needles.

Oh, so it's not just me! Can confirm.

You're right, tried it myself and am able to make him lock at even greater ranges as before the hotfix - but it's hit and miss and the locks are pretty fragile

Happened to me only once on a MP-Server - never had it again, but heard of it. Not a consistent bug for everyone i talked to.

No success. Still locking only below 10 miles.

I think it's the latter. Usually i see the targets right before Jester sees them on the screen - now we both don't. I already tried telling him to set the antenna center, tried both narrow modes - but no success.

Three times there wasn't even a callout when the fishbed already fired. f4_nodetect.trk f4_nodetect2.trk f4_nodetect3.trk

No, not the case. As soon as he calls them out he can lock them. That happened at ranges of 12-20 miles for a headon Fishbed. Now it's about half the distance for the same scenario. I'm not sure it's a bug or intentional - maybe the F-4 radar was that bad and the one of the Mig is overperforming. It's just that it changed with the hotfix.

It's Jester. He calls out targets only under 10 miles now.

Oh... so that's why the pickup range of fighters is basically reduced by half after the hotfix? I can't believe nobody noticed by now.