DoorMouse

So specifically the mode I am talking about is not Home on Jam, but more of a Self Protect mode. If you lock up a tomcat or have your radar on, the phoenix could acquire and track you.

Just to be clear - we are talking about Home on Radiation, not Home on Jam. Right? If they are actively locking you or have their search radars on, the phoenix will act like a HARM

@Naquaii While you're here- Any plans to implement Home on Radiation for the AIM-54- IE it will seek out airborne active radars. I had heard a former Tomcat A RIO talking about that as a mode in a different discussion.

Appreciate the replies and info. I had this understanding but I think its important it be said by you guys so we can point to it... Again there is a lot of confusion with people who don't own the Tomcat module regarding how it operates. Hell, im learning things right now and I have more hours than I care to speak about in it. I thought you cannot PD-STT and provide Range information while it is TCS Slaved, and that once you slave it to TCS all shots come off the rail active. That is very interesting! Honestly I'd love a chart of all possible launch conditions and their behavior, I think a lot of people benefit from it. Hell, if I created it could you correct it? ----------------- Regarding the TCS switch not providing RWR warnings - When we did this test last fall we were using F16s and F18s as the targets, flying straight and level. It was not a blind spot issue or isolated to a specific airframe. Completely understand that you need specifics and some tracks/videos. I'll try to do that this week and get back to you guys.

@IronMike Ok so here's my best understanding. It's been a while so I do forget the exact steps. Last time we all discussed this several months ago (around when ED fixed the aim54 desync issue) there was also a Fix applied in the patch notes which said it resolved some of the issues with the TCS slaved shots... However others re-tested this after the patch and found that the Phoenix still does not give an RWR warning in situations where you fire a TCS slaved shot with your radar on standby (or off) and... I think subsequently break lock. I'll have to see if I can get you the right steps, but it was my understanding this was known by you guys, and we all reported it here afterwards. Another separate point, the radar modes and firing conditions are pretty complex compared to other aircraft and most people don't understand them.... Hell I think I probably have a few points I'd like clarified. If you guys could make a table of possible Phoenix firing modes that would be incredibly helpful and informative. Maybe call out where discrepancies between the current implementation and reality might be (PD PH Active, and the DCS 10 mile limitations... for instance) For this point... Could you confirm: ANY shot made with TCS slaved will go active off the rails just like a PSTT shot, correct? But they should be getting an RWR warning I'd presume... There is no way to guide the Phoenix in silently.

If people want to talk about the Whitepaper or Improving performance/accuracy of the module that's great. HB acknowledged the issue in less than 24 hours said we would see progress on this in the upcoming patch, and the AIM-54 being switched to the API is item #2 on their public roadmap. Thats a pretty fast response time. At least wait for the new patch and then test it - and then you can present it the way DunDun did with data. Otherwise you aren't helping and just screaming into the ether like a crazy person.

Sorry to Necro this topic but I believe it is still unresolved. We had a number of fixes in the patch after these discussions but it was found this RWR bug still works under certain conditions

ECM is barely modeled in this game, in the most simplistic way possible.... Why would any dev spend time building ECM when ED is likely to completely change how it works this year- As has been stated. Its just wasted time. If anyone truly cares for online play just either disallow all ECM to make it even across the board, or live with the way it is today. Those are your practical options as of January 2021.

I think this is a feature? The speedbrake can be commanded at any valid speed regardless of engine settings, with the exception of commanding afterburner. This means you can keep the engine spooled on landings and in combat without worrying that your flight profile will drastically change with your express command.

E-TF[113]-Doormouse F5

Really took the wind out of my complaint there, Mike....

Here is one example, happy to provide more: https://www.twitch.tv/videos/1230764362 But in short: Jester will not IFF targets you have STT locked WVR. He needs to put an indicator on the TID Bandit or Enemy as HIS VERY NEXT ACTION after an STT. A human Rio does this instantly, and it should be trivial for Jester to do the same. Why do we need a TID icon if its WVR??? Well, Jester often calls Enemy aircraft Friendly. He very reliably screws up his call-outs and will say "You Locked a Buddy" on a bandit. I hypothesize what is going on is that if the F16 is on both teams, the logic screws up. I have no idea what the logic on the back end is, but I can say for certain it is 100% broken, about 50% of the time. It is unreliable enough that you just cannot ever listen to it. I have Hope that this can be fixed, because upon further review he does go into his WVR workflow and starts calling speeds and bandit locations when it is a real bandit... EVEN IF he says "You locked a buddy". This makes me think something is just messed up In any case, this can be avoided if Jester, rather than doing whatever logic he does now, just presses the Bandit/Friendly ID button and puts the correct answer on the TID. If his voice line then was driven off that, rather than whatever it is today, he should give the correct call out. TLDR: Can you teach jester to IFF properly in WVR situations, please?

Any response at all on this from the team?

I mean ED showing up in the news getting arrested for F16 documentation MUST have sold SOME copies. Just send a crack team from Heatblur into Iran to get documentation

Fair enough I dont think the IRIAF was particularly forthcoming with their documentation. It would just be neat to launch the existing hawk- but maybe thats best left for mods.

This is absurd. Air to Air missiles intercepting eachother is not in any way realistic or intended - this is a bug. And as a point of clarification, a tomahawk cruise missile is TWICE the size of a phoenix missile and will have an even larger RCS due to the wings.... and it is incredibly challenging for missiles to intercept those. Having SD10's intercept Phoenixes or 120's is complete nonsense.

God, I hope we get Hawks for the IRAF tomcats

E-TF[113] Doormouse Mig29

If you can VID a Phoenix, you have bigger problems but yeah this one would be cool to get models for.

This is my anecdotal experience as well. I feel like the radar needs to be less sensitive to network issues. I hypothesize what is happening to be that the real radar has a refresh rate and sometimes the network data runs afoul of that. I also still get issues where the hud will lock things and the diamond is somewhere nonsensical. They did a great job syncing the TCS with pilot and Rio in the last patch, I'm hoping these are solvable too.

This always drops tracks for us, even on non-maneuvering targets. its a major annoyance. It seems to be much worse on multiplayer with many players. My hypothesis is that the AWG 9 has a very sensitive requirement to "hold" a track and needs constant updates that heavy multiplayer servers cannot provide - So your local simulation thinks it has lost the track, when really it is that the MP data hasnt gotten to you yet, or is the wrong tick-rate, or there was just a temporary network slowdown/loss. Switching to TWS Auto is a partial work-around sometimes - It seems to work better- but it shouldn't have to be.

Awesome patch, and thank you and the team for taking the time to look at our report. Appreciate it!

Thank you, and awesome this is getting resolved soon! Also great information on the CW/flood when Slaved to the TCS, that is so cool! I'm looking forward to the TCS STT modes being implemented

Which requires nose hot and you can't guide a Phoenix. It also is limited to less than 3 miles or something. It's pretty close range, different use case

If you lost radar lock. Often at less than 30nm the TCS does a better job of tracking than the radar if they go to the notch. The Camera will track the target just fine- Fire off a phoenix in their direction to keep them from going Hot. for one. Its a neat feature, but very very situational.... frankly I have no idea how its supposed to exactly work. We would need an SME