Jump to content

SOLVED: new RWR behavior after the update?


Recommended Posts

Posted (edited)

Hello

the RWR behavior and symbology got updated

I'm confused, now the circle thing around an airborne threat which is locking you no longer exists, so now you will have no idea which threat is locking on you, but the latest manual still says there will be a circle around the emitter indicating who is locking you, so is this a new bug or the manual is wrong?

and the sound now is far less warning not only because of a much lower volume but it also only beeps for several seconds instead of the constant beeping... is this more realistic?

null

image.png

image.pngnull

image.png

Edited by zlm63682
Posted (edited)

I'm a bit confused as well.  I have a test mission with an E-3, and normally when I turn on the RWR I get a beep right away from it.
Now there is only silence, while it shows up on the TEWS.

Edited by Mud
typo
Spoiler

W10-x64 | B650E Gigabyte Aorus Master | AMD Ryzen 7 7800X3D | Noctua NH-D15

G.Skill Trident ZS Neo DDR5-6000 64Gb | MSI RTX 3080ti Gaming X

Asus Xonar AE | TM Hotas Warthog

MFG Crosswind pedals | Valve Index

 

  • zlm63682 changed the title to new RWR behavior after the update?
Posted
On 2/22/2024 at 6:49 PM, Mud said:

I have a test mission with an E-3, and normally when I turn on the RWR I get a beep right away from it.
Now there is only silence, while it shows up on the TEWS.

Following SME feedback, new A/A contacts in search (Nails) have no "new guy" tone.

i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440

Posted
53 minutes ago, Ramsay said:

Following SME feedback, new A/A contacts in search (Nails) have no "new guy" tone.

Cheers for the info, Ramsay.
However, in a test I just flew,  I'm also not getting a "new guy" tone for an SA-2 and SA-3.

Not seeing many others comment on the same issue here though, so I will try to wipe the F-15E installation files and have them re-downloaded.

Br,

Mud

Spoiler

W10-x64 | B650E Gigabyte Aorus Master | AMD Ryzen 7 7800X3D | Noctua NH-D15

G.Skill Trident ZS Neo DDR5-6000 64Gb | MSI RTX 3080ti Gaming X

Asus Xonar AE | TM Hotas Warthog

MFG Crosswind pedals | Valve Index

 

Posted
4 minutes ago, Mud said:

Not seeing many others comment on the same issue here though, so I will try to wipe the F-15E installation files and have them re-downloaded.

The Razbam F-15E discord was/is full of RWR discussion about the changes, AFAIK from the SME replies, the new behaviour is correct i.e. matches the real.

  • Thanks 2

i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440

Posted (edited)
3 hours ago, Ramsay said:

The Razbam F-15E discord was/is full of RWR discussion about the changes, AFAIK from the SME replies, the new behaviour is correct i.e. matches the real.

Does that mean we will have no way to identify which AA threats are currently locking on us if there are multiple of them?

 

-----------------------

never mind i just found the discord server.

Edited by zlm63682
Posted (edited)
1 hour ago, zlm63682 said:

Does that mean we will have no way to identify which AA threats are currently locking on us if there are multiple of them?

My understanding is that -

• NEW locks generate a warning tone and the identified threat aircraft symbology should flash/blink for 5 seconds on the TEWS.
• The previous behaviour, where a circle was drawn on the TEWS aircraft that was locking us up, was unrealistic.

I haven't tested this in game.

Edited by Ramsay

i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440

Posted
14 hours ago, dorianR666 said:

so after 5 seconds, there is no way to know which aircraft is locking me?

thats a weird design...

SME just said in DC that it will get fixed in next patch/hot fix

it will be a bracket around the AI threat who is locking on you

  • Like 1
  • zlm63682 changed the title to SOLVED: new RWR behavior after the update?
Posted
15 minutes ago, zlm63682 said:

SME just said in DC that it will get fixed in next patch/hot fix

it will be a bracket around the AI threat who is locking on you

Does this mean that we will be flying with bad indications for a month or two?

  • Like 1

:pilotfly:

Posted
1 hour ago, Miro said:

Does this mean that we will be flying with bad indications for a month or two?

Wow... is that right? This was my worry about the new 'unified dcs version' with patching in 6 weeks gap.

  • Like 2
Posted

I am curious about the sound as well in that is it correct behavior that the launch alert only sounds for 5 seconds and then remains off for that tracking launch? I had always relied upon the sound to know when I finally broke lock with maneuvering / terrain masking. Just curious so that I can set my expectations correctly. It is what it is.

  • Like 1
Posted
On 2/25/2024 at 6:11 AM, Miro said:

Does this mean that we will be flying with bad indications for a month or two?

It’s DCS. Might longer than 2 weeks. Remember, it early access or however they always phrase it!

Posted
12 hours ago, Str][ker said:

I am curious about the sound as well in that is it correct behavior that the launch alert only sounds for 5 seconds and then remains off for that tracking launch? I had always relied upon the sound to know when I finally broke lock with maneuvering / terrain masking. Just curious so that I can set my expectations correctly. It is what it is.

the sound alarming logic is correct, however the tone might be adjusted by a little bit in later updates.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...