DoorMouse

To be honest, it is really quite bafflingly inconsistent right now. I'll refrain from calling it useless, but it's maybe slightly better than useless. Im compiling some examples, but it is overtaken by an aim7 or even the firing aircraft against targets inside 10 miles sometimes... You will see it often wobble back and forth like it can't decide what path it wants to take to the target- this is primarily during PSTT launches. Something is definitely wrong with the guidance. TWS is definitely incredibly reduced but 30-40 mile kills are still possible, but I Don't see how it could be performing any of the test shots the HB had listed as benchmarks. I can't say with 100% confidence, but I'm pretty sure the Phoenix should out range the aim120 a/b/c5? My concern is that guidance is out of your hands and that means we are all at the whim of a third party who has many irons in the fire already to fix it.... Who knows when ED gets around to it. It's also the case that you guys have had moving this over to the new API as a priority on the public roadmap for a long time, so I presume there are still things ED has yet to provide you with in order to do it... Or it's just simply not possible yet. Could you set any expectations as to when we may see a fix on this... While it's not "useless" it is absolutely hobbled.

Thats the question. It's got significant deficiency in guidance, but that's not up to HB. It seems to more closely match the CFD in a straight line though. Edit- corrected.

@Naquaii @IronMike That was very quick turn around. Thank you. Could you guys provide any data around what you changed and your testing data? It would be good to see how close it is to the CFD now, and where you expect changes when it eventually ports over to the new API. Anecdotally, people are reporting it's a pretty significant change- but most importantly, let's help build the consensus that it's accurate so we can all move on to other things appreciate it

When we get the naval variant, can we get Ens. Jester as the character in the official campaign :-). I figured he flew f4s before tomcats.

E-TF [113] Doormouse/WhiteRabbit F-14 A RED

Unfortunately, DCS is single CPU thread, and single thread speed is king. I've seen massive improvements overclocking my CPU. More so than GPU/Ram/anything. Disclaimer: Overclocking can damage your CPU. 4.20ghz is pretty slow for that chip.... My 10700k im running at 5.1 pretty comfortably, and saw a pretty significant increase in VR performance. https://www.anandtech.com/show/16857/overclocking-with-intel-rocket-lake-four-core-i911900k-binned-and-analyzed/7 You should be able to push much faster than 4.2ghz. Provided you are cooling properly. Do so with care. Also turn your grass off, who cares. you wont see it at 10,000 feet. And experiment with turning the trees down. Due to the increased Radius, the greater the range, the more things that need to be rendered by a squared factor. (Circle Surface Area = πr²). So you arent rendering 2x as many trees if you double the radius, you are rendering 4x as many. They really do make a hit on performance as far as shimmering goes - If you find a solution to that please let me know. DCS looks like Absolute ARSE when there are buildings or objects with sharp angles, when viewing textures at high angles, everything shimmers. Its really annoying.

As far as I'm concerned DCS is in Early Access until this feature is added.

And the wings ripping off hilariously inside its published safety factor

That would be welcome news. I had not heard this.... and its been the neglected step child of ED's modules for years until they decided to make wings rip off hilariously last patch....

I suspected this might be the case. A RIO had a discord event a while ago and mentioned it... but I got the impression it maybe wasn't documented. I was hoping you knew more about it

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.