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

[grant977]

So I do a cold start this am and swap the ins over to ground then to nav and no map and way off on navigation. I restart the mission a couple times and actually wait for the countdown to swap over and still no dice.

 

Something get broken with the patch?

 

 

Update: This happens with cold start and agm 154s loaded.

Edited July 31, 2019 by grant977

[QuiGon]

Sounds a bit like the INS issue from a few updates before has returned :cry:

[BIGNEWY]

Hi

 

I can not reproduce please attach a track replay showing the issue

 

If you have not already please try a cleanup and repair

 

thanks

[timo144]

[MISSING TRACK REPLAY]HSI No longer works with Litening pod open beta update

 

HSI No longer works with Litening pod open beta update. Doesn't show the map in the caucasus anymore. (steam version)

[BIGNEWY]

Hi

 

can you please attach a track replay showing the issue.

 

I can not reproduce.

[BIGNEWY]

Merged threads

[timo144]

Track sent

HSI Broken.trk

[grant977]

Track as requested.

INS ISSUE F18.trk

[BIGNEWY]

Track as requested.

 

try setting the mission date later than 1994, it should help.

 

Let me know if it does.

[BIGNEWY]

The team are still looking into this

[grant977]

Will try I also reverted back to prior to patch and it works fine.

[NineLine]

Remember, GPS was in wide use by 94/95. As well the Hornet we are using is right around the early 2000's, so for the best bet, make sure you are using similar or newer dates in your missions.

 

If you time travel to 1944, some systems won't work.

[timo144]

I don't even own any of the WWII planes. Just made a new mission on the caucasus from the fresh and it did this. So unless all maps and mission files are defaulted to 1944 i wouldn't see why my missions were in 1944

[NineLine]

Well, 1944 was a drastic example, but if you created a new mission and didn't change it, it shouldn't be an issue. Can you upload your mission?

[Wizard_03]

Working for me on the PG map, fresh mission cold start with pod loaded Current date. Map works/INS aligned well verified with TACAN Fix.

Edited July 31, 2019 by Wizard_03

[BIGNEWY]

Hi all

 

If you are seeing this issue please ensure you have removed any unofficial modifications ( if any) and done a cleanup and repair.

 

If you are using steam version, verify the integrity of your files.

 

Thanks

[grant977]

Just made it current date loaded up the agm154s and no joy. I had luck with airplane clean and no 154s but when I loaded the mission with them the problem occurs.

[Neor]

Is the F-18 on the USA side?

[Viper 9]

Hornet INS NOT Working On OPFOR - Chapter 2

 

This bug has returned:

 

Eagle Dynamics/FA 18 Development Team:

 

While there have been some changes to the INS, the hornet will still correctly align when flying on for the "nato/blufor" coalitions on both Caucasus and PG map. However, when flying for OPFOR (Russian hornet, USAF aggressors hornet, etc.) and performing a cold start, the hornet completely refuses to appropriately align.

 

Using the normal alignment procedure (start up, switch to ground, wait for timer to countdown, switch to NAV, wait for HSI to display appropriate alignment) does not result in appropriate alignment of "OPFOR" hornets at any point in time. The HSI will continuously display all zeros for northing and easting, and waypoint 0 will always remain thousands of miles away. The heading tape will still function normally, but that is all.

 

This results in being unable to effectively navigate using onboard INS/HSI. The HSI map is not available obviously, and entering waypoints has been rendered useless. The F10 map has to be used as a means of obtaining range and bearing to targets (on servers that allow the F10 views). In addition, the datalink/SA becomes completely non-functional. The range displayed on the SA page is so far off from your actual location that absolutely no HAFUs will appear on the screen.

 

I have tested this on both public servers (Buddyspike and Growling Sidewinder) as well as user ran servers during a scrim with some friends. Any time a hornet spawned for cold start on OPFOR (for example: a Russian hornet at Beslan or Nalchik; or a USAF aggressors hornet at Bandar-Abbas) proper alignment could not be completed. I have not tested this issue offline, only in a multiplayer setting.

 

The effects of this could have severe consequences on upcoming SATAL matches for pilots that wish to fly the hornet as their SA would be severely compromised.

 

Thanks for listening,

 

Viper 9

 

There may be some subtle differences from before (This was originally posted a few months ago when this bug first became apparent). But the Hornet not aligning bug has returned for any hornets playing on OPFOR coalitions (Russia, China, USAF Aggrsrs etc.). This bug is present regardless of whether or not the targeting pod is loaded, which may be in contrast to another bug report recently. SATAL matches are this weekend and, without a working SA page, hornet drivers will not be able to effectively compete as they normally would.

 

Do I have to go through the trouble of making another track file?? The problem is almost identical to the one I reported a few months ago.

 

:mad::mad::mad::mad:

[Harker]

Works for me on both PG and Caucasus, for Bluefor. Mind you, the map won't show up until I turn the dial to NAV, which is not correct, but it shows up after.

I've had the map go away a couple of times during a mission (just black background), but it came back after a while.

Edited August 5, 2019 by Harker

[Tholozor]

What I do is start a ground align and wait for the distance to waypoint zero become 0, and going to NAV after that brings the map up for me.

[grant977]

Hmm Harker that’s interesting will try that and see if I get same result.

[Cskelly]

HSI not working in open beta, BFM campaign.

Would like to roll back update in open beta but not sure how.

[Harker]

HSI not working in open beta, BFM campaign.

 

Would like to roll back update in open beta but not sure how.

I tried it as well, no dice. It's because of the bug with the INS alignment not working specifically for the Red coalition. Looks like the campaign is on hold for now.

[Ironwulf]

Had issues with the moving map going a bit weird when loading up the TGP after startup from cold start with no weapons. Scren was half black, half white. Could be removed by turning the map off, but if you turned it back on it came back. Same with SA page MAP. Once the aircraft started moving, it was fine again.