Bullseye help
-
Bulls on overview map (WDP) is perfect …
I was just saying no pencil …. and no need of big acuracy. you have radar cursor. Note that over 100 - 1500nm BE becomes too much unprecise… IRL there are several bulls on the theater. -
Use a pen is not a bad idea, in fact it’s a real technics use by F-16 pilot before M3 update. After a picture call, put a dot on the sketchmap.
Why M3? because since M3, you have a HSD cursor bulleyes. And in Falcon too, so this is the new technic use (and the one I use too). When receive a bulleyes, switch SOI on HSD and slew the cursor. Bulleye of the cursor is given on the lower right corner. Then you have a good SA of the bulleye position. -
Hi there.
What I use to improve my sa a little bit is this
It helps me especially if BE simbol is visible on hsd display. This way I can figure out faster in my head where the given bulls position is.
If BE is not visible on Hsd, I can quickly zoom out until it is.
It takes no time at all to set it up, and if you use WDP once you draw it, it will be there too for your next mission. I always use line 4 to draw it.
Some A/C have a HSD mode in which the display can be centered on BE and oriented to north.
The display will be fixed and it is your AC which is moving around the screen. With this mode it is very fast and easy to lacate a BE position, but it does not work as well when you are flying very far away from bulls.I whish F16 had this hsd mode…
Anyway I hope my little “trick” helps you.
-
you can fix the display so that the aircraft is not centered in the screen, but without actually flying over BE as you do it I am not sure about centering it over BE.
-
you can fix the display so that the aircraft is not centered in the screen, but without actually flying over BE as you do it I am not sure about centering it over BE.
I have to further look into this…
Thanks for the tip
-
OSB 7 on the HSD is the FZ option, which if selected (is supposed to) freeze the movement of the HSD as well as center it over the ground stabilised position of the HSD cursor. so if you slew the cursor to bullseye, then hit FZ, if should center the display over the bullseye… but I think it retains your present orientation though, which would mean you would need to be heading north to start the process.
-
OSB 7 on the HSD is the FZ option, which if selected (is supposed to) freeze the movement of the HSD as well as center it over the ground stabilised position of the HSD cursor. so if you slew the cursor to bullseye, then hit FZ, if should center the display over the bullseye… but I think it retains your present orientation though, which would mean you would need to be heading north to start the process.
What happens then if u change the range scale?
-
same as usual unless you have also coupled the range to the FCR.
-
-
I think that the HSD is the easiest way to check a BE coordinate. But it also helps to be able to imagine where the BE is and its orientation to me in order to be able to move the HSD cursor around and predict how the numbers are going to change as I move it instead of just randomly moving it around as numbers change.
What helped me was to use a post-it note, and draw a circle on it with lines for 0, 90, 180 and 270. Then give myself a random BE position. Hold the post it note where the BE is. The lower left corner of the FCR and HSD has a symbol that points toward it. I would imagine a line from me to the BE for proportional distance. Rotate the post-it note correctly. Then imagine a line from the post-it note to the contact position. Practice this enough and you can imagine a line coming from your position to BE and out from BE toward the contact. To remember which way the numbers go, I tell myself “left-large.” Because the numbers always get bigger going left on the dial as you look at it.
I hope this helps.
-
I wrote a dirty little excel program to help with my bullseye calls. I found the other trainer listed above was too much for me (maybe i was trying it too early in my falcon career?). Feel free to give it a shot: http://www.mediafire.com/view/fnr3mc4bt45kaea/Bullseye_Training_0.1.xlsm
Far from professional grade, but i needed something when i moved from BRAA to bullseye calls. No plans to update this thing further. The file uses Visual Basic macros, so you’ll have to “trust me” and allow them. After trying this thing again for the first time in ages, i’m realizing that i could use some more work too….
Good luck!
-
You can also use your radar or HSD cursor because as you move this cursor around the MFD, you will see the Bullseye readouts displayed for the position of that cursor. So, when you get a bullseye call, just move your cursor around and try to put it on that called out position. If you cannot then the position is probably not in your immediate vicinity. You can change the range of the display if you need to. However, if you do find the coordinates and they are close enough you can maneuver accordingly.
Raven
-
There’s also an option to not have AWACS and others use bullseye and just give everything in angle/distance relative to you. That really helps me with bullseye calls At this point I don’t need the training wheels, I guess.
-
using BRAA calls for that is not really very secure…
-
^Against what?
If the human adversaries in Red Flag are spying on the other frequencies, they will get the bullseye-position. And for playability reasons it is not moved often… Fixed BE information is even better for the intel.It would take quite sizeable human resources to reverse-engineer BRAA calls in-flight and then relay data real time so it benefits the planes in air. In real war, yes, that would be at least tried, but in BMS environment we don’t even have ID and C2 staff (enough). And their meaning is decades more important than intel.
-
BRAA is a very unpractical stuff. BRAA is only valid for one guy (or anybody knowing where this guy is) … BE can be used by everyone = much more practical.
BRAA in only useful for a guy or a patrol about approaching to the merge criteria.
If the human adversaries in Red Flag are spying on the other frequencies, they will get the bullseye-position.
How?
-
By taking about 2-4 conflicts, and checking where the involved planes were at the time of the calls and merge. The high criteria targets for AWACS guys are enemy (=our) F-16s, so it doesn’t even take lots of comparisons. Additional matching information can be taking in maneuvering or splash information. Even one merge can give you approximate position, if you can time it to one single incident.
When you find matching location, you can verify it by the next calls. It doesn’t need to be very sharp, within 10-20 miles is still good. It makes possible to decipher which own groups are noticed and targetted, and which may still be unattended.This can of course be countered with rotating bullseyes every now and then, and having different bullseyes for different packages. But I doubt Red Flag AWACS would have that much manpower, energy and coordination with the sporadic pilots and flights.
In fact it would be quite interesting exercise to preassign several bullseyes and force the groups to rotate them (even on fly). Just for the fun of it.
-
Additional matching information can be taking in maneuvering or splash information. Even one merge can give you approximate position, if you can time it to one single incident.
It is why BE must change frequently and code words (not talking about brevity which are not code words) should be used … and base numbers as well.
-
Here (Attachment) how to use HSI for a Fix-Fix methode with BE calls…
-