Jump to content

Recommended Posts

Posted (edited)

The difference in heading from NAV mode then switching to A/G mode is an old bug from DCS ver 1.2. It doesn't always happen though. I'm surprised this has not been fixed for sooooo long.

Edited by Winston60

Posted

I have realized that you have to let the plane time enough so the INS correctly align... It seems like the NAV and combat modes doesn't use the same inertial reference.... You can follow how the difference is getting closer by switching between nav and any combat mode (for example, press 1 - 7 - 1 - 7..... Etc etc)

 

In dont know if this is intended to work like this... But in real life it tooks up to 7 minutes to allign the nav system (IR) of an airbus a320 (i work as engineer in this plane).

Intel i5 11700F + H80 | 4x4GB 3200mhz RAM | AORUS ELITE B560M | Samsung 850 PRO SSD 256gb| KINGSTON SA400 480GB SSD | WD 500GB | Gigabyte GTX 1070 8GB | Antec 1200 PSU | Thrustmaster Warthog HOTAS and homemade panels and rudder pedals | 24" Samsung T24C550 @60Hz 2ms | Opentrack 3 led clip

Posted

I flew in a 1.5 hour multiplayer mission recently. At the end my nav hud heading was still massively different from the heading shown on my A/G hud mode. :dunno:

 

No change for me since sometime in ver 1.2

Posted
I have realized that you have to let the plane time enough so the INS correctly align... It seems like the NAV and combat modes doesn't use the same inertial reference.... You can follow how the difference is getting closer by switching between nav and any combat mode (for example, press 1 - 7 - 1 - 7..... Etc etc)

 

In dont know if this is intended to work like this... But in real life it tooks up to 7 minutes to allign the nav system (IR) of an airbus a320 (i work as engineer in this plane).

Yes, it's normal, the alignement is ~3 min on the 25T.

The problem is that with a non aligned INS, half the modes of the HUD are still correct when none should be.

Posted (edited)
Yes, it's normal, the alignement is ~3 min on the 25T.

The problem is that with a non aligned INS, half the modes of the HUD are still correct when none should be.

 

I think we should get an answer frim the devs... Maybe this is meant to be like that... Maybe not...

But as you say the best is to wait that 3 min....:thumbup:

Edited by aap_flanker

Intel i5 11700F + H80 | 4x4GB 3200mhz RAM | AORUS ELITE B560M | Samsung 850 PRO SSD 256gb| KINGSTON SA400 480GB SSD | WD 500GB | Gigabyte GTX 1070 8GB | Antec 1200 PSU | Thrustmaster Warthog HOTAS and homemade panels and rudder pedals | 24" Samsung T24C550 @60Hz 2ms | Opentrack 3 led clip

  • 2 weeks later...
Posted
Yesterday I flew Su-25T again, and noticed that the mistake between the mode seems fixed. However, it still feature a 7 degrees difference so i'm suspecting one of the mode doesn't take magnetic drift into account.

It might be possible that some of them display the true heading.

[sIGPIC][/sIGPIC]

  • 1 month later...
Posted

I often noticed the hud heading tape is not showing the same heading as the compass. It seems to be avoided if you wait long enough on the ramp before taxiing. There is no mention of the necessity to wait for INS alignment in the su-25t manual that I can find. Would be nice to have this alignment time verified by official word.

GPU: PALIT NVIDIA RTX 3080 10GB | CPU: Intel Core i7-9700K 4,9GHz | RAM: 64GB DDR4 3000MHz
VR: HP Reverb G2 | HOTAS: TM Warthog Throttle and Stick
OS: Windows 10 22H2

  • Recently Browsing   0 members

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