Jump to content

[CORRECT AS IS] locked target in FCR the target range and TA alt not appear in HUD


Recommended Posts

Posted (edited)

I try the instant action take off without A-A weapons,

 

I locked an A-A target in FCR but the F target range and letter TA target altitude never appear in the right side of the HUD

 

I only have the B letter for RNG to STRP, even with target locked in FCR

 

But in the same mission ( and it is not mission issue this happened also generaly if A-A weapons not loadout ) with A-A (CATM or AIM ) weapons loadout, the locked target gives in HUD the F target range but not TA altitude details.

 

The bug is -===when we lock in FCR we must get data F and TA in right handside of HUD even we have or have not A-A weapons. The FCR lock's the target not the A-A weapon.

 

 

Screenshot without A-A weapons Screen-200504-142733.png

 

Screenshot with A-A weapons Screen-200504-144331.png

Edited by Geraki
Posted

When the Viper was first released, you did get a range scale on the right side of the HUD along with an indication of relative speed (even without live A2A weapons) but for some reason, that changed a couple of updates ago. Now you must carry live missiles in order to get that HUD symbology.

[sIGPIC][/sIGPIC]

http://www.476vfightergroup.com/content.php

High Quality Aviation Photography For Personal Enjoyment And Editorial Use.

www.crosswindimages.com

Posted

Since your RADAR FCR locks the target the details from radar must display in the HUD, if not then you could have a reason for the TD box in the hud.

 

The lock is Radar associated and not missile associated.

Posted
Since your RADAR FCR locks the target the details from radar must display in the HUD, if not then you could have a reason for the TD box in the hud.

 

The lock is Radar associated and not missile associated.

 

Not in NAV master mode

Posted

you are wrong mate .....

 

Watch the video below ..and again the target lock is FCR dependent

 

in RL the pilot locks the target even in ACM or FCR the TD box remains in NAV mode until brake lock from the pilot that why the purpose of TD box in HUD.

 

Posted

It is my understanding that the "B" line in the lower right data block should show F010.0 e.g for a target 10nm away and not B030.0 e.g. for a waypoint 30nm away when there is an air to air radar target even in NAV mode.

 

However the TA value beside TD box on HUD I think is software dependent and might not be a feature on this DCS variant.

Posted (edited)
you are wrong mate .....

 

Watch the video below ..and again the target lock is FCR dependent

 

in RL the pilot locks the target even in ACM or FCR the TD box remains in NAV mode until brake lock from the pilot that why the purpose of TD box in HUD.

 

 

And you are absolutely right! TA in M tapes nowadays is shown under TD box. No DLZ because of no weapons left. You should see the F (FCR) distance to target..also in NAV. But also stpt number and distance.

Edited by Bouli306
Posted

Correct for TA altitude for DCS F-16 sim tape, wrong of DLZ you said I am in NAV mode, BUT in NAV mode you can have TD box and F target distance ... view the video end of discussion.

Posted (edited)
Correct for TA altitude for DCS F-16 sim tape, wrong of DLZ you said I am in NAV mode, BUT in NAV mode you can have TD box and F target distance ... view the video end of discussion.

 

I think i said in my last post that you were right didn't I? But the DLZ only shows when there is an actual missile on the jet or when you simulate one being there (as far as i know this can't be done in DCS).

Edited by Bouli306
Posted

Bouli306 my friend i am sorry .... :)

 

lets hope to be fixed in new update like some other like AIM 120 DLZ ,and ASEC circle in HUD and MFD, ACM slew mode .... e.t.c

 

 

kind Regards

  • ED Team
Posted
Bouli306 my friend i am sorry .... :)

 

lets hope to be fixed in new update like some other like AIM 120 DLZ ,and ASEC circle in HUD and MFD, ACM slew mode .... e.t.c

 

 

kind Regards

 

Hi

 

We see all of these but ACM slew mode, that will come later in EA.

 

thank you

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

  • ED Team
Posted

Hi all

 

We do not have the TA indication in our reference documents.

 

If you have information that states otherwise for an F-16C Block 50 operated by the United States Air Force and Air National Guard circa 2007 please let us know either here or via PM.

 

thank you

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

@BIGNEWY I speak about TD box and F target distance this is not correct as it is ....when pilot locks target in FCR the F details MUST show in the right-hand side of the HUD even in NAV mode. watch the RL video above.

 

about TA altitude YES this is correct as it is .

Posted

Let this be a lesson that introducing two or more issues in a bug report can result in the [CORRECT AS IS] label despite only one of the issues justifying that label.

Posted

you are correct about 2 issues reported i am sorry !!!!

 

The bug is when we have TD box in HUD even in NAV mode we must have F distance in the righthand side of HUD.

Posted
watch the RL video above.

 

Just be careful when referencing real world footage unless you know the exact model, as there are a large amount of different blocks operated by the U.S. For all we know that footage could be a Block 30 on a different tape.

REAPER 51 | Tholozor
VFA-136 (c.2007): https://www.digitalcombatsimulator.com/en/files/3305981/
Arleigh Burke Destroyer Pack (2020): https://www.digitalcombatsimulator.com/en/files/3313752/

  • 5 months later...
Posted

=====================This is not correct as is=============

 

The bug is when we have TD box of the locked-buged target in HUD even in NAV mode we must have F distance (target distance) in the righthand side of HUD. and not B STRP (streerpoint) distance.

Real Video pilot switch from ACM -locked target into NAV mode the radar target is still locked and the distance in F distance in the right side of the HUD

 

 

kind regards

Posted

It is not block related it is radar lock-related, but even that refere to T.O,F-16 Block 50 2007

 

It is not logical to have a RADAR locked aerial target in HUD and the distance shows the B STRP distance.

 

When lock dropped then the hud has the B distance

 

Block 40 video

 

Block 50

 

  • 2 weeks later...
  • Recently Browsing   0 members

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