[NO BUG] Nevada GPS/Nav/etc. Borked in Patch 2.5.5.38040

[WOPR]

There appears to be an issue tied to INS alignment in the Hornet on the Nevada map. If this is the root cause tied to the release issue that's been fixed internally, great!

 

 

 

1. Weapon aim points are nonsense when using either the TGP or way points. The drop line is in the wrong position. This happens in CCIP or Auto.

2. Mission editor way point distances don't change on the HUD. It seems like the direction determined when on the ground during startup is what the HUD marker is stuck on. INS is verified as set to NAV.

3. The initial point isn't quite right, and the distance to it is 0.0 nmi when over 50 nmi away, like the INS is stuck at the initial point. Waypoint 0 after alignment is not the same as what can be seen on the F10 map with the cursor under the coordinates.

 

 

 

Steps to reproduce:

1. Join a beta dedicated multiplayer server running the Nevada map (I'm confident it's patched)

2. Do an INS alignment prior to take-off.

3. Load up some bombs and the TGP.

4. Observe the issues above while trying the Hornet systems.

 

 

 

You shouldn't need a track file to see this behavior. It's glaringly obvious.

Edited October 20, 2019 by WOPR

[Andrei]

What was the date of the mission and coalition of the Hornet? If GPS is not available due to one of those reason, you will have that behavior.

[Maggot]

I tried the F18 BFM campaign (Nevada) a few hours ago. Open beta. Restarted the first mission three times, since I couldn’t get the waypoints or the moving map to work, and assumed I did something wrong in the startup procedure. Then I gave up.

Was just about to read up on the start procedure again when I saw this post...

[WOPR]

What was the date of the mission and coalition of the Hornet? If GPS is not available due to one of those reason, you will have that behavior.

 

 

GPS works fine on the A10Cs and AV8Bs in the same mission. This is not a factor in this case.

[NineLine]

We would like to see the mission and/or a track, please.

[NineLine]

I tried online myself, and havent seen the issue yet. SO if you have a track or maybe a specific server I can check that out.

[Ramsay]

I tried the F18 BFM campaign (Nevada) a few hours ago. Open beta. Restarted the first mission three times, since I couldn’t get the waypoints or the moving map to work, and assumed I did something wrong in the startup procedure.

There's a know issue using the F/A-18C in the 'Maple Flag Aggressors Campaign' - as they are REDFOR they don't align correctly and you need to do a 'waypoint 0' update (after the alignment) to load the correct co-ordinates into it's Nav.

 

https://forums.eagle.ru/showthread.php?p=4067626#post4067626

 

The work around is still require in DCS Open Beta 2.5.5.38040

[Ramsay]

GPS works fine on the A10Cs and AV8Bs in the same mission. This is not a factor in this case.

 

AFAIK the A-10C and AV-8B will align correctly when assigned to RED, only the F/A-18C is effected.

[Maggot]

[MISSING TRACK] Nevada GPS/Nav/etc. Borked in Patch 2.5.5.38040

 

There's a know issue using the F/A-18C in the 'Maple Flag Aggressors Campaign' - as they are REDFOR they don't align correctly and you need to do a 'waypoint 0' update (after the alignment) to load the correct co-ordinates into it's Nav.

 

 

 

https://forums.eagle.ru/showthread.php?p=4067626#post4067626

 

 

 

The work around is still require in DCS Open Beta 2.5.5.38040

 

 

 

Okey, thank you!

Edited October 21, 2019 by Maggot

[BIGNEWY]

Hi

 

REDFOR do not use GPS so you have to align manually.

[WOPR]

BLUFOR aircraft only in this mission. I wasn't aware of the REDFOR issue in NTTR.

 

BTW you can see the alignment issue on a smaller scale in the Caucus, but it doesn't seem to manifest as a catastrophic INS issue.

 

 

Forums won't let me upload the 56 MB track file.

 

 

Bignewy, have you attempted to replicate the issue?

 

 

 

Edited October 21, 2019 by WOPR

[BIGNEWY]

Yes, REDFOR aircraft do not use GPS as it is a US military asset.

 

 

Can you let me know which mission it is, I will take a look. Or a very short track file showing the issue only

 

Bare in mind also GPS isn't present before 1994 in DCS

Edited October 22, 2019 by BIGNEWY

[WOPR]

Okay, I get to retract the earlier statement about the year. :face palm:

 

 

 

After digging in further, it appears that the mission date was unexpectedly reset to 1990 after being edited and saved. This might actually be mission editor bug report. I'm not able to try and fix it tonight, but I or a squad mate will tomorrow and I'll let you know for sure.

 

 

I appreciate the discussion.

[BIGNEWY]

No problem, at least we have solved the initial problem.

 

thanks for letting us know

[Eddie]

Yes, REDFOR aircraft do not use GPS as it is a US military asset.

 

Ok this doesn’t really make sense. I get what ED has tried to go for here, but it doesn’t quite work that way.

 

It’s certainly the case that “opfor” wouldn’t have the necessary crypto codes to access the GPS P codes, however they’d still be able to use the C codes (just like your sat nav). The only way that wouldn’t be the case is if GPS were being jammed by “blufor”, which could only be localised and not theatre wide, and would affect both sides.

[BIGNEWY]

Ok this doesn’t really make sense. I get what ED has tried to go for here, but it doesn’t quite work that way.

 

It’s certainly the case that “opfor” wouldn’t have the necessary crypto codes to access the GPS P codes, however they’d still be able to use the C codes (just like your sat nav). The only way that wouldn’t be the case is if GPS were being jammed by “blufor”, which could only be localised and not theatre wide, and would affect both sides.

 

I have made a report to the team asking for a change, can not promise any change at the moment but the team are considering it.