Is there a frequency for a multi-flight package?
-
As before, in 4.33, I fragged a typical OCA Strike package - one SEAD flight, one OCA Strike flight (me) and one ESCORT flight to cover our collective sixes.
In 4.33 I distinctly remember hearing chatter from a package that helped me with a situational awareness (like knowing if an escort flight is engaging those fighters scrambling to intercept us so bombers don’t need to worry).
In 4.34 the only way I know of is switching between default 15-16-17 VHF freq to hear all the flights in this given package, but I can’t do it all the time, plus that way I skip things from other flights incl. my own.Needless to say I quickly ended up being surrounded by 2x Mig29A (both of which I’ve managed to dispatch) and 2x Mig23 (one of which got me) due to lack of comms or even knowing if escort is doing anything useful.
Is there a general frequency/channel that will help me hear what’s going on in all of my package?
-
Hi Kraze!
Nope.
Each packages its own Tactical allocation (and there is already a lot of people on the feq with 20 a/c in a package! … and also a lot for the two WC in the AWACS!)
-
In 4.33 I distinctly remember hearing chatter from a package that helped me with a situational awareness
Not possible. You maybe had a feeling of SA … but actually it wasn’t.
How can you build an SA if you don’t know who is talking on the radio nor where are their position? Chatter in 4.33 for nothing but radio garbage/pollution. -
But how should I know if the package has pushed? If escorts are engaging? If I have my own flights doing stuff and if (in case of me being an escort) a flight is done with the job and leaving so I can do it too?
I mean in reality there should be some kind of inter-flight comm within the same package, otherwise how do they cooperate? -
But how should I know if the package has pushed? If escorts are engaging?
Those call are missing from day1 …
And here you have a good point. The frags exists (Departing push point, In, Out, Miller time, RTB … etc …) , but the coder in charge of comms didn’t managed yet to fix it.
Another coder was able to fix it but it seems that it wasn’t “properly” done (?) … so it has been reverted.Indeed we would really need those calls.
Full callings are also missing:
“Two Defending” … okay … but, Sepent1-2, Serpent 2-2, Sanke3-2 … who is “two” exactly?! … and where he is?
I mean in reality there should be some kind of inter-flight comm within the same package, otherwise how do they cooperate?
Yep … but only without the package. IRL, depending on the type of control provided, you need one AWACS per package since there are only two communicators per AWACS, imagine the workload for them with 20 a/c to manage.
Another point for you about SA, it that we had a bug in 4.33: As long as AIs/AWACS were giving a BE posit, info is useful for you whatever you/their position, since BE is common.
But as soon as threat comes below 30-20Nm, AWACS goes in BRAA, and BRAA is pointless for you if you don’t know who is talking and where their are.The bug was that any BRAA given to IAs by AWACS was “translated” in a BRAA relative to your position, which is wrong … especially in MP (each player were hearing a different BRAA relative to their own position) … This has been fixed in 4.34, it means that now, and BRAA given to an IA is pointless if you don’t know his position.