[REPORTED]AGM-65 selection garbles Steerpoint Info

[Alpha]

With the current OB (this week) when slecting AG-Mode with AGM-65 on the jet the Distance to the active Steerpoint and ETA on the HUD jumps to bizarre numbers. Also the DME on the HSI is affected in the same way.

Deselection of the AGM-65 or AG-Mode does not restore proper Data. The steerpoint HUD-box is also not shown correctly in NAV Mode anymore in this case.

 

Verified for AGM-65 D/H on Syria and Nellis Map. This also happens on the ground right after startup. Just select AG Mastermode and check the Steerpoint Dist/ETA on HUD and HSI.

Edited September 24, 2020 by Alpha

[Y-Man]

Experienced the same issue on PG MP map as well. HSD waypoints stayed the same, but INS nav waypoints became unusable.

[The RDN]

Hi,

same issue for me, on caucasus map...

[Bonzo0181]

Same problem. What seems to be happening is that the nav system is showing distance to the target point (whatever it's called), not a steerpoint.

 

 

It should show usable numbers when you slew the sensor to the ground. Also, PRE mode should work nonetheless.

 

 

I don't know what's supposed to happen, but the same happens in Wags' video (13:55).

[Jugdriver]

I am seeing the same thing.

 

 

MattE

[deadpool]

It happens because Mavericks jump back to VIS mode all the time ...

like when you go to MRM and then back to AG .. it will be in VIS mode again ..

 

or when you fired the last and switch modes back to NAV .. might end up in VIS mode .. and that shows you those bogus data.

[Falconeer]

Waypoints completely off

 

Hello,

 

i dont know what happened, but i found out after the update (havent flown for a couple of days) that my waypoints are completely off. I usually use "stored heading" alignment, before takeoff and wait till the "RDY" lights starts flashing. I used "inflight aligment" and normal alignment aswell (with confirming the coordinates), and still waypoints are literly miles off. Sometimes they are even way up in the sky.

 

I tried repairing DCS, but didn't help. I also made sure that the jet isn't moving during alignment and that the weapons are loaded, before even starting the engine. I tried recording it, but since im flying mostly on MP, the files get to big to upload here.

 

Is there anyone with the same problems? It makes flying Viper difficult this way

 

edit: tried the "Cold and Dark" mision a couple of times, with different alignment modes and every is working fine there

Kirks Freeflight summer evening 2.0.6-20200925-124705.zip

Edited September 25, 2020 by Falconeer

[Stubbies2003]

It had been awhile since I had flown the Viper but I did fly on OB patch day and noticed the same thing on a MP Persian Gulf map. Some of the waypoints were correct but most were grossly off. The odd part was the HSD page was totally correct for waypoint locations so we just ignored the INS indications and flew off of the HSD for current location. That MP map was hot started aircraft so the INS was already aligned.

[Ithronwise]

I experienced this bug when I switch between A/G- or A/A- and NAV mode. Suddenly the distance to the chosen waypoint in the HUD increases (see trackfile, Nevada map is needed), as soon I switch back to NAV. The position of the waypoint also isn't correct anymore.

F-16C Bug Waypoint Distance Tonopah NTTR 01.trk

[Majik]

Have had this happen with Mavs powered on. HSD shows correct steerpoints, but the hud sherm is pointing nowhere near where it should, and the distance to waypoint information looks like I'm being hacked. Powering off all mavs eventually returned the sherm to where it should be pointing.

[Majik]

Confimed same issue on Syria TTI. Powering off mavs on the SMS page eventually returned correct steerpoint info.

[Falconeer]

Have had this happen with Mavs powered on. HSD shows correct steerpoints, but the hud sherm is pointing nowhere near where it should, and the distance to waypoint information looks like I'm being hacked. Powering off all mavs eventually returned the sherm to where it should be pointing.

 

Now that you say it.... I only flew the MP missions with the Mavericks loaded and power on. In the SP missions i tried (when it did work) i had the training bombs loaded, so we might be on too something here

[fjacobsen]

I think it´s the TGP that messes up the wewaypoints.

 

When I use the TGP the waypoint positions and distance are messed up on the HUD, the HSD looks correct.

 

Maybe it´s remnants from when the TGP manipulated the active waypoint to which it was slaved.

 

I just flew a mission, practicing the AGM-88C HARM and flew without a TGP pod, HUD indications remained accurate.

[Falconeer]

I think it´s the TGP that messes up the wewaypoints.

 

When I use the TGP the waypoint positions and distance are messed up on the HUD, the HSD looks correct.

 

Maybe it´s remnants from when the TGP manipulated the active waypoint to which it was slaved.

 

I just flew a mission, practicing the AGM-88C HARM and flew without a TGP pod, HUD indications remained accurate.

 

Then its the TGP or the Mavericks

[Falconeer]

Might this be the same issue?

 

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

[Majik]

Then its the TGP or the Mavericks

 

After I had issues with the steerpoints with Mavericks, I switched to a CAP loadout and didn't notice any issues with the TGP in A-A mode. Haven't yet tried TGP in A-G without Mavericks since the patch dropped though, so still could very well be a TGP issue.

 

 

Powering off the Mavericks did fix the issue for me though, and I didn't store the TGP.

Edited September 25, 2020 by Majik

[Ithronwise]

I think it´s the TGP that messes up the wewaypoints.

 

When I use the TGP the waypoint positions and distance are messed up on the HUD, the HSD looks correct.

 

Maybe it´s remnants from when the TGP manipulated the active waypoint to which it was slaved.

 

I just flew a mission, practicing the AGM-88C HARM and flew without a TGP pod, HUD indications remained accurate.

 

It's definitely not the TGP. The track I attached on my first posting was without targeting pod, but with Mavs. I also think, that the bug is related to them.

[Viking 1-1]

Yes. Mav Power on screws the NAV Data on the EHSI

[Frederf]

EO VIS is treating the pre-designate aiming box the same as the TD box and generating system deltas like CCRP. This is wrong simulation. Pre-designate EO VIS is just a LOS slaving feature like DTOS, steerpoint is not updated.

 

I don't even think that post-designate EO VIS adds system deltas (same DTOS). You should be able to attack EO VIS or DTOS with all kinds of slewing pre or post designate and never apply any deltas.

 

In the track you can see simply slewing the pre-designate EO VIS box is doing wild things to the navigation solution on the EHSI.

F16 EO VIS predesignate move stpt.trk

[Musis]

Wrong distance information in HUD

 

With last issue of OB (Take off Beirut, WP1 Damas, HUD displays a wrong distance (normaly 50nm)...

[FoxOne007]

I'm having the same issue (whenever I air start at least)

[Falconeer]

Did you have mavericks loaded and powered on?

[Musis]

Effectively, 6 AGM 65D for training, ON at take off, and switched on during alignment.

[Falconeer]

Effectively, 6 AGM 65D for training, ON at take off, and switched on during alignment.

 

There is your problem. There seems to be a bug with Maverick switched on and steerpoint information. There are already 2 threads below this one, with the same issue (mine included)

[BIGNEWY]

Merged three threads, will investigate.

 

My guess is it will relate to the phantom waypoint issue already reported, the SPI system should resolve this.

I will replay after I have investigated.

 

thanks