Fropa

I am devastated by your immense suffering. I hereby dedicate this post to the innocent puppies that have been slaughtered by your logic.

It's better for an update to be right instead of rushed.

The FCR for the AH-64D can only be equipped by selecting a special option via the mission editor. This makes the FCR inaccessible in multiplayer, and requires server owners to go through each AH-64D slot individually in order to enable FCR usage. This requires a hotfix ASAP so that the client can equip the FCR through the rearm/refuel window. *I posted this in the multiplayer bugs section, but that post appears to have been ignored. Therefore, I am posting it here.

The FCR for the AH-64D can only be equipped by selecting a special option via the mission editor. This makes the FCR inaccessible in multiplayer, and requires server owners to go through each AH-64D slot individually in order to enable FCR usage. This requires a hotfix ASAP so that the client can equip the FCR through the rearm/refuel window.

I think this "server outage" is a blessing in disguise. We should be able to use what we paid for regardless of whether some server is working or not. Now ED can get to fixing this so that we never have this problem again.

The fact that you have to do that just to play something you already paid for is almost as ridiculous as you not realizing how ridiculous this is...

Not in multiplayer, it would seem...

There is no need for your toxicity. I have reported your post to the moderators. Have a wonderful day.

Please read and comprehend the entirety of my original post before replying to me. It'll save us all a lot of time. Thank you.

I genuinely appreciate you giving a blunt answer instead of beating around the bush. I do understand it's a process, and I literally do not understand anything beyond that, so I hope you can forgive me for prodding. Speaking of which, I am curious, does a lot of the closed beta testing involve testing things in large multiplayer environments?

Fortunately, I have a much better idea of what it is that I am asking for than you do. I would encourage you to not just read my original post, but to actually comprehend its meaning rather than making pretentious statements that distract from the issue.

2 weeks™

So back on January 27th, ED announced on the patch thread that the next update would be on March 1st. Then @BIGNEWY updated the thread to say, more or less, that "Yes there really isn't going to be a February patch update, the next one really is not going to hit until March 1st, please stop messaging me about it." Then March 1st came around, and we know the patch got delayed again. All I want to know is why has it been delayed? Especially after we went all of February without an update. I get that ED needs more time to test something, but what is it that needs more testing? I don't mind waiting for the next update, I just want to know what it is that I am waiting for. I hope that's not too much to ask...

I would amend this to say that any target performing any high G maneuver, especially in a look-down shoot-down scenario, automatically defeats the AIM-120. This is 100% reproducible in the multiplayer PVP environment. I would provide a track, but the 50mb upload limit makes that impossible for multiplayer tracks. Fortunately, it's not hard to hop on a multiplayer PVP server and see for yourself. Please fix this ASAP as this makes BVR, and especially WVR, with the AMRAAM practically impossible. Thank you.

https://drive.google.com/file/d/10ro1mjqL8V5jHAEemYxgGf-b-cacaRCM/view?usp=share_link As you know, multiplayer trackfiles are too large to post here. The link above was taken from Moonshine's post in this very thread. For what it's worth, all you need to do is hop in a multiplayer server and attempt BVR in the F-16 to see what the problem is.