Jump to content

[FIXED INTERNALLY] Change HAFU symbology on radar page after changing ID(PLID)


Recommended Posts

Posted

I think I found a bug. Because the PLID function was added to the SA page after the last update, I checked the link to the HUD and the radar page. The track includes a simple mission, one F/A-18 on the blue side and one IL-76 on the red side (AWACS is not in the mission.). On the SA page I changed the target ID on the hostile. LTWS is active on the radar, and I see that the target is still unknow after placing TDC on target. If the target is locked with LTWS, the radar display the target marked as a hostile. If I target lock with STT, the target is again unknow although on HUD and SA page is marked as hostile.

 

 

https://drive.google.com/file/d/1WEo0GJH2ebXqx5M1NpDftE-5XU0nJvzt/view?usp=sharing

Posted

I just ran into this as well. Simple 1v1 from 60nm, no AWACS.

 

I set the target as hostile with PLID and when I placed the TDC on top of the contact (TUC) on the Radar page (LTWS enabled), it showed up as Unknown. What's more, the HAFU reverted to Unknown on the SA page as well.

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

  • ED Team
Posted

There were some fixes that missed this Open Beta, so it's possible that's what is happening here, as I watched the track on our dev build and each time you changed the PLID it changed on the radar page just fine.

 

I will leave this thread open, and let me know if you are still seeing it after the next update please.

64Sig.png
Forum RulesMy YouTube • My Discord - NineLine#0440• **How to Report a Bug**

1146563203_makefg(6).png.82dab0a01be3a361522f3fff75916ba4.png  80141746_makefg(1).png.6fa028f2fe35222644e87c786da1fabb.png  28661714_makefg(2).png.b3816386a8f83b0cceab6cb43ae2477e.png  389390805_makefg(3).png.bca83a238dd2aaf235ea3ce2873b55bc.png  216757889_makefg(4).png.35cb826069cdae5c1a164a94deaff377.png  1359338181_makefg(5).png.e6135dea01fa097e5d841ee5fb3c2dc5.png

Posted

Just to be clear, it shows up correct on the radar scope, but changes to the Unknown HAFU when it's TUC (under the TDC), with LTWS on. If that doesn't occur in your internal build, then it's good.

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

Posted (edited)

I think the issue here is when a HAFU is designated as L&S or DT2 or is under the cursor on the radar it essentially exists in its own bubble. Not only with its identification, but often the trackfile rank is also different - plus the already reported bug where the bottom HAFU isn't shown at all when cursoring over or designating.

Edited by Jak525
Posted
Just to be clear, it shows up correct on the radar scope, but changes to the Unknown HAFU when it's TUC (under the TDC), with LTWS on. If that doesn't occur in your internal build, then it's good.

 

This is unrelated to PLID and was present before it. It's pretty much as jak described, and I reported it to nineline. Unclear if that is fixed internally though.

  • Recently Browsing   0 members

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