Are bullseye calls broken?

[JEFX]

This has been annoying me for quite a while now... Is it something I do wrong or is there something not working properly?

 

This has been happening a lot in the fast mission generator, then it did happen to me in a campaing mission and finally, I did a test tonight, just simple in the mission Editor... Here is my problem :

 

When I start hearing Bullseye calls (usually way too many for the same group of vehicles..) I hook myself on the TAD and put the TAD in mode BUL-CURS, then I can move around the cursor and have a rough idea where are the targets... Very often, the calls point to a location that is totally out of the way, far from the battle… Still, when I wasnt sure, I thought, OK… perhaps there is something I dont see...

 

But tonight in Georgian Hammer (mission 2-3), the Bullseye call was pointing somewhere in Turkey, way south of Batumi, when we all know that the battle in Georgian Hammer is north of Batumi…

 

I decided to make an experimentation : I set-up a small mission where I fly towards a bunch of vehicles and there is one F-16 that is flying towards it too (assigned CAS). I did again the hooking of myself and the BUL-CURS setting on the TAD and I see the F-16 (because of EPLRS) on my TAD. At one point, he says :

 

‘tally utility at bulls such and such’ and a minute later

‘engaging utility’ at bulls such and such

And I think finally

‘kill utility at bulls such and such’

 

I can see the purple beam of his SPI on my TAD and I put my cursor on it and…

it is not at all the Bullseye coordinates that he is calling. Further more, the 3 different ‘such and such’ that he called were very different (and I had put the bullseye far enough that it is not because it was in the middle…)

 

Now, what is wrong with this?

 

thanks

 

JF

[ralfidude]

There is a thing called an OFFSET that you can use on the CDU for the BULLSEYE call that give you an exact measure of what they are talking about, and as far as I am concerned it has worked for me perfectly.

 

The accuracy is not as good as a DATA sent by JTAC but it does get you in the ballpark.

So not sure here, but no problems on my side.

[GGTharos]

JEFX, track please.

[Aries]

Had same thing with F-16s in deephouse's mission Standby CSAR... they call some weird bulls offsets... like bulls 100 for 250 miles??? and also that stuff... vehicles bla bla, defending vehicles... and we're all like 35 miles from bullseye LOL...

[Paranoid_CF]

Same thing here on my mission. Calls are wrongs!!!

[Joyride]

Yes, noticed this occurring yesterday in a mission and thought I was crazy. The only enemy units in the mission were within 20 mi of bullseye but the AI calls were "for 150".

[JEFX]

I found something, perhaps

 

OK GG here is a track (actually 2)

 

This is a very simple track.

I F-16 attacks right at the start one lone utility vehicle.

In the ME, I measured the Bullseye coords and it is 166 deg. for 17 NM.

When the F-16 attacks, its call is precisely the same!

but...

When I look at my TAD in mission (after hooking myself and putting the TAD in BULLS-CURS mode and slewing my cursor over his SPI), the reading in the lower right is 159 for 017... There is a difference of -7 degrees.

 

The second track is the same with a different target, located at 194 for 13 and the F-16s call is again precisely on it and once again, the TAD reading of his SPI is again -7 degrees (187 for 013)...

 

I have had wilder discrepencies in the past but that resembles what I was observing in the fast mission generator a couple of days ago.

 

What can explain a consistent -7degrees offset?

 

????????:huh:

 

(by the way, thanks for all the answer, but, yes, friends, I know about the OFFSET page of the CDU, but when in the heat of battle, I want to know quickly what is going on, I find it very handy to play around with the cursor of the TAD like this and make MARK POINTS whenever I need to keep a memory of a particular point of interest...)

bullseye experiment 1.trk

bullseye experiment 2.trk

[BlueRidgeDx]

TAD map convergence and magnetic variation are items that will *likely* appear in the 1.1.1.1 patch fixes.

 

The only reason I say "likely" instead of "will", is because I don't have the authority to say so.

 

:)

[GGTharos]

Thanks JEFX.

 

I also need tracks where AI call the target too far away.

[JEFX]

Thanks BlueRidge

 

I understand what you are saying, but is 7 degrees the magnetic variation in the black sea region? I thought it was 5 degrees E ?

 

thanks

 

 

GG, I dont have a track with a wild distance difference but next time it occurs, I will send it here.

 

Jean-Francois

[kylania]

I tried to use the bullseye call from an F-16 to find it's targets. The targets were at the bottom of a mountain and the bullseye call was placed on the other side high of the mountain. For someone figuring it out while flying a fast mover I'm guessing that's 'close enough'? :)

[BlueRidgeDx]

JEFX,

 

It varies from one edge of the map to the other. Without specifically looking, I believe that the average value is 5, but other values are correct depending on position.

[JEFX]

Here is a track with crazy BULLSEYE calls

 

OK GG

 

here is a track for crazy distance behavior of bullseye calls...

 

Here is a track of mission 2-3-0 from Georgian Hammer campaign.

 

2 minutes in mission (at 07:32) one can hear : "Boar 14 tally AAA at Bulls 116 for 400"... I checked on the F10 map and if one measures 116 for 400 from bullseye, the position is roughly 11 NM ESE of Ozurgeti, which seems East of all red vehicles... and that is when looking on map... When checked in TAD (again with hooking oneself and putting the TAD in BULLS<CURS mode and putting the cursor at 116 for 400, the point is WAAY behind our lines in Turkey (which probably means that a few degrees difference at 400 miles make a great difference...) still, if one looks on TAD and deducts 5 or 7 degrees, still, the point found is still east of the battle...

 

Then, at around 07:36:20, one can hear "in from the south-east, engaging radar at 117 for 400... Checked with both methods (F10 map or TAD cursor) that point doesnt make any sense in relation to the broadcasted SPI and, anyway, I checked with F2 and ALL of our aircraft is close to the sea and that point (117 for 400) lies somewhere inland where there is no battle and no SPI (and no aircraft)...

 

Thanks for checking, but that is a great immersion killer...

 

JEFX

G.Hammer2-3-0 crazy bullseye.trk

[Juuba]

We noticed yesterday in Multiplayer (playing OP Lagavulin by Druid_) that When the Host called "PICTURE" the Awacs replied with correct bearing/range..

And when it was "automatic" (e.g POP UP GROUP) the Awacs's BRA was correct.

 

But when the other clients tried to call Picture themselves, only the Host heard/could read the correct BRA, clients received (both audio and text) totally off the mark BRA, like in the range of "350 for 150" when the correct was about "095 for 11" or similar.

This incorrect BRA was always the same.

 

We could circumvent this by having the host repeat the BRA, but still, a hassle. :)

 

And we want don't mess with the Hoff.