I have a lot of experience in online multiplayer and one of the problems we always find ourselves is that, flights that go to the same area of operation (FAOR), carry completely different AWACS frequencies and yes, of course I understand it, I know that in In real life, this is the case, but the problem is that, in real life, the different controllers operating in AWACS coordinate with each other and coordinate their assigned flights, depending on the circumstances (SA). The problem is that taking it to a simulator would be somewhat more complex.
A possible solution, which in its day I gave to the developers, I don’t know if they listened to me, is to assign a unique AWACS frequency for each FAOR (and not as it happens now for flight packages) like this, if there is no coordination between the IA AWACS controllers (as now happens), there will be it between humans in multiplayer as long as they are within the same FAOR (since we all share the same AWACS frequency). I think that the current situation, in which the simulator is, of a radio bubble is NOT the solution (also, for those of us who know the subject, it is unrealistic). And returning to the subject, the frequency plan, if it is assigned by callsigns, which is not a bad idea, should be assigned without repetition of frequencies. Doing a false encoding is not very realistic either, since if two flights are on the same frequency, in reality we would step on each other and it is about doing something realistic. It’s what I think.Regards my friend
Well, your post is condensated, but you covered it…
When you say that if 2 Military flights are on the same frequency they step on each other, it’s in RL? Because as Mil-Comm uses Trunking(read below), so my guess is that it’s because they’re on the same channel.
With deeper thinking, I agree that isolating the player’s intra-flight radio-freq isn’t a realistic solution then…
The problem is due to the multi-callsigns sharing, this still needs to change…
One “almost-simplified-realistic” solution is in this case, to throw the OPFOR(non-NATO countries) on a different “callsigns group” than NATO and a different VHF frequency band.
Doing so it would free up frequencies and cut down the frequency sharing…
Or, maybe changing the frequency distribution from WideBand(25KHz separation between 2 channels) to NarrowBand(12.5 KHz chan. sep.) would be an other solution?
Doing so, this allows setting OPFOR callsign’s frequencies on the NB freqs and keeping NATO-Forces on WB.
On an other side, I need to write a correction about my Original Post:
Radio-Comms Trunking
I’ve done some deeper research about IRL VHF military radio systems(as far as publicly available informations go) and I’ve learned that it’s using radio trunking system to secure communications, (in commercial R-C, an RSA key is used as additionnal security in some cases). Trunking is in fact digital radio-communication and uses, in simple words digital data insertion on the signal, to protect from unauthorized access(which is a form of encoding/encryption).
Some sources says that, someone having the right equipment and knowledge, it’s possible to listen to Military Comms in some locations, but not emitting(As emitting requires VERY specific radio programmation).
So in a way, in my O.P I was right, but also miss-leading…
The real military radios are in fact using channels that are programmed in the radio system, not frequencies. I don’t know about exact channels identification, but they don’t use the frequency(as it appears to be in F-BMS as it is), which would kind-of mean that the comm are unprotected(except for the Military-reserved VHF band), similar to public(and basic/low-end commercial) air/marine navigation VHF radios.
So if we look at the(and for) realism, the present system isn’t realistic…
Knowing a little bit about commercial(non-military) Radio Trunking specifications myself, I guess a realistic implementation might be pretty hard to implement in F-BMS…
Another solution would be a simplified trunking system if possible, as something like this:
- No changes to UHF system(didn’t research RL Mil UHF radio-comms)
- VHF Frequencies stay shared, BUT the radio-comms uses channels(next point)
- Callsigns-assotiated channel-ID(numeric I guess) are used as channels isolate flights from each-other, but it’s possible to share by using the same Chan-ID.
- Package-assotiated channel, for package co-ordination(in the case of am all-human multiplayer package) /// just an idea, IDK how MP radio works
I did my best to keep it clear…