DoorMouse

Press shift enter and bring up the joystick display. It also shows radar mode. When jester is in TWS Auto you can't tell him to scan manually. It would be nice to have him go back to yes manual if you know something is there tho, I agree

That type of behavior is realistic. You're being tracked in TWS by the f-14 and the missile is being fed data while its own radar is completely off. It only turns on just before impact to do its terminal guidance to target a few seconds before impact. It was designed this way

F-14 Pilot- Doormouse Rio- WhiteRabbit

This is a known issue but they say they are having issues replicating it. If you do more testing try to stream/record it, and turn your track files on..they need more data. I've got a thread in the bugs section, but the HB guys are responding to this one. Either works

Are you saying that Jester just forgets to turn on the missile prep if you jump into the Rio Seat after he has performed startup? That may be a feature? He keeps the radar in standby as well untill you take off. Could you list out the problem/steps in some bullet points?

This still happens on a daily basis- At least Twice again tonight. Ill post recordings and tracks.

Interested to see this track. I've had issues with the upload before. Try loading it to Dropbox and then pointing their upload utility at it- or link it here.

Please someone tell me the MLC Auto was what was causing jester to screw up? I really hope this patch fixed jester. Another several months of not reliably being able to TWS with him would be really obnoxious

That's not correct. The ACM switch makes the sparrow and phoenixes drop off the rail faster, and it commands the Phoenix active off the rail. It also overrides the various modes of the aircraft and let's you select air to air weapons, and finally it turns msl prep on and guns rate to high In no condition does it BORESIGHT any missiles. It does however only allow Phoenix 1second launch cycles if the target is less than 10* ADL. But the seeker head is not boresighted in any way

I think you are talking about the ACM switch (red cover) The OP is talking about the msl mode button which does only two things. 1) put sidewinders into BORESIGHT 2.5* circle rather than 40* for shooting in tight engagements with friendlies or against the sun 2) put sparrows and Phoenixes into FLOOD mode

(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)