Jump to content

Recommended Posts

Posted

Prior to INS Alignment, the Lat Long Coordinates shown on the Persian Gulf F10 Map view for my aircraft don't match what is shown in the cockpit for Waypoint 0.

 

See the attached screenshots:

757904784_CockpitCooridinates.png.f8e97e910ad814bdbfe9cac20e676cb2.png

605643738_F10MapCoordinates.thumb.png.2d86824c8016f9b5150bb754935fb525.png

Posted (edited)

The coordinates shown on the data page are in lat/long decimal even though there is the apostrophe after the last two digits. You have to enter coordonates in lat/long seconds, the INS does not allow input if the last number is higher then 60.

It's really weird, i'll look for it in NATOPS.

Edited by Rex854Warrior

[sIGPIC][/sIGPIC]

Posted
Prior to INS Alignment, the Lat Long Coordinates shown on the Persian Gulf F10 Map view for my aircraft don't match what is shown in the cockpit for Waypoint 0.

 

See the attached screenshots:

 

Doesn't it just convert?

 

For example:

 

21/60 = 0.35 so : 24 13 21 = 24 13 35

Posted
Doesn't it just convert?

 

For example:

 

21/60 = 0.35 so : 24 13 21 = 24 13 35

 

 

Correct.

 

 

you can see what it is with the sign after the numbers.

 

 

N65°25.5' would be decimal minutes as depicted by '

N65°25'30" would be in degrees,minutes and then seconds.

 

 

 

both of these coordinates are the same Latitude.

Posted
Sure? Source?

 

Source: I fly it with INS switch at off position since it was released. Not a single problem.

 

Haven't tried A/G yet, maybe it affect that mode.

 

To be fair, I misread OP question, and I agree with other answers, it's just a different format.

Do not expect fairness.

The times of chivalry and fair competition are long gone.

  • 3 weeks later...
Posted

Looking at the NATOPS, all HSI displays shown in CH 24 use degrees, minutes, seconds, and NOT degrees, decimal minutes.

 

 

Maybe it's a software version thing?

System spec: Intel i7 12700k @ stock, ASUS TUF Gaming GeForce RTX 3080 Ti 12GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance LPX 32GB (2 x 16GB) DDR4 3200MHz C16, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), WD Black SN 850X 2TB NVME M.2 SSD (games drive), Thermalright Assassin Spirit 120 Evo Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS

Prev System spec (leaving here because I often reference it in my posts): Intel i9 13900KF @ stock,  Gigabyte GeForce RTX 4090 Gaming OC 24GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance RGB PRO SL 32GB (2 x 16GB) DDR4 3600MHz C18, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), Samsung 970 EVO 1 TB NVME M.2 SSD (games drive), Cooler Master ML360 Illusion CPU Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS, MFG Crosswind Rudder Pedals

Posted
Hi guys,

 

Natops doesnt state that, in fact it states that decimal minutes are cold default view in MC after 20x and seconds in MC before 20x, it can be changed IRL, not yet in DCS.

 

 

Thank you - maybe I should have done more than just look at the pretty pictures!

System spec: Intel i7 12700k @ stock, ASUS TUF Gaming GeForce RTX 3080 Ti 12GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance LPX 32GB (2 x 16GB) DDR4 3200MHz C16, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), WD Black SN 850X 2TB NVME M.2 SSD (games drive), Thermalright Assassin Spirit 120 Evo Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS

Prev System spec (leaving here because I often reference it in my posts): Intel i9 13900KF @ stock,  Gigabyte GeForce RTX 4090 Gaming OC 24GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance RGB PRO SL 32GB (2 x 16GB) DDR4 3600MHz C18, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), Samsung 970 EVO 1 TB NVME M.2 SSD (games drive), Cooler Master ML360 Illusion CPU Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS, MFG Crosswind Rudder Pedals

  • Recently Browsing   0 members

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