Jump to content

[FIXED INTERNALLY]Misslie flyout symbol does not correct for azimuth change


Harker

Recommended Posts

The missile flyout symbol does not correct for the target's azimuth change on the radar scope, either because of ownship or target maneuvering.

 

If you launch a missile on the L&S and change heading yourself, the L&S correctly moves on the Radar page to reflect the change in aspect between ownship and target. The flyout symbol does not follow the L&S symbol's movement, instead it flies straight ahead on the Radar page.

 

If you launch a missile and keep your current heading, but is flying at an angle different than 0 or 180 relative to you, it's azimuth on the Radar page correctly changes. The flyout symbol still flies straight ahead on the Radar page.

 

See attached tracks and screenshot. The tracks use STT from RWS and AACQ, but the same behavior is present in TWS as well.

 

Tested on Open Beta 2.5.6.43931 (latest), PG map.

Screen_200227_223323.thumb.png.a191758f7d6f49f523924b5024ab9298.png

Flyout symbol azimuth bug.trk

Flyout symbol azimuth bug_2.trk

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3
-
i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro

Link to comment
Share on other sites

I've noticed a similar thing. But sometimes when I launch multiple AIM-120s in TWS, some of them change azimuth on the radar display to match their target, and some remain straight ahead per the screenshot above. Not sure why or how to reliably reproduce it though.

Link to comment
Share on other sites

I also noticed that if I drop the lock and reacquire it (with AACQ, for example), sometimes the symbols will correct to the new azimuth upon reacquisition, but then stop correcting again.

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3
-
i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro

Link to comment
Share on other sites

  • 1 month later...

Bump. This was partially corrected recently for TWS/LTWS launches (good job, devs!), but the bug still appears for launches in STT.

I'm also wondering if it's related to another bug, where the HAFU of a target locked in STT doesn't update smoothly, even though the track should be getting constantly updated, yet the HAFU is moving smoothly in TWS/LTWS via extrapolation between updates.

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3
-
i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro

Link to comment
Share on other sites

This is already fixed internally, sorry, I didn't notice this thread
For STT as well? Good, hope to see it in an update soon. Thanks for the update, Santi.

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3
-
i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro

Link to comment
Share on other sites

  • Recently Browsing   0 members

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