DoorMouse

(Correction) That is not 'always' the case. The Sparrow was designed to use the same signal the radar put out to establish a lock. This signal does not change when the sparrow is launched, and it only seeks the reflection of that target. The Sparrow can launch in two modes, PD (pulse doppler), or CW (continuous wave). CW can be Flood or STT, PD can be STT only. Neither of these change the outgoing radiation from the radar of the aircraft and in all cases, to be clear, the sparrow emits no signals. Only some of the sparrows are capable of getting a mid course correction from the rear antenna of the missile which MIGHT trigger an RWR warning as the signal changes to send data. Otherwise it just seeks out the pulse of the locked aircraft, and (i believe) confirms that PD signal with its rear antenna to make sure its on the right target. The Sparrow does not even turn on its radar Detector until its already well in flight and has completed it 'english bias' maneuver. Essentially the firing aircraft gives the missile a signal and tells it to "turn approximately this much and this far" before turning on its seeker. This is done for a variety of reasons but it seems the biggest one is to get it clear of radar interference from the launching aircraft. For sparrows that provide a mid course correction or are using PD, depending on how modern the RWR is it may be able to pick that up. For CW illumination, you basically have a flashlight on- the radar is blasting you and the missile is just looking for the brightest reflection, you would not get a launch warning.

You will not get a missile launch, only an aircraft lock warning. Fox 1's emit no radiation only seek Oh- I misunderstood. Yes. your RWR cannot see above/below you only to the sides. AND- If you bank, it confuses the RWR, or completely obscures the antenna

Upload your track to your message. Hopefully they see this. Ive got another one with video I need to submit. Its really fun when jester does this when youre at 25 miles hot and he makes you incapable of returning fire.

I seem to recall this happening to me when i messed up the track files. Did you make your own B side, because otherwise its blank.

Rule 1: If its forward Firing, its the trigger Rule 2: If its dropping ordinance its the pickle button Rule 3: you can only ever have one forward firing weapon at a time

Yes You can press CTRL ENTER and see your joystick positions, as well as the Radar mode the Rio is in. Its an overlay for the game, so Im 100% sure hes going RWS

It probably has to do with the 'framerate' of the server. So if there are a lot of things going on, like ground units, players, etc.... it gets worse. That is very interesting.

Heatblur has already said they think jester has some issues since the last patch. "expecting the rio to not switch radar modes upon firing" is pretty reasonable.

There is a thread I posted of this with Tracks and Recordings: https://forums.eagle.ru/showthread.php?t=281888

We have seen it with the bandit non-maneuvering holding a steady vector. I'll have to track/record it and post it, but good to know others are having this problem, and im not alone.

You can absolutely do this in the game. I've done it loads of times, its just not as effective as say a F15 at it.

FWIW I have found that the limiting factor is DCS.EXE seems to be CPU bottlenecked. my FPS went up significantly by overclocking from 4ghz to 4.4 ghz. Changing my GPU did practically nothing in this game.

Another item I didnt see in the list above is 1) Jester stuck in TWS Auto with no active locks/contacts/missiles. 2) Subsequent shots after this behavior result in a TWS Launch without Time to Impact being displayed https://forums.eagle.ru/showthread.php?t=282072 EDIT: Something my Rio and I have been discussing. Sometimes tracks will fly off at odd angles at what seems like mach 5, only to be replaced with a track just underneath of where it used to be. Sometimes they just drop of and are immediately replaced. This only happens in Multiplayer. Could it be possible the player you are TWS locking has some rubberbanding/lag and the radar interprets that as having them move between their two incorrectly reported locations? It may be determining through its logic that the de-sync'd player is actually two contacts, or has suddenly accelerated, etc.... and therefore causing an issue?

I get about 1/2 the FPS in the tomcat. 4.4ghz 32mb 2080ti. Ive even got the VR shaders mod running now which makes it playable. The f15 i get 90fps the tomcat i get 45.

Ensure radar is on, and not in standby Make sure pilot selects A2A mode, and not Cruise (which looks similar but has the compass rose tape) Select SW, SP, or PH (guns will not show the diamond)

Super fun as always, I liked the added depth of having a ground objective, rather than 1985-2 that was just an all out brawl. Looking forward to future scenarios!

Ive had more luck with a human rio- IT may be that the MLC issue has broken Jester's brain and hes dropping tracks, not locking stt, and missiles are trashing because of it? Im going to test some TWS shots this weekend with a human, but as of right now its almost entirely broken in multiplayer and you have to STT ACM all your phoenixes to get any hits. I used to be able to get 60-70 mile shots from 30k fairly reliably (under correct conditions, non maneuvering climbing target, 1000knots closure, 10kft-20kft altitude). I have not seen a single hit, even if somehow mercifully the track lasts long enough to pitbull.

So the A has a lot of modern features missing, and some development problems. Two big ones being: The TF30 engines were a horrible mismatch for the platform. They were not intended to be used in the way the F-14 could push them and their signature issue was that they would compressor stall at high AOA... like when you are maybe a bit above on-speed AOA for a carrier landing. Not ideal. The RWR was also a big difference. The A model's radar warning system was particularly lacking, and there are stories of how the crews would put consumer grade police radar detectors in the cockpit on the left and right side to detect incoming missiles.

SO i just did a super un-scientific test and made a singleplayer mission. Everything seemed to work, and phoenixes actually goddamn tracked their targets, the radar didnt drop locks all over the place. I have a feeling it has to do with multiplayer with many players/ground units/stuff going on causing issues with the radar when it tries to reconcile all the players positions.

I'd really love to hear a reply on this. The 14 has become incredibly frustrating to fly in multiplayer since the last patch, and supposedly no changes were made. I assume that means A) ED changed something that screwed up the Radar and therefore Jester's logic is messed up. And/Or B) ED changed the guidance of missiles again without informing anyone, screwing up the AIM 7 and the AIM 54 since they are both SAHR missiles.

Do you like a difficult challenge? Fly the B Do you enjoy randomly getting stabbed? Fly the A

if it went for chaff then maybe it just missed. If you have one that STT tracked the whole way in, had energy, and just plain didnt turn while you still had lock - That could be something?

Go to Advanced Options, Look in Additional Options. Click Manage Attachments From Manage Attachements pick one of the 3 slots to "Choose File" Once you choose it, hit UPLOAD Once it uploads successfully close the window. Id also take a look at their guide here, they get a million bug requests and this will help them sort things: https://forums.eagle.ru/showthread.php?t=253852

Please try to reproduce this and submit a full bug report the way they want us to if possible. The more evidence of this, maybe they will take a look. Heatblur has said they have not changed anything with regard to the radar. Jester's behavior is very different, but that is probably a symptom of whatever the core issue is. Seeing as how the Aim7s are having issues maneuvering. The Phoenix TWS shots seem to also not be maneuvering/hitting... I suspect ED changed something and didnt document it, or there are multiple issues. But please post track files to this thread, or the other threads so we get them concrete evidence. Right now the F-14 is pretty broken.

Go to your Saved Games folder and look for DCS/Tracks, youll probably have a ton, you'll need to find the correct one. Sort by date.