INS long alignement and short alignement

[jef32]

Hi

I don't understand: When I choose the short alignment, when the alignement is done, I switch on NAV and the HUD displays in the right down corner the distance to the selected waypoint. If I choose the NORM alignment, impossible to display this information on the HUD after the alignement is done and I've switched on NAV. I don't understans why ?

Edited March 30, 2023 by jef32

[Furiz]

51 minutes ago, jef32 said:

Hi

I don't understand: When I choose the short alignment, when the alignement is done, I switch on NAV and the HUD displays in the right down corner the distance to the selected waypoint. If I choose the NORM alignment, impossible to display this information on the HUD after the alignement is done and I've switched on NAV. I don't understans why ?

 

If you didn't Confirm coordinates at the first 2 min of Norm alignment it will mess up, you have to press enter on both Lat and Long when doing Norm alignment.

 

If its something else, post a track.

[skywalker22]

19 minutes ago, Furiz said:

If you didn't Confirm coordinates at the first 2 min of Norm alignment it will mess up, you have to press enter on both Lat and Long when doing Norm alignment.

 

If its something else, post a track.

uff, I completely forgot about that too. thx so much.

[jef32]

Thank for having informed me.

[jef32]

I've made some tries and I have the issue. I press enter after the end of alignment for the Lat, the Long and the Alt and it's the same.

[Furiz]

5 minutes ago, jef32 said:

I've made some tries and I have the issue. I press enter after the end of alignment for the Lat, the Long and the Alt and it's the same.

Not after the end, at the start of the alignment.

Start watching at 2 mins:

 

[jef32]

Ok, thanks ! I didn't know that I must press "enter" before 2 minutes after the beginning of alignment, for the LAT and LNG but I've made the try as shown in video but the issue is still here.

But there is something else that I don't understand: The first steerpoint ( number one ) isn't the start place but a steerpoint already in flight. The start place is the number 0 in the ME but the DED shows "1" in its right upper corner. So at this time, is the DED showing the "1" steerpoint parameters or the actual parking place parameters ?

Edited April 1, 2023 by jef32

[Lace]

1 is the selected 'To' SP.  It is slightly confusing that it is shown on the DED INS alignment page, as it is not the position of SP 1 which you are entering, you are entering the current location of the aircraft (SP zero).

[jef32]

Thanks for this tip. For altitude, I've understood that I must set my altimeter in first.

[Lace]

Just now, jef32 said:

Thanks for this tip. For altitude, I've understood that I must set my altimeter in first.

Yes, Batumi only has an elevation of 37ft IRL.  Every millibar of pressure setting is approx 30ft change, so it won't take much deviation from a ISA to put you on a 'negative' altitude.

[jef32]

Ok, I think I've found where's the issue: My mission with F-16 has been done in first for an other plane, The mirage 2000. When I've bought the F-16 recently, I've just replaced the Mirage 2000 with the F-16. And this method causes bugs in the INS Alignment. I've made a new try with the F-16 in a new mission and this time, all was quite OK and I have my HUD displaying distance to the waypoint with a normal assignment.

 

Thanks for your help

[jef32]

To add to my previous message, it's a little bit more complicated. My DCS is heavily modded. A long long time ago, I had prepared for the Caucasus, a lot of airbases and airfields models including officials DCS items and freeware mods, and when I wanted to create a mission I was using these models. The missions I have already done with these models are working properly yet if I don't try to modify them. But if i try to include some of these models in a new mission, the mission don't launch or don't save and its value in bytes is o. I have identified what models I'd made were causing issue if I tried to use them in a new mission, but If I try just to change the plane in a mission made already with these models, the mission works but the terrain datas are false and that's what I've made with the F-16. I took a old mission for the Mirage 2000, heavily loaded all around the map with all the models I've made and I've just replaced the Mirage 2000 with the F-16 and tha's why it was impossible for the INS to work properly. I've noticed that it was even impossible to set the altimeter of the F-16. This one indicated me a false negative altitude, even on the maximum set (31mm/hg). So in fact, I was doing the mistake to not press enter at the good times during alignment but after that, when I've tried on NTTR map and that the HUD was displaying the distance to the waypoint after a long alignment and wasn't displaying it on a Caucasus mission, I understood that the issue whas caused by the map and all I had put on it. Since I have erased the models causing issue and replaced by the new ones I've made ( Sochi and Senaki) and all became normal.

Edited April 5, 2023 by jef32