Description

Incoming Missile Alert is broken. After you get locked by another tank, helicopter or Jet it gives a single short beep when the mission is fired from the enemy vehicle. After thats its completely silent until the missile impacts. Their was a couple of scenarios where it worked as before but I dont know how to reproduce that. It seemed long range AA fired from A Buzzard gave proper incoming missile warning but All 3 long range aa missiles missed even though enemy pilot had solid lock and I was in a autohovering posistion and didnt even fire flares. When the enemy pilot switched to close range AA and fired I got a single beep before impact.
This is heavily effecting game modes like KOTH where radar use is essential.

Details

Severity

Major

Resolution

Open

Reproducibility

Always

Operating System

Windows 10 x64

Category

Other

Steps To Reproduce

Step 1: Spawn A kajmin and a Blackfoot.
Step 2. Fly up and away
Step 3: At approx 3km have the blackfoot lock the Kajmin and Fire
Step 4: Watch the radar. You will hear a single beep.

Like described above this almost always happen except for a few exceptions. Why it worked normally in those instances im not sure about.

Additional Information

Tested in Sandbox mission.

I have video of all testing and can be uploaded on request though im choosing not to since the bug is so easy to reproduce.

Im not sure how to provide a better repro but the basics is just flying around with different helicopters or jets and then having someone lock on to you with AA and fire MANPADS, Jets, Helicopters or ground vehicles.

Feel free to ask any questions and I will answer them to the best of my abilities.

Still the same scenario as prior to the hot fix patch 1.66; AA missile alert within A-164 would announce an initial AA/AAA launch with one or two tones, then silence until impacted with the AA/AAA missile.

@rogerx
Please make sure you have the latest version of the game installed and don't forget to verify the integrity of the game cache after the update.

If the issue is still present, please try to provide some more info about the issue, the first issue was hard to pinpoint as it seemed pretty random, if the issue is still there, it might be something, that is even more random which is hard to reproduce, so any closer info about the situation when this does happen will help us greatly.

I'll verify integrity, as a last resort as I've never had a problem in the past except during initial alpha/beta releases.

I'll also provide the name of the multiplayer server. Could be some scripts are also interfering or using an old dysfunctional method. (The multi-player server is a Tanoa map co-op server. Pretty much the only popular Tanoa co-op map around this region, and will provide the exact name later.)

On the flip, this server's map PBO scenario file is locked to prevent extracting. They're using something called mikero PboDll, after examining the pbo header using hexedit. I, myself, despise encryption/scrambling due to deterred debugging and help from the community. (Pretty stupid idea, unless all a person wants is money in life.)

If nobody else provides any further information or duplicate bugs (or you're not seeing this problem with the Blackfish), then I'll have to assume it's related to the MAP PBO scenario file.