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.

You really need to read what it is I stated before you post something like this... although I'll give you the benefit of the doubt that you didn't see the edited version of my post that I added 2 minutes after the original, which included the details about radar lock and missile launch. Cheers

Just as the title says... In the latest patch, despite the RWR being turned on, I get no visual indications of radar lock or missile launch. The audible tones are working, but there are no corresponding visual symbols. This renders the F-16 nearly unflyable in combat scenarios... How did this get past the closed beta testers?

After educating myself and doing some test shots under "perfect" parameters, I retract my previous statement and agree that there is nothing to fix. My apologies. Thanks for doing what you do!

The loft parameters of the phoenix make no sense. I can launch a C missile at 40kft/mach1.1, but if the target is more then 30nm away, the missile lofts almost vertically, which significantly cuts the missile's top speed. That doesn't make sense... please fix this.

@BIGNEWY I'm still having the same problem in multiplayer as I originally reported in this thread. Any idea on when it will be fixed?

Wow. If this is really "correct as is", then I am blown away how this big of a change in radar logic and BVR workflow wasn't included in the changelog and illustrated in a tutorial video. Something isn't adding up here...

I have 2 questions for @NineLine and @BIGNEWY, but I have to set it up first... We all know that before this patch we could lock up a target in RWS the moment the radar detected the contact. Unless I am missing something, this has been a given (A2A radar logic 101 for those who have cared to learn) for as long as I have been flying in DCS (4 years now). Obviously, that has now changed for the Viper in this new patch, but I see that you guys have labeled this issue as "correct as is". Question 1: Given the fact that this is a pretty big change in A2A radar logic, why was it left out of the F-16 section of the changelog? Also, this is quite the change in BVR workflow in the Viper when committing on a bandit given that an entirely new parameter has been introduced: a delay between a contact appearing on radar and the distance and/or time afterwards to where you can lock that contact up on radar. Question 2: Why hasn't this new parameter in Viper BVR workflow been introduced and explained in a tutorial? Conclusion: If this is correct as is, then this entire bug thread constitutes a failure to communicate on your/ED's part. Can you guys please not leave future changes like this unaddressed? Thank you.

That is exactly what I see in multiplayer as well. Thanks for reporting!

This bug has been persistent throughout the EA period, and still exists despite the recent patch. I have replicated it many times. I am unable to attach the track file, as it is 75mb. Here is the scenario: I'm in the middle of a sortie and I take battle damage resulting in a single engine failure. I RTB on the good engine, land, engage APU, shut down both engines, and wait for the rotor RPM to read 0 on the A/C page. Then, I'll shut off the APU and battery, wait a few minutes, then request repair. I'll get the unable to repair/shut off your engines message, despite being fully shutdown. What's interesting is that on the in-game info bar, the battle-damaged engine will still show it spinning at around 44%rpm, despite having fully shut down the aircraft according to on board instruments. I'm not sure what is causing this desync, but it means that I am unable to repair the aircraft, and I have to reslot and start all over again from scratch. Please help. Thanks.

Thanks for the quick response, NineLine!