[REPORTED] 2.5.5.31917 - INS and Waypoint Issue

[boscoh]

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"]

 

It doesn't appear the server needs the workaround, just you. Try editing a mission per the steps then connect to your mp server and see if its fixed.

[Ironwulf]

Not true mate.

 

I connect to two TTI servers here - one with mission date 1986 and one 2011

 

 

1986 doesn't work

 

 

2011 does. So, its not the client end.

[boscoh]

Not true mate.

 

I connect to two TTI servers here - one with mission date 1986 and one 2011

 

 

1986 doesn't work

 

 

2011 does. So, its not the client end.

 

The workaround doesn't work if the mission date is earlier than Mar 28 1994 so I would expect that.

[Harker]

Not true mate.

 

I connect to two TTI servers here - one with mission date 1986 and one 2011

 

 

1986 doesn't work

 

 

2011 does. So, its not the client end.

If I'm not mistaken, the C version of the Hornet was introduced in 1987. So I wouldn't be surprised if the INS wouldn't align before that.

[NineLine]

So I can reproduce it in OB as well, but not internally, so I have asked one of the Hornet devs to let me know if its a bug or by design.

[boscoh]

So I can reproduce it in OB as well, but not internally, so I have asked one of the Hornet devs to let me know if its a bug or by design.

 

Are you talking about INS not aligning at all, until you perform the workaround?

 

Or are you talking about it just not working before Mar 28 1994?

 

I want to make sure the original reported issue isn't being muddled up with the 1994 finding.

[NineLine]

No, I tried your tracks, taking control and doing both start up on my own and auto startup, and giving INS its proper time the WPs show correctly.

 

Make sure you run INS until your ownship waypoint 0 coordinates are shown.

[RogueSqdn]

That may be the case, but in the 1989 campaign you have a hot start on the deck and have these issues. Something needs to be done about that.

 

 

Sent from my iPhone using Tapatalk

[boscoh]

No, I tried your tracks, taking control and doing both start up on my own and auto startup, and giving INS its proper time the WPs show correctly.

 

Make sure you run INS until your ownship waypoint 0 coordinates are shown.

 

That's the thing though. It never aligns until you do the workaround.

 

The track doesn't show it, but I've sat for 10+ minutes without it aligning. I can do a complete reinstall and record a track that shows this, I just didn't think anyone would want to watch a 10+ minute track.

 

Once you do the workaround, INS alignment is consistently achieved within about 90 seconds. Yes you do have to wait for some time after QUAL 0.5 OK, but it does work after the workaround.

 

Are you saying that on a brand new install of OpenBeta, you're not able to reproduce the INS never aligning?

[Juuba]

If it works, it takes about 1:40 (a minute and 40 seconds) for the map to show.

 

if it doesn't it don't matter how long you wait.

[QuiGon]

Has this issue been fixued in todays update? Doesn't seem like it, as the changelog doesn't mention it :(

[X-man]

Has this issue been fixued in todays update? Doesn't seem like it, as the changelog doesn't mention it :(

I still experience it.

 

Tried to re-save mission, load up on our server. Join as client in AUSAF F/A-18. INS still only show zeroes, no DL, no WPTS :(

 

Tried the work around as well (Mission 2011, resave as 1980, resave as 2019). No joy.