Jump to content

Offset is applied to existing designation, instead of resetting it to the Offset coordinates


Recommended Posts

Posted (edited)

Edit: After looking into it more and discussing with more people, seems like the current behavior is correct. @BIGNEWY, I took the liberty to change the tag and I'm pinging you to let you know to stop working on this. Sorry for the confusion.

 

2.7.5.10869 Open Beta

 

1. Set up an Offset to a WP (I chose WP1).

2. WPDSG. Designation moves to WP1.

3. Slew the designation around (example, 1,000 ft North). (Delta = 1,000 ft North).

4. Bug = Press O/S. The designation moves to the offset point, plus the previous delta from the WP.

 

Expected behavior: Once O/S is pressed, the designation should simply reset to the Offset coordinates.

FA-18C_Offset is applied to the designation.trk

Edited by Harker
  • Like 1

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3
-
i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro

Posted

What's your reference for this Harker? AFAIK, the offset should be applied to the designation. Otherwise how would radar offset bombing work? I.e. Target is an offset from a known radar map point, but INS drifts, so re-slew to radar significant point and add the offset to get the corrected true target position..... 

Posted
2 hours ago, AvroLanc said:

What's your reference for this Harker? AFAIK, the offset should be applied to the designation. Otherwise how would radar offset bombing work? I.e. Target is an offset from a known radar map point, but INS drifts, so re-slew to radar significant point and add the offset to get the corrected true target position..... 

After looking into it more, the current behavior is actually correct. The confusion came from the fact that the O/S option was available even after manually slewing the designation, but given new information that @Jak525 shared with me, it is normal that the offset will be applied to any existing designation, not just the one from WPDSG.

I am going to change the title and OP to reflect that the current implementation (on this front) seems to be correct.

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3
-
i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro

  • Harker changed the title to [Correct behavior] Offset is applied to existing designation, instead of resetting it to the Offset coordinates
  • Harker changed the title to [Correct as is] Offset is applied to existing designation, instead of resetting it to the Offset coordinates
Posted

 

39 minutes ago, Harker said:

After looking into it more, the current behavior is actually correct. The confusion came from the fact that the O/S option was available even after manually slewing the designation, but given new information that @Jak525 shared with me, it is normal that the offset will be applied to any existing designation, not just the one from WPDSG.

I am going to change the title and OP to reflect that the current implementation (on this front) seems to be correct.


Thanks, I wasn’t going mad then.
 

I’ve not played around with offsets much since some ‘fixes’ were made in an OB update a while ago. But the behaviour you describe seems 100% legit, at least on this one point. Validation is sweet. 

Posted (edited)
20 minutes ago, AvroLanc said:

 


Thanks, I wasn’t going mad then.
 

I’ve not played around with offsets much since some ‘fixes’ were made in an OB update a while ago. But the behaviour you describe seems 100% legit, at least on this one point. Validation is sweet. 

Yeah, I had misunderstood some functionality. The overall logic is still kinda weird though, so I'm looking into refining my other bug reports. Mainly there is inconsistency between how sensors and release cues work after using the Offset function.

Edited by Harker

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3
-
i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro

  • BIGNEWY changed the title to Offset is applied to existing designation, instead of resetting it to the Offset coordinates
Posted
23 minutes ago, Harker said:

Yeah, I had misunderstood some functionality. The overall logic is still kinda weird though, so I'm looking into refining my other bug reports. Mainly there is inconsistency between how sensors and release cues work after using the Offset function.

 


Most definitely. One inconsistency is when you try a HUD TDC assignment with an offset designated. For example, when becoming visual with a radar offset designated target...the problem is the TDC cue is assigned to the OAP/Waypoint position in the HUD, rather than the target/offset (I.e the target you want to refine the slew on to correct the inherent radar inaccuracy.)
 

At least that’s how I remember it working from when I tried it a couple months ago. I’m having a Hornet break at the moment. 

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...