Archer.xd

Leagues: 4v4 Squadron Name : VTAF Discord/Guilded: Archer#7762 / Archer Contact person: Archer

thx didnt saw that report

When u lock a bandit with SAM in RWS (single TMS up), it doesnt shows up on HUD. No target box, nor range. (AA mode selected) You can even slew radar cursor everywhere with maintaining lock on bandit rws.trk

[VTAF] Archer Blue F/A-18C SC = Yes

Well, firstly i strongly agree with current F-14 bans&restrictions on PvP events. If these bans were caused by a single bug, yeah that would be a foolish thing to completely ban. But hey, there are too many bugs and too many ways to trigger one of them. "We're certainly disappointed in the decision-making process of various tournaments- especially those we have sponsored. We will not be involving ourselves in sponsoring tournaments that do not allow the F-14 for now." About this, yeah i can understand your situation but come on, these desync bugs are around for a good 6-7 months. Rather than throwing the ball to other responsibles (if its caused by ED's API or smth else) you guys just could work together and fix these things. Instead of fixes, in every update we only see its getting worse and worse. And now the "no RWR warning" is back with the latest patch. Yeah, every missile has desync issues and unrealistic things going on but lets just take a look and try to find which one of them is the most common and most affecting the gameplay. AIM-54s and F-14s ! I have the F-14 and i bought it to play what it's intended to be played in, A2A. The week after i bought it, a patch came in, and boom! RWR warnings were gone. Almost every PvP server decided to ban the AIM-54 and tomcats, which is a legitimate decision. And this means i cant play a module i bought to play in the way it should be played on. And then with later patches yeah rwr thing was fixed but desync came into the battlefields. And im not talking about a simple desync, this missile really has amazing skills in desyncing. (not considering the other weird acts of aim54, just gonna talk about desync) Personally, i've experienced many of these desync things bcs we were testing it to find out how far its gonna go and i know most of the techniques to trigger a desync. And the weirdest one i've seen is a missile (AIM54 ofc) crashing to a mountain and exploding on there and then it *flies* to the target which is behind that mountain missile was crashed into, and then kills the target. And this wasnt a problem at first since we've only seen it once, we just laughed it off. But then with time going on, it started to happen more often. It happened both on populated servers and private servers by the way, so it's not completely related to the server. In short, I'm really disappointed with the HB and the F-14. When I bought the module it did not have such problems. Yes, I know it's an early access module, but probably no one expected that HB would *add* such bugs to this module then without bothering to fix it and cause different problems with each update for 7 months. I wish I could see the future. If I had seen the current state of the module when I bought it, I would not have given even a penny. Anyways, i'll leave a simple tacview file (its a server-side file and i dont have track file, i had it disabled on my settings when this thing happened) and go. Apologies if it's too harsh, but couldnt say these things with a more soft language. desync.acmi

it has become a usual thing that aim54 gets bugged or rwr warnings disappears.. i wonder how long its gonna take to fix this time and what'll break next also, do you have a video record of this that u can share?

is this happening only in sp or mp too?