Lymark

Somebody on the discord figured out a temp fix to the RWR issue in PVP. I'll repost my comment here. https://forums.eagle.ru/showpost.php?p=4152325&postcount=32

There's a temp fix floating around on the GS discord, I haven't tested it yet, but a few others said it's working so far(in MP). It only fixes the RWR and warnings, not D/L.

It sucks but I don't think we will be getting another update until next year. Since everyone will most likely be taking a holiday break.

That inconsistent sounds about right to me. I could be seeing [14]/[15]/[18] the 1st flight, then no [14] the 2nd. Then nothing at all the 3th.

1)After start up, insert the DTC and upload its data to the aircraft via LMFD 2)Eject DTC, re-arm and update your DTC with the crew 3)Insert DTC and upload again

And that's every single flight that you've flown? My friends and I only have a 1/3 chance that it will work. It's like a lucky draw every time we start it up.:(

+1 My friends and I have been getting very inconsistent results in PVP(GS server) with the DTC trick. In one flight, the RWR could have totally bugged for me but not my friends, then the next spawn, it'd work for me but not for them. Then, there's also a VERY high tendency for it to not work for us at all. Not to mention that, I rarely receive [14] nails nor warnings from the phoenix. So now, whenever I find a target on my radar and it's not painting me, I'd just assume it's a F14. Also, the old bug where my radar locked target wouldn't show on the HSD sees to have resurfaced now(Picture attached). It was just a one time thing tho.

Do you see F-14 tho? I've been using this trick since the big update on wednesday, never have I once seen an [14] icon, sometimes no [15] too, [18] seems fine most of the time tho. (Everything in PVP)

According to Nineline on reddit, It just seems to be a miscommunication.

Loving the new binds! The only essential buttons that's left, at least for me, would be the 3 ways switch that you mentioned and the 'Betty shut up key'(master caution). :lol:

I'd also like to add my experience in PVP too. Not only have I not received 'tracking' calls(the well known MP bug), I now do not receive RWR aircraft type even though they have me on their radar, nor MAWS warnings. Which are new bugs in this patch for me. The 'RWR aircraft type not showing' bug seems to happen to certain aircraft only. I have not seen [14] yet, and occasionally for [15] as well. Picture attached is an engagement against a F-14. Of course I didn't know it was a F-14 then because the only available info was from my own radar. I assumed it was an F-15/18, so I started cranking at ~40nm, the only warning that I had was a big boom that killed me. No other warnings no nothing, just went from that picture to a big boom.

Man, i thought we had a 6 weeks long QA. I have no clue how we've been able to find more critical bugs in 1/3 time of the QA than the QA's team. I think what bugs me the most is how limited 3th party teams have over updates, and I also realized that December is the worst month to release a module. Everyone is trying to wrap things up, and if they miss anything or couldn't fix things in time, then we'd have to wait for next year. That's what sucks the most!:(

ED hasn't released the patch yet, it should happen in between 1~3 hours from now.

Thanks for the info! :)

I went back and checked the 'alive time' of those shots. Both the 70 and 80nm shots lived for 2:30mins before going dead. However, the 75nm one has lived an extra minute(3:30) for some reason. I know nothing about battery lifespan, but thought I'd leave the info here anyway.

The latter is correct. Everything that's fixed now is only fixed internally until ED releases their open beta update. It normally happens once a week, but last week was canceled and it's not something 3th party developer can control. Good news is, this week's update is planned for today!

While we're at it, can we get a preview of 'Updated cockpit textures'' too :lol:

I was curious about the max range of LD-10, so I tested it in a quick mission that I made in SP, and the results were interesting. All tests were conducted at 40,000ft ASL with full burner at M0.92. #1) A 80nm shot= The missile tracked the radar source about 2/3 way through and it suddenly decided to dive toward the ground when it's 13nm, 21000 feet away from the target at Mach 2.1. #2) 75nm shot: Again, it detected the target, but it started aiming toward the ground at ~8nm away and 15000ft at Mach 1.97. #3) 70nm shot: Began diving at 4nm away, 6000ft at Mach 1.62 #4) 65nm shot: Finally a hit at Mach 1.3 The 'fall off' range seems to vary based on the speed and altitude that I fire these long range shots from. Track files attached 65nm hit and 70nm miss.trk 75-80nm misses.trk

I'm no thermal tech expert, but I just tested the TGP after reading this post. I think the issue with that picture is that, as mentioned by others, A-10C's level/gain is already tuned to a perfect settings, whereas JF-17's is not. Default 'Level' at -4 is totally overexposed. Everything seems to be quite distinguishable after giving 'level' a positive value. By no means It's perfect, but I won't have problem finding targets.

I think that's working as intended. The HARM on the blue side is supposed to have a similar mode called PB(Pre-Briefed), where It will steer toward a coordinate and hit on the exact spot If it finds nothing.

One of the devs in discord said that there might be an update on Friday, later today.

I'm kinda surprised that we ain't getting beta update this week, seeing it's a newly released plane and Deka managed to fix a longggg list of bugs a few days after release, I was actually expecting to have more than one patch within a week.

There's no update this week. ED wanted to push everything in to the big hornet update next week, the 18th). :cry:

There's also a guy in GS who has had similar 'crash during engagement' experience as mine. He suggests that the issue is somehow connected to when an enemy(PVP) is on his and is spamming AIM-120s, which fits the description of my previous report. As long as he avoids having enemy on his six, he's crash-free. I'll try to ask him to report his experience here.

Me too, the only evidence I have is tacview from the GS server, not sure if that could be any of help. I swear it must have something to do with the RWR/MAWS, datalink, aim-120 or any of the combination. I just crashed out of my 1st game of today, was dealing with a single F-16 in the entire area, launched one SD-10 at him at 13nm in TWS at ~13k feet, then I dived back to deck and went cold. His has only fired one 120C and it appeared on my RWR as the same time as he's killed by mine. My MAWS screamed ''Missile, Missile'' when it reached that 5km detection range, but it was too far/slow to catch me. ~10-20sec later, my game crashed, again, same situation. :doh: My rig is: AMD Ryzen 5 3600, 16GB RAM, GTX 1060. And I've been flying with a 4x SD-10, 2x PL-5II, Two tanks and SPJ pod as my PVP A2A loadout. Never have crashes like this before in other modules.