Jump to content

Recommended Posts

Posted

Anyone noticed the Shkval Targeting sight as seen through HUD does not seem to always tally with the cursor position as shown on the map display of the ABRIS (with connecting yellow line from Ka)?

 

When it does not match up, usually the map's cursor would be further away than where the target sight actually is resting on as seen through the HUD. This posed a problem when snapping to a captured target point in memory, as it would move the sight to a wrong location.

 

Looks like it is a bug.

Posted
Anyone noticed the Shkval Targeting sight as seen through HUD does not seem to always tally with the cursor position as shown on the map display of the ABRIS (with connecting yellow line from Ka)?

 

When it does not match up, usually the map's cursor would be further away than where the target sight actually is resting on as seen through the HUD. This posed a problem when snapping to a captured target point in memory, as it would move the sight to a wrong location.

 

Looks like it is a bug.

 

Storing a target point with the Shkval/PVI doesn't capture target elevation data. (I don't think the forum ever determined if this was correct behavior or not; it's still in 'we don't know' territory as far as I'm aware.) In the absence of elevation data, the Shkval makes assumptions about the target's elevation that may not hold. I haven't done enough mountainous flying lately, but I think that saving targets with the datalink does keep elevation data and slew back onto the saved point correctly.

 

Just another odd little Russian hardware idiosyncrasy.

Black Shark, Harrier, and Hornet pilot

Many Words - Serial Fiction | Ka-50 Employment Guide | Ka-50 Avionics Cheat Sheet | Multiplayer Shooting Range Mission

Posted

I'm not sure if the issue I raised is fully understood, but I'm going to test if the issue could be that when the Shkval is uncage when the Ka is pointing high in the sky, the map cursor tends to be positioned way off away to far part of map, resulting in mis-match in position between sight reticle on HUD and map cursor. Maybe going to lower altitude and uncaging only when nose pointed towards ground may help synchronise the position of targeted point.

Posted (edited)

What Isegrim and Bad CrC said should solve your problem ;)

 

When you see an actual distance value in your Shkval after lasing then the Shkval cursor on the Abris should be on the correct spot as well.

Edited by QuiGon

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

DCS Panavia Tornado (IDS) really needs to be a thing!

Tornado3 small.jpg

  • Recently Browsing   0 members

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