[REPORTED] 2.5.5.31917 - INS and Waypoint Issue

[boscoh]

There's two things going on here:

 

 

Issue #1 - "INS - WAYPOINTS - HOT START.TRK" - the waypoint distance and altitude is incorrect. You can see it shows in thousands of miles away, and the altitude at 2000m. You can view in the mission editor and see the waypoint is very close and at ground level. This mission was created in this version of OB. I have also tested with missions from 2.4 to the same effect.

 

Issue #2 - "INS - WAYPOINTS - COLD START.TRK" - Despite following checklist procedure for INS alignment, INS will align to 0.5 OK but never move past that. When you go into HSI > DATA > A/C, you'll see the INS has the correct info but for some reason your position on HSI while in alignment mode never updates from 0 degrees N/E. You also can never enable the moving map, probably because of this. It looks like actual INS works because your heading tape updates correctly with your aircraft.

 

EDIT - added workaround - this worked for ME - if it doesn't work for you please let us know. Make sure you are working with a clean/repaired DCS and NO MODS running.

To resolve the issue (workaround):

 

1. Edit a mission where the INS does not work and waypoint distance is wrong. This mission should have a date that is relatively modern, the default ME date of June 1 2011 works fine.

2. Change the date of this mission to something earlier than 1994. I used 1988 when I initially fixed the issue.

3. Save. Fly. Verify the INS and waypoints are still broken.

4. Re-edit the mission, change the date to the current date.

5. Save. Fly. Verify the INS and waypoints work correctly.

6. Done.

 

You should not have to modify any other missions. However, any missions with a start date earlier than March 28 1994 at 00:00:01 will not have working INS.

 

Further detail: https://forums.eagle.ru/showpost.php?p=3943139&postcount=19

INS - WAYPOINTS - HOT START.trk

INS - WAYPOINTS - COLD START.trk

Edited June 10, 2019 by boscoh
Added workaround

[Ironwulf]

I didn't have an issue in hot start... in facti t works correct, for me, with the A/C position being the same as the W0 position.

 

In cold start, the hornet seems to think its at N0deg 0.00' E0deg 0.00' and it will not align but I concur that in the 'A/C' area of the HSI 'data' menu, the position seems correct.

 

Interestingly precise mode seems to be working on the waypoint data entry... not sure if its related or not.

 

Man I cant believe this is borked before a weekend! :(

Edited June 7, 2019 by Ironwulf

[Yeti42]

There's two things going on here:

 

 

Issue #1 - "INS - WAYPOINTS - HOT START.TRK" - the waypoint distance and altitude is incorrect. You can see it shows in thousands of miles away, and the altitude at 2000m. You can view in the mission editor and see the waypoint is very close and at ground level. This mission was created in this version of OB. I have also tested with missions from 2.4 to the same effect.

 

Issue #2 - "INS - WAYPOINTS - COLD START.TRK" - Despite following checklist procedure for INS alignment, INS will align to 0.5 OK but never move past that. When you go into HSI > DATA > A/C, you'll see the INS has the correct info but for some reason your position on HSI while in alignment mode never updates from 0 degrees N/E. You also can never enable the moving map, probably because of this. It looks like actual INS works because your heading tape updates correctly with your aircraft.

 

The same issue here, it showed up when I tried to fly one of the Hornet campaign missions

[Ironwulf]

See this for a bit of a workaround

 

https://forums.eagle.ru/showthread.php?t=242554

[Ironwulf]

Looks like carrier TACAN may also be effected... our carrier started flying away at thousands of miles per hour (according to TACAN) to end up 9000miles away... even though it hadn't actually movedo n the map.

 

Note changing channels away, and then back again brought it 'back'.

 

Note whilst this was happening ILS navigation was fine....

[TBear]

I noticed that if the date of the mission You fly is set before 2000 (i.e 1987) then the INS does NOT work. If U set it at a later date then it works properly.

Edited June 8, 2019 by TBear

[boscoh]

None of those workarounds were successful for me, even after waiting for 10 minutes.

[Ironwulf]

Were you on Caucasus? Because I have found it to not work on that map, but it definitely does on Persian Gulf...

 

Edit: going off what Tbear said, more than likely that's a date related issue, because the Caucasus map I was flying in had a mission date prior to 1/1/2000 whereas the PG map was in 2011

Edited June 8, 2019 by Ironwulf

[Ironwulf]

I can confirm what Tbear has said, if the mission date is before 1/1/2000, it wont align, at all, by any of the workaround methods given.

[boscoh]

Were you on Caucasus? Because I have found it to not work on that map, but it definitely does on Persian Gulf...

 

Edit: going off what Tbear said, more than likely that's a date related issue, because the Caucasus map I was flying in had a mission date prior to 1/1/2000 whereas the PG map was in 2011

 

I have tried on Caucasus and PG.

[Svend_Dellepude]

Works for me everytime in both PG and Caucasus.

Maybe you should try a repair, if you didn't already.

[RogueSqdn]

I had been four missions into the five-mission 1989 campaign, and this bug bit me. I edited the mission date to 2001, and the INS worked.

[Panthir]

In my case guys the problem exists all maps and latest dates (later than 2000). The same problem occurs for all Squadron members.

[SVgamer72]

I had the issue, and when I did a full checklist startup (with audible warning A/B switch) It worked. That was the only step I was skipping when I had the issue.

 

It may be coincidence, but I figured I would pass it along.

 

 

 

 

 

Sent from my iPhone using Tapatalk

[Ironwulf]

Just for reference I tried setting the mission computer date forward to 2001 when in a 1986 mission, and it would not align.

[Ironwulf]

I had a pre 2000 mission and it did not work even in SP. Changed the mission date via the mission editor to 2001, and it worked. No other changes.

 

That being said, perhaps just saving the mission in the new version is what did it. I will have ot change it back and see. this would confirm what Panthir says then.

[NineLine]

Never hurts to resave missions, especially going from 2.5.4 to 2.5.5

[Ironwulf]

Ran some testing and I confirm that changing the abovementioned mission that failed, then worked when I changed the date, continued to work when I changed it back.

 

apparently re-saving the mission in the current ME might fix the problem.

[boscoh]

I noticed that if the date of the mission You fly is set before 2000 (i.e 1987) then the INS does NOT work. If U set it at a later date then it works properly.

 

Thanks to this post I went and investigated further. I figured out how to semi-permanently resolve my INS and waypoint issues, as well as some additional info that may help tracking this down if it's reproducible.

 

To resolve the issue (workaround):

 

1. Edit a mission where the INS does not work and waypoint distance is wrong. This mission should have a date that is relatively modern, the default ME date of June 1 2011 works fine.

2. Change the date of this mission to something earlier than 1994. I used 1988 when I initially fixed the issue.

3. Save. Fly. Verify the INS and waypoints are still broken.

4. Re-edit the mission, change the date to the current date.

5. Save. Fly. Verify the INS and waypoints work correctly.

6. Done.

 

You should not have to modify any other missions, as long as the mission date is after March 28 1994 at 00:00:01.

 

This works for both hot start and cold start missions. It is quicker to validate on a hot start.

Note that currently the INS alignment takes some additional time after you get QUAL 0.5 OK. It seems variable but around 20-30sec additional before the map and position show up and you can move to NAV. (https://forums.eagle.ru/showthread.php?p=3943135#post3943135)

 

I verified this issue and workaround on a clean build with no mods.

 

 

More details:

 

I narrowed down the magic date, for me it is 28 March 1994 at 00:00:00 time.

A. Any mission date/time BEFORE this date, and INS and waypoints to not work properly.

B. Any mission date/time AFTER this date, and INS and waypoints work fine.

 

See the attached two tracks.

INS -HOT START - 28MAR-94-00-00-00_not-working.trk - done at 28Mar 1994 with mission time set to 00:00:00, you can see INS is not working.

INS -HOT START - 28MAR-94-00-00-01_working.trk - done at 28Mar 1994 with mission time set to 00:00:01, you can see INS works fine.

 

Interestingly, if you start at 00:00:00, the problem does not resolve when the clock hits :01.

 

You can very easily change the mission time in ME to before/after this date and see the problem clearly, which is what I did to capture these two tracks.

 

I believe the above workaround should solve the issue completely, at least it did for me. However, if the mission date is 28 March 1994 @ 00:00:00 or earlier, INS will still not work.

INS -HOT START - 28MAR-94-00-00-00_not-working.trk

INS -HOT START - 28MAR-94-00-00-01_working.trk

Edited June 9, 2019 by boscoh

[NineLine]

Wonder if it's something like GPS were it is disabled if you set the time back far enough, anyways, good report, I will pass it along.

[boscoh]

Wonder if it's something like GPS were it is disabled if you set the time back far enough, anyways, good report, I will pass it along.

 

That may very well be. I'd be interested to hear.

 

I'm more hoping this helps the devs to find and fix the problem of INS never aligning since the workaround is at least related to it.

[SVgamer72]

Completely fubar for me. Other players have no issues on the same MP server.So it isn't the mission file.

 

I have tried different startup order, wait 5 mins, wait 5 secs, deleted the F18 folder and let it download again, wiped all my control mappings, etc. Wiped the cached mission trk files.

 

The Hornet is unflyable if you can't align the INS (no SA, no heading tape etc)

[boscoh]

Completely fubar for me. Other players have no issues on the same MP server.So it isn't the mission file.

 

I have tried different startup order, wait 5 mins, wait 5 secs, deleted the F18 folder and let it download again, wiped all my control mappings, etc. Wiped the cached mission trk files.

 

The Hornet is unflyable if you can't align the INS (no SA, no heading tape etc)

 

Have you tried the workaround? This might be a client-side fix, meaning it doesn't matter if the server has done it, it may only matter if you do it.

 

Are you starting the game with no mods enabled?

Edited June 10, 2019 by boscoh

[SVgamer72]

Have you tried the workaround? This might be a client-side fix, meaning it doesn't matter if the server has done it, it may only matter if you do it.

 

Are you starting the game with no mods enabled?

 

No mods, and I even disabled my second monitor and used the default 1 screen config file.

 

Workaround is not possible for a MP mission.

 

I just sat for a solid 10 minutes waiting for it to complete alignment, and watched 5 other Hornets spawn in, spool up, and leave with no issues.

 

MP Mission Date:

 

["date"] =

{

["Day"] = 17,

["Year"] = 2019,

["Month"] = 6,

}, -- end of ["date"]

Edited June 10, 2019 by SVgamer72

[Ironwulf]

@boscoh I was working on a new mission just before the update, its mission date was 5 October 1996. It had the issue. Set it forward to 5 October 2001 and it was fixed.

 

Set it back to 5 October 1996, still works.

 

This was in an Australian Hornet too, so there's no Country based issue that I can see.