[REPORTED]INS Align / HSI No longer works with Litening pod open beta update

Sounds familiar... :(

Use update TCN. Its only one problem. System not have start position. How in AV-8B and F-14. It is necessary to do coordination through known points.

I have the same issue cold starting at Nellis AFB, I have not tried without the tpod yet but with it I cannot get alignment and no map shows up.

When I start on the ramp hot or in the air the map shows and alignment is fine. I'll get a track file a bit later when I have time.

https://imgur.com/Kq1tyL1

Thanks that works well.

Good work around! Thanks!

No MAP on DDI since last patch

I no longer have a map overlay on my botton DDI since the last patch

Also, if I equip the TPOD, I get a weird flir like image where the map should be

I notice that the higher zoom levels do the half a map thing. If i zoom to 80 or 160 ots ok.

Similar behavior with zoom can be seen in the Mission planner or F10 map when in MAP mode. Not sure if the two are linked at all. I've seen it happen in the Harrier as well, so there could be a link.

Merged threads.

 

If you are having trouble with the map it is probably due to an INS issue,

try the steps below it should help

That didn't work for my starting from CV. The workaround for me is change the mission to hot start and everything is good

I have no moving map: multiplayer cold start on Stennis - autostart. (date 2019)

edit: 2nd time also don't have map with TGP, stennis is anchored

EDIT: if this corrected, please correct also "ins to nav" before "parking brake release"

Anyone else having issues opening up the SA page too? I believe its related to this INS issue. Whenever I try to open the SA page it crashes my game completely..

Ive even tried reinstalling the module.. Its really frustrating.. My crash file is corrupt for some reason too.

I havent seen this, is it generating crash logs and such?

I just checked the logs, and no there isnt any that was my mistake.. If this happens again i will post the TRK file. I have noticed that it happens when my INS is not aligned and i switch to NAV without getting it aligned properly. Then I click that scary SA page that sends me to desktop.

F/A-18C HSI Map Bug After 2.5.5.34108

After the release of the TGP to the F/A-18C I have not been able to get the map to work at all. The HSI work fine as well as the FLIR, but the map looks like what is is in the image.

This Image shows i have the TGP mounted on the CenterLine

i just had the same issue.

no map on HSI with Tpod attached

i can see map on hsi when i use editor with hot start or cold start (auto start)

i don't see map on mp servers in any case

INS CV/GND, AND WAIT +3 MINUTES AND MAP SHOULD APPEAR!

Ownship incorrect position?

Hello,

So today I got on Buddyspike Caucasus for some ground pounding on a FARP that is suppose to be 50ish miles away (tuapse), I imput its coordinates select wp1 and it shows about 200nm... So ok I must have typed it wrong, double checked the coordinates, tripe, checked it 4 times, it was correct.

So I think alright disregard that I'll just find it visually, and visually found it I did, located the targets on my TGP and for my surprise when I set them as target they show as beeing 200ish miles away...

Now that's confusing, I have alinged my INS as usual then set it to NAV (not sure if even matters at this point in EA but I do it anyways)

It's just like the plane though it were somere different entirelly, have many many hours on the hornet, never had that happen before

Track on link (too big to upload here) https://www.dropbox.com/s/qrfpeznirliehhl/BLUE-FLAG.1052-CTLD-Hornet-Red-Mirage-Blue.miz-dynamic-20190809-160440.trk?dl=0

It's a known issue. There's a workaround here

https://forums.eagle.ru/showthread.php?p=3996452

Ahh cool, thanks! Will try if happens again, was the first occurance in many flights this patch

Its the mission year for me. Had two missions, one set in 1987 the other in 1989. Was doing my head in as to why I couldnt align the Hornet, carrier and land. Waited up to 5 min before switching to Nav. Worked fine for me earlier on Persian Gulf (2019), but not in the those two 87 and 89 Caucasus missions.

Then switched the 1987 one to 1997, and voila. After timer hitting 1m30 in the align, I switch to Nav and boom, map.

Also, not only a missing map issue. It had no idea where it was. Setting a waypoint would be 384nm away (was 100nm away), and wrong direction too, when it was 1987.