correct as is Waypoint Offset BRG input bug

[Killshot0597]

Someone in the ED discord brought me to light a potential bug regarding the input of BRG for adding an offset aimpoint. I distinctly remember the value to be inputted as just in degrees in the UFC in "DDD" format. Right now it seems to be in "DDD MM SS" format instead. In my track file below the humvee is located 162 degrees T from waypoint 1, I'd need to input 162 00 00 in the ufc to get the desired result. I'm not sure if this is intentional or not so I've made a report and provided a track file to show it.

hornet offset aimpoint brg input bug.trk

[BIGNEWY]

Thank you Killshot, we will look into it

 

[BIGNEWY]

I've spoken to the team, 

it was adjusted to the new format based on new evidence. It is working as intended. 

Obviously older videos are out of date now, and the manual will need to be adjusted. 

thank you 

[Phantom711]

As someone with a military and aviation background, I find that very odd.

I‘ve never heard or seen anyone breaking up a bearing in something smaller than a degree. And it‘s even weirder to do it in minutes and seconds.

What would be the actual use case? Where would you get bearing information from, that is that accurate?

Anyways…it isn‘t gamebreaking…I just fill in the zeros…

[Blackfyre]

31 minutes ago, Phantom711 said:

As someone with a military and aviation background, I find that very odd.

I‘ve never heard or seen anyone breaking up a bearing in something smaller than a degree. And it‘s even weirder to do it in minutes and seconds.

What would be the actual use case? Where would you get bearing information from, that is that accurate?

Anyways…it isn‘t gamebreaking…I just fill in the zeros…

NATOPS confirms it should be DDD MM SS for the bearing of an offset aimpoint. (see 24.2.5.1.2)

I guess it is just a byproduct of latitude/longitude entry method.

[Phantom711]

vor 4 Stunden schrieb Blackfyre:

NATOPS confirms it should be DDD MM SS for the bearing of an offset aimpoint. (see 24.2.5.1.2)

I guess it is just a byproduct of latitude/longitude entry method.

I just checked it myself and came back here to "confess"... 

[AMEDooley]

14 hours ago, BIGNEWY said:

I've spoken to the team, 

it was adjusted to the new format based on new evidence. It is working as intended. 

Obviously older videos are out of date now, and the manual will need to be adjusted. 

thank you 

What Doc did they find this info in? I’d like to read it cause I can’t enter anything in at all. I tried the format above but it kept saying error. Maybe it’s because I’m in precise? But I’d like to read it to see what I’m doing wrong.

[450Devil]

I suspect someone has read the F-18 NATOPS manual A1-F18AC-NFM-000 page VII-24-24 which requires OFP (Offset Aimpoint Programming) to be enter in to a precision that is "hundredths of a minute" for PRECISE Unboxed and "ten thousandths of a minute ... and hundredths of a second" for PRECISE Boxed.

[rob10]

3 hours ago, AMEDooley said:

What Doc did they find this info in? I’d like to read it cause I can’t enter anything in at all. I tried the format above but it kept saying error. Maybe it’s because I’m in precise? But I’d like to read it to see what I’m doing wrong.

That's pretty obvious in the post 2 above yours (not sure that's what ED is using, but it appears to support ED's interpretation).

[HanuXXL]

But you DO get it to work?

In Arctic Thunder I was pulling my hair as I could not enter the bearing, and finally noticed the same as topic opener. I decided to train a bit and created a mission with some targets around a WP and used ruler in ME to bearing and range... But when I try to Weapon Designate FLIR to those O/S points, they are way off (sic). Seems like it designates several degrees below the intended area.

[Phantom711]

@HanuXXL

Have you entered the elevation correctly?

Not sure right now, but I believe the ruler shows true bearing, the system in the Hornet uses magnetic by default. Depending on the magnetic variation the difference might be significant enough.

[HanuXXL]

Hmm, guess you are right Phantom, I must have fumbled with elevation, probably mixed up the meters/feets.