Bullseye help
-
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…
-
-
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
Just found out, that when I use the HSD cursor to locate the bullseye call, I can press TMS up and a waypoint is created
Very easy method, and a quick one too.
If the bullseye call is outside the HSD range I don’t bother. Too far away to engage anyway. -
…
If the bullseye call is outside the HSD range I don’t bother. Too far away to engage anyway.Thou be careful with your HSD range setting, if it’s set to 5NM, then you should care about it…
-
Just found out, that when I use the HSD cursor to locate the bullseye call, I can press TMS up and a waypoint is created
Very easy method, and a quick one too.
If the bullseye call is outside the HSD range I don’t bother. Too far away to engage anyway.what mode is this in? this is new to me…
-
No special mode, just one of MFDs in HSD and as SOI (AFAIK).
-
:rofl::rofl::rofl:@flyway:
Thou be careful with your HSD range setting, if it’s set to 5NM, then you should care about it…
-
No special mode, just one of MFDs in HSD and as SOI (AFAIK).
does not work for me. you can create a waypoint with the ICP mode for it, but not on the HSD.
you can TMS up on an existing STPT with the cursor when the HSD is SOI to change the current STPT to the selected one. thats the closest I know of with the TMS up on the HSD.
-
does not work for me. you can create a waypoint with the ICP mode for it, but not on the HSD.
you can TMS up on an existing STPT with the cursor when the HSD is SOI to change the current STPT to the selected one. thats the closest I know of with the TMS up on the HSD.
Ok. Maybe I just got lucky and hit a PPT. I’ll look into it.
-
You are making things harder than it should. You have already everything (Your bull’s posit on HUD, MFD, plus Bull’s symbol and bearing + distance on the MFD’s left down corner (activate bulls mode via ICP)
-
trainer: http://www.185th.co.uk/squad_info/training/BullseyeTraining.zip
THIS IS FUN aCTAULLY REALLY AWESOME STUFF
-
Those trainer are good but what you have to learn is the 1:60 rules. Basically, at 60 nm 1 degree of arc is like to travel 1 Nm. Beliving or not it is like that. So if you have a contact that is at 30 Nm from bullseye 1 degree of arc is like to travel 0.5 nm. Keeping that in mind if you are at the same distance it will be easy to understand how many miles to travel if you are not at the same distance you must make an estimation.
Look at http://www.maclittle.es/2008/08/09/situational-awareness/ . Use the translator, there is a good explanation inside.
After, to understand it perfectly you should study a bit of IFR, TACAN, VOR navigation. The main concept after the 1:60 rules is to use the point to point navigation to place your nose into the right heading to illuminate the target into your radar if you want to engage and if it is at a certain aspect and distance from you that is dangerous.
You may read the Bullseye_helper doc. I found it around here, it was taken from an url of a guy who explained the bullseye for Flanker virtual pilot. If you read it, the explanation it is giving , it is basically a point to point navigation explanation.
Flyaway did, too long time before me:):
Here (Attachment) how to use HSI for a Fix-Fix methode with BE calls…
Pages17-21_KF4-Checklist-FLIGHT Data.pdfNow that you know what to read, study and practice…
-
Those trainer are good but what you have to learn is the 1:60 rules. Basically, at 60 nm 1 degree of arc is like to travel 1 Nm. Beliving or not it is like that. So if you have a contact that is at 30 Nm from bullseye 1 degree of arc is like to travel 0.5 nm. Keeping that in mind if you are at the same distance it will be easy to understand how many miles to travel if you are not at the same distance you must make an estimation.
Look at http://www.maclittle.es/2008/08/09/situational-awareness/ . Use the translator, there is a good explanation inside.
…
Link above not working (at least for me).
About 60:1 rules, check here;
http://www.google.pt/url?sa=t&rct=j&q=&esrc=s&source=web&cd=7&ved=0CGkQFjAG&url=http%3A%2F%2Fwww.airforcedriver.com%2F47OG%2F86FTS%2Fnew%2520web%2FDOWweb%2FTRAINING%2520AIDS%2F60%2520to%25201%2520Rules.doc&ei=KVU7UvTGMpGh7Aa1toC4Bg&usg=AFQjCNEBgmXC5UejB56jRhNqJI1_DHI4aA&sig2=WH3npp3uWtGBOKyzR6bc0A&bvm=bv.52288139,d.ZGU&cad=rja
or here;
http://www.google.pt/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&cad=rja&ved=0CEEQFjAC&url=http%3A%2F%2Fwww.cnatra.navy.mil%2Febrief%2Fdocuments%2F01_Training_Air_Wing_One%2Freferences%2FCOLUMN%25204%2FINST%2520REFERENCES%2F60-1%2520rules%2520Jan%252007.pdf&ei=KVU7UvTGMpGh7Aa1toC4Bg&usg=AFQjCNFgEudFBxtZKpkj_gWJgqGuEpY5Ng&sig2=RGhCGW3aeMdM9VJuM24opg&bvm=bv.52288139,d.ZGU