Jump to content

Recommended Posts

Posted

Track attached. I slew the HUD TDC cursor, ensuring the radar is in AGR. I look back and forth from the HUD cursor  and the FLIR which is slaved to the designation. You can see that the designation is always below the actual cursor dot, and if the cursor is off the nose to the left, the cursor is to the right of the designation and vice versa. I also try inside and outside of active pause, and try different perspectives and zoom levels with my TRACKIR and slow zoom and the results repeat every time.

 

I would expect, especially in active pause, that the cursor and the designation point are co-located.

 

This holds true (shown in track_2) when designation is done the other way around, i.e. you designate with FLIR and inspect the diamond location in AUTO and find the diamond is offset in the same way.

Hud_cursor_bug.trk Hud_cursor_bug_2.trk

  • ED Team
Posted

The HUD cursor is not as precise as the FLIR designation, it is often only used to get the designation in the area of the target, I will ask the team for more information. 

 

thanks

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal

Posted
The HUD cursor is not as precise as the FLIR designation, it is often only used to get the designation in the area of the target, I will ask the team for more information. 
 
thanks
The HUD cursor is fairly precise IRL, as it can be used for targeting and INS updating. Not every Hornet carries a targeting pod all the time and they can employ dumb bombs in AUTO just fine. It may not be accurate enough for JDAM employment, but the FLIR isn't either for the most part, IRL.

But its sensitivity is not the point here, it should always point exactly at the designation, since the MC draws it exactly where it determines the designation to be, using the INS and perhaps other sensors, such as the FLIR or A/G radar. The limiting factor, if applicable, should be the HUD resolution.
  • Like 4

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

It should be fairly precise and together with corrected slewing relatively effective using AUTO and unguided munitions. For reference:

 

Posted
On 10/6/2021 at 7:51 AM, BIGNEWY said:

The HUD cursor is not as precise as the FLIR designation, it is often only used to get the designation in the area of the target, I will ask the team for more information. 

 

thanks

That would be a problem of accuracy, not precision. The cursor is always above the designation exactly the same way every time, so the system as currently implemented is precise, meaning it is exactly inaccurate the same way every time. This almost always indicates a bug.

Also, TACMAN indicates using the HUD to refine the point in almost all cases, and never once mentions it for areal use. I think that's how DCS players use it, but that's because with the current slewing implementation that's all it's good for. According to documentation and users like @IvanK, this is not correct and the HUD should be uses to refine the aim point all the way to release.

Posted (edited)

As in the Bug post slewing to +-1mill is achievable IRL. In DCS the best you can achieve is about 9 mills.

Edited by IvanK
  • Thanks 1
  • Recently Browsing   0 members

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