correct as is Tpod moves the entire flightplan and all waypoints away

[Draken401]

Since DCS 2.9.9.2280 - 10/30/2024

Slewing the Tpod moves all waypoints at the same time. When switching through the waypoints, all waypoints are then in the wrong position/direction/distance. Not on the HSD/MFD, but visible/recognizable on the EHSI (Electronic Horizontal Situation Indicator) and on the Lollipop and Waypoint information block on the HUD. The waypoints can then only be reset by pressing CZ-Center Zero on the Tpod/MFD.
Markpoints are also moved, which makes it impossible to designate multiple markpoints and ripples GBU-38 at them. You can clearly see on the Tpod that the markpoints are moving and consequently the bombs are missing.

[razo+r]

As far as I know, that's how the system is supposed to work. By slewing a sensor, you create an offset that then is maintained and applied to every steerpoint or markpoint that you select until you press CZ.

Unless you mean something different, then I guess a short track showcasing your issue would be helpfull.

Edited December 9, 2024 by razo+r

[Lord Vader]

Hello @Draken401

This is correct behaviour. Every time you move your cursor to a point or area track you're adding a delta to the sensor cursor. In order to remove these deltas, you'll need to TMS aft or select the MFD "CZ" option to Cursor Zero.

[Draken401]

Hello @razo+r, hello @Lord Vader,

Thank you very much for your answers.

I understand that when I move the Tpod, an offset or delta is created. In my opinion, however, this should only affect the current waypoint/steering point.

I cannot say whether this is or should be visible on the EHSI or on the lollipop on the HUD, also Nav data block on the HUD, but I believe this has only been the case since the aforementioned patch 2.9.9.2280 from October 30, 2024.
Nevertheless, unfortunately this shifting of the waypoints, or creation of the delta, does not only affect the selected waypoint, but affects all waypoints at the same time.

The same goes for markpoints. If I set several markpoints one after the other, the ones set first move.

Thank you for understanding that I am asking this question, as the F-16C is one of my favorite modules since it came out and this "innovation" is driving me crazy.

Tpod moves all waypoints.trk Tpod moves all waypoints navblock.trk

[Lord Vader]

Again, the Cursor Zero logic has been refined to replicate real world data from the F-16C Block 50 CCIP to our DCS: F-16C.

If you think this isn't working as the real aircraft would, please supply publicly available non-classified documentation to prove otherwise via private message to @BIGNEWYand we will look into it. Unfortunately, we cannot commit to changes based on personal opinions. 

[Layer_8]

Hi all,

today I run into some odd issue...

I did a little HARM training mission after quite some time away from the sim and I noticed that after an SA-10 engagement, HSI (MFD Page) and HUD where completely misaligned (STP8 on HSD Page is way more to the east than on HUD, Drift C/O is enabled to rule out its drift):

After checking with the F10 Map (as "Ponit of Truth"), it seems the HSD Page is correct, and HUD is wrong:

I´m not sure if it is a bug or a procedural error on my side, as far as I noticed, the problem surfaced after engaging some SA-10 Radars with HARM and HTS. INS alignment went as always and as far as I can tell it was on spot prior the SA-10 Engagement.

 

Any ideas?

Best Regards
Layer_8

HUD_vs_HSD.trk

[razo+r]

Did you press CZ after the engagement?

[Layer_8]

Actually no, as i didn't use the tpod if you mean the cz on tpod? 

[razo+r]

CZ is not exclusive to the TGP. Did you slew the FCR or the SPI in general?

[Layer_8]

1 minute ago, razo+r said:

CZ is not exclusive to the TGP. Did you slew the FCR or the SPI in general?

Yes, on the HTS i targeted the SA-10 Radars. In general, should i allways press CZ on the HSI/Tpod after finishing what ever i did? 

[razo+r]

While I am currently not sure if the HTS will also cause the issue (I'll check the track later), it is definitly a good idea to always make sure that any offset/delta is cleared after you are done.

[Layer_8]

1 minute ago, razo+r said:

While I am currently not sure if the HTS will also cause the issue (I'll check the track later), it is definitly a good idea to always make sure that any offset/delta is cleared after you are done.

Will try later, thanks for the advice!

[Layer_8]

43 minutes ago, razo+r said:

Did you press CZ after the engagement?

You are right, i simply forgot how the viper works in regards to SPIs. Pushing CZ fixes the issue, and explains some oddities i ran into earlier without paying attention to it! 

 

[BIGNEWY]

threads merged

[scotth6]

One question.  WHY?  Why would they design the sensors like this.  Slewing the TGP moves all of your steerpoints?  I'm failing to see any way this could be helpful or necessary.

[Hobel]

vor 3 Stunden schrieb scotth6:

One question.  WHY?  Why would they design the sensors like this.  Slewing the TGP moves all of your steerpoints?  I'm failing to see any way this could be helpful or necessary.

 

From a friend:

Zitat

The F-16C was designed to operate without GPS, using only INS navigation. The most useful aspect of the offset delta being applied to all steerpoints is that in case of INS drift, you don't need to spend time performing an INS FIX to correct for that drift, but can instead simply apply an offset to a known reference point, and it will apply to your entire flight plan. This is one of the primary uses of Offset Aimpoints, as you can put the OA on an easily identifiable landmark near the target area if your target is hard to locate, and then during ingress you correct the OA location using the TGP or any other sensor onto the landmark, and then have an accurate target location for your attack even with INS drift.