reported SLANT RANGE B - TARGET SLANT RANGE F

[Geraki]

When we are in NAV master mode we have Streer- point Slant range , But in NAV mode if we have Radar A-A contact "bugged" the Slant Range B must be changed to F which become the TARGET SLANT RANGE.  

 

 

Edited September 7, 2021 by Geraki

[BIGNEWY]

HI,

 

which block and tape is the video from?

 

thanks

[Geraki]

The video shows possibly a block40 F-16 But....i have seen that in Block 50 too.

 

It is normal since we have Radar lock -> when we switch into the NAV mod without to drop the target in FCR, the target designator box schould be remain when we switch form A-A /Dogft into NAV mode. If the pilot drop's the FCR target then the target designator box disapper from the NAV HYD mode. 

[Geraki]

Please put the above topic into Wishlist!!

[Geraki]

Please change the notice - need track replay- i think it is a feature for W.I.P - in comparison with topic radar loose lock when switching from deferent A-A modes e.g locked in dogf and then switch into NAV mode. e.t.c

******When we are in NAV master mode we have Streer- point Slant range B, But in NAV mode if we have Radar A-A contact "bugged" the Slant Range B must be changed to F which become the TARGET SLANT RANGE.*****

 

Associated with topics 

 

 

 

Edited September 24, 2021 by Geraki

[Frederf]

HUD info window 10 is the same as HMCS window A-3. Most descriptions of helmet A-3 apply to HUD 10.

 

XXX is for DGFT/MSL/AAM/GUN when there's no valid range (ground range never valid for these modes)

M and range if manual range is a valid concept (e.g. 015 for 1,500')

F for FCR valid range

AG B R or P for slant range depending on BARO PR RALT selection and no higher priority sensor

F for FCR ground range

TGP laser range

AG IAM horizontal range instead of slant

 

Notice that the window 10 blanks accelerating on takeoff at ~70-90 knots and then remains blanked until the landing gear is raised.

 

100% sure that NAV mm and FCR tracking AA target slant range in window 10 is FCR range to AA target. The thinking is that you may be in a navigation setting like takeoff or finding the tanker where you absolutely don't want to select weapons and kill anyone but you do want to know their position so you don't run into them or anything. What I don't know is what happens if in NAV mm you switch FCR GM and say FTT some object. Will window 10 show FCR AG range in NAV mm?

[Geraki]

any update off te above?-SLANT RANGE B - TARGET SLANT RANGE F

 

Kind Regards 

 

 

[Noctrach]

On 9/14/2021 at 12:58 PM, BIGNEWY said:

HI,

 

which block and tape is the video from?

 

thanks

From the block 50CJ manual: Window 10 (slant range) should indicate slant range from the highest priority tracking sensor.

This is the FCR (in any mode) whenever an air contact is locked.The current DCS mnemonic (Bxxx) being present even if target is locked in NAV is incorrect, as this would treat the steerpoint/barometric elevation as the highest priority sensor even if FCR is SOI.

I can send you the excerpt in PM if needed, but I'm pretty sure you guys have this doc.

There's multiple HUD tapes on youtube with different blocks and tapes, all with identical behaviour to the description in the manual. This is not a "wishlist request" but a bug/incorrect/WIP implementation.

OP's video is a Block 40 with CCIP or later upgrade (JHMCS)

F-16N block 30, tape unknown, NAV mode with target locked showing locator line and radar range.

There's multiple F-16D fam flights like this, block and tape unknown, HUD in NAV, showing both locator line and radar ranging with bugged target.

 

Edited December 6, 2021 by Noctrach

[Frederf]

Example track which should show "F" as the slant range sensor source (AG, CCRP, FCR GM primary sensor).

F16 Slant Range F.trk

[Geraki]

i hope to be fixed soon.

[Geraki]

Track replay was attached , please re-evaluate

 

Kind Regards , lets make the DCS F-16 realistic as it's get!!! 

[Geraki]

The same bug occurred when you lock a Jammed target in FCR in NAV mod , we have the bugged" the Slant Range B  and wrong miles instead of   F which become the TARGET SLANT RANGE.  

 

 

 

 

 

Edited February 4, 2022 by Geraki

[Noctrach]

Gonna bump this up since there's a trackfile and multiple sets of evidence attached but thread status has not been updated yet

Official documentation and pretty much all online video evidence support the FCR being primary sensor for HUD window 10 if target is locked for both NAV and A2A master modes, yet in-game behaviour is still different as of latest open-beta release. Any info on the team's stance for this item? @NineLine

 

[NineLine]

Thanks for the track, I will check it out soon.

[NineLine]

Just checked, this is already in progress internally, so already reported and known. Thanks.