Jump to content

INS not working in F18 since update


Go to solution Solved by rob10,

Recommended Posts

Posted

Since the update 2.9 i noticed that my INS / GPS is not tuned well. After proper start-up with STD HDG etc (which normally works well for me) it does not align after flip the switch to IFA. It then suddenly lost its 'mind'. I waited for alignment of course and "OK" sign.

So i cant fly on TACAN etc at the moment.

  • ED Team
Posted

just tested also, not seeing any problem. 

Maybe terrain / mission specific? Check the mission date also. 

need to see a track replay example. 

thanks

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

I just tried to get the error but it was now working. Maybe i was starting up too much at same time. For now im good i think. I try to just start engine and align and not flip too much switches.

Posted

Ive also just encountered this, got to about 3 minutes and INS stops counting down and just flashes, reset the INS sequence 3 times and just sat at 0.00 flashing. Turned INS to IFA and it started the countdown and eventually worked.

Posted (edited)
10 hours ago, HE5405 said:

Ive also just encountered this, got to about 3 minutes and INS stops counting down and just flashes, reset the INS sequence 3 times and just sat at 0.00 flashing. Turned INS to IFA and it started the countdown and eventually worked.

Yes the flashing at 0:00 is just a matter of waiting a minute and then it starts a countdown from 90 to 0,5 OK. So just wait 1 or maybe 2 mins.

 

I found that my problem with INS was not so much INS that lost calibration but i think it had to do with TACAN channels that were not found. I noticed that when i entered a TACAN code that does not exist, the compass starts spinning as well. 

I guess there is/was something wrong, in the server that i play in, with TACAN. I always get the spinning when trying to find a tanker or the carrier. I'll adress that there.

 

 

Edited by Michel0079
Posted (edited)
1 hour ago, Michel0079 said:

Yes the flashing at 0:00 is just a matter of waiting a minute and then it starts a countdown from 90 to 0,5 OK. So just wait 1 or maybe 2 mins.

 

I found that my problem with INS was not so much INS that lost calibration but i think it had to do with TACAN channels that were not found. I noticed that when i entered a TACAN code that does not exist, the compass starts spinning as well. 

I guess there is/was something wrong, in the server that i play in, with TACAN. I always get the spinning when trying to find a tanker or the carrier. I'll adress that there.

 

 

 

You should post a track, because I'm getting the INS to align even then I use a nonexistent tacan freq.

Edited by BarTzi
  • Solution
Posted
5 hours ago, Michel0079 said:

Ok well the compass is spinning. I dont know if that is the same thing as "not getting aligned". For who wants to study a track, i post one hereby.

In the end of the track i tune on a non existant TCN and an existent one, of the carrier.

No, TCN compass spinning is NOT related in any way to INS.  When the TCN is spinning that means that it is powered ON but has no valid signal coming in (ie out of range of tuned TCN, wrong TCN freq entered etc).  It was reported fixed in today's hotfix, but in the 1st version of 2.9 if you were in MP and didn't have Voice Chat checked in both client and server you got a really restricted range (like 20 nm).

  • Thanks 1
Posted
1 hour ago, rob10 said:

No, TCN compass spinning is NOT related in any way to INS.  When the TCN is spinning that means that it is powered ON but has no valid signal coming in (ie out of range of tuned TCN, wrong TCN freq entered etc).  It was reported fixed in today's hotfix, but in the 1st version of 2.9 if you were in MP and didn't have Voice Chat checked in both client and server you got a really restricted range (like 20 nm).

Thx for the info. I indeed had voice chat turned off since it gave me a ping of 400 and i got kicked 😌. Good the update was quick.

Posted
20 minutes ago, Michel0079 said:

Thx for the info. I indeed had voice chat turned off since it gave me a ping of 400 and i got kicked 😌. Good the update was quick.

TCN had reduced range, but it still has nothing to do with your issue with the INS.

Posted
25 minutes ago, BarTzi said:

TCN had reduced range, but it still has nothing to do with your issue with the INS.

Well i thought it was INS but in fact it was the "TCN bug". So it is solved now.

  • Recently Browsing   0 members

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