Jump to content

Recommended Posts

Posted

Can anyone tell me what these numbers are? Clearly relating to a heading and range, but I'm not sure to what.

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Posted

Sorry, but no. The numbers just don’t work, even in the screenshot I attached.

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Posted

Relative bearing in 10s of degrees, range to target in nautical miles (or tenths if <10nm).

 

"33" would be "330" which is thirty degrees left of nose and "7.8' 7.8nm to target.

Posted

Sorry guys, I don't get it. In the attachment, I'm heading straight for the target, and the number says 32. How does that work out?

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Posted
Sorry, but no. The numbers just don’t work, even in the screenshot I attached.

 

I don't know why don't work. May be a bug? But that's what it is or should be.

 

Relative bearing in 10s of degrees, range to target in nautical miles (or tenths if <10nm).

 

"33" would be "330" which is thirty degrees left of nose and "7.8' 7.8nm to target.

 

Better explained :thumbup:

Posted

It is supposed to be bearing and range to tgt but looks to be off by quite a bit. Steerpoint data is so messed up right now.

Twitch Channel

 

[sIGPIC][/sIGPIC]

Virtual Thunderbirds, LLC | Sponsored by Thrustmaster

 

Z390 Aorus Xtreme, i9 9900k, G.SKILL TridentZ Series 32GB, 1080ti 11GB, Obutto R3Volution, Thrustmaster HOTAS Warthog, TPR, Cougar MFDs, FSSB R3L, JetSeat, Oculus Rift S, Buddy-Fox A-10C UFC, F/A-18C UFC, Tek Creations F-16 ICP

 

Posted

Looking at the image, the heading may be in degrees, which would align better with the direction of your aircraft in the screenshot, and there may even be a magnetic variation in there too.

 

maybe fly past the target and see how those numbers change. If the heading becomes a 3 digit number, then that might prove the above. if not, then I'm lost too.

 

If it is, and your heading doesn't equal the target's when you are flying straight at it, then maybe the difference could be explained by magnetic variation? Odd, but at least it would be an explanation

Posted (edited)
The distance part is a slant range, isn’t it?

 

As far as I can tell, no. Docs seem to go out of their way to call out slant range when they mean it. Also the NAV mode values in the same position are called "range" and are the 2D variety. Unfortunately all the example diagrams I've seen are at low altitude which makes the 2D and 3D ranges too hard to decide on those alone.

 

I tested DCS and it's giving the absolute true bearing to target and 2D range. Example I am approaching directly a target in NTTR which is 346 magnetic, e.g. 000 relative bearing. My true heading is 358 which is also what the HUD displays. It should say "00" not "358".

 

So, it's wrong. It's showing true heading in all three digits instead of relative bearing in two digit tens.

Edited by Frederf
Posted
Piggybacking on what Greyman said, the magnetic variation on NTTR is roughly 12°.

 

That would make the most sense, but isn't the HUD heading tape supposed to be magnetic and not true?

Posted

I just had a look at the EA manual. Unfortunatly it's not explaind there, but in the ccrp section you can clearly see, that these numbers have sometihng to do with heading and range to some kind of target marker. If it's a waypoint or the point where the tgp is looking, I don't know.

 

In some of the pictures ther is no variation in others there ist.

Posted

Thanks guys. After further investigation today, I can confirm that it is the bearing in degrees (not with a factor of 10 as suggested above) to the target, taking magnetic declination into account.

 

Not sure it is always working correctly, but that's another matter.

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Posted

A follow up here. It seems to me that the HUD is showing true heading and the CCRP indicator is showing magnetic which is consistent with the magnetic compass.

 

Surely, the HUD should be showing magentic as well? Is this a bug?

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Posted (edited)
It's not supposed to be true or magnetic. It's supposed to be relative bearing.

 

Sorry, I am talking about when bomb in line with target. Anyway, the HUD should not be showing true.

 

To be honest, I am giving up on this. There seems to be so many inconsistencies.

 

See attachment showing that the CCRP isn't showing relative bearing to target. It 12 degrees more than HUD, which was the same as the magnetic compass.

Edited by imacken

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Posted

I’m not sure what you are saying here, but I am saying that the CCRP data is not showing any kind of relative bearing to target, and the HUD is showing true heading which it shouldn’t be!

 

Both are wrong IMO.

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Posted
Piggybacking on what Greyman said, the magnetic variation on NTTR is roughly 12°.

 

True, but that still wouldn't account for the bearing being that far off.

System HW: i9-9900K @5ghz, MSI 11GB RTX-2080-Ti Trio, G-Skill 32GB RAM, Reverb HMD, Steam VR, TM Warthog Hotas Stick & Throttle, TM F/A-18 Stick grip add-on, TM TFRP pedals. SW: 2.5.6 OB

Posted (edited)

In the OP's image, his HUD tape reads roughly 020°, bottom-right of the HUD reads 32. And in the last image on the previous page, it again shows a difference of 12.

 

I'm not saying what should be present in that section of the HUD (true bearing, relative bearing, etc), only what it appears to be. If it's supposed to be relative bearing, then that's probably a bug.

Edited by Tholozor

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/

Posted

How do we know it's supposed to be a relative bearing? Where is that documented?

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Posted
As far as I can tell, no. Docs seem to go out of their way to call out slant range when they mean it. Also the NAV mode values in the same position are called "range" and are the 2D variety. Unfortunately all the example diagrams I've seen are at low altitude which makes the 2D and 3D ranges too hard to decide on those alone.

 

 

Agree that its very unlikely to be SLR, as that would require some angle computations using either a sensor or some kind of altimeter to compute the triangle. It's not that the range couldn't be SLR, just unlikely that it is.

System HW: i9-9900K @5ghz, MSI 11GB RTX-2080-Ti Trio, G-Skill 32GB RAM, Reverb HMD, Steam VR, TM Warthog Hotas Stick & Throttle, TM F/A-18 Stick grip add-on, TM TFRP pedals. SW: 2.5.6 OB

Posted
Sorry, I am talking about when bomb in line with target. Anyway, the HUD should not be showing true.

 

To be honest, I am giving up on this. There seems to be so many inconsistencies.

 

See attachment showing that the CCRP isn't showing relative bearing to target. It 12 degrees more than HUD, which was the same as the magnetic compass.

 

The other thing that is not adding up is the range to the designation in the numbers in question (assuming that's what it is) and the Slant range (F001.1) obviously don't add up. Look on pg 187 of the DCS F-16 Early Access guide. It labels everything except that bottom row. But clearly you can't have a slant range of 1.1nm and a ground range of 7.8nm.

 

The relative bearing adds up taking into account mag var, but not the range. Something's afoot at the Circle K, Ted

1589394683_CCRPEAguide.thumb.PNG.7895aba0eacb0b3835ad17cd0173e88d.PNG

System HW: i9-9900K @5ghz, MSI 11GB RTX-2080-Ti Trio, G-Skill 32GB RAM, Reverb HMD, Steam VR, TM Warthog Hotas Stick & Throttle, TM F/A-18 Stick grip add-on, TM TFRP pedals. SW: 2.5.6 OB

  • Recently Browsing   0 members

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