As long as you have a 11.7-12.7 in your lineup (which allows you to fly in the battle), you can also fly any lower BR aircraft you have in the same lineup.
Rarely seen (especially such large BR differences), but just recently flew a Mirage F1C against an F-8E (10.3) which was also outside of my bracket (10.7-11.7)…
Well, it is indeed a huge topic but Gaijin can’t do too much about it, i have almost 2 and a half years playing air SB, the last few months and the amount of players that i saw going for a kamikaze mission (destroy base and then crash) it’s been increase alot, i hate does players bc they are the reason of Gaijin lowering the rewards in SB mode.
So kamikaze players are mostly premium account with premium planes that don’t care about losing SL bc obviously they won’t lose any has far as they destroy a base.
Also, When i start to play air SB, they were alot of full servers, now there’s like 1 in prop planes(3.3/4.3 - 4.0/5.0) and 2 in jets (10.3/11.3) and (13.0/14.7) thoes are the br that i see most often full but that’s not the problem
The problem in self is Gaijin that don’t give anything new to SB (Maps, missions, etc) and is bc the “Main” game mode is RB, so you can see always a update in that mode and is bc of that. We the SB Players have to just wait untill Gaijin remember that we exist
3 Likes
After being repaired (if needed), J-Out and you can change the loadout for a small SL fee.
This has been working since… forever.
This is what we call a ghost lobby, usually it means that a lobby in a certain map is duplicated within itself This means that the lobby itself has all players, but the games, usually in the same map, are separated and cannot be joined at will…
The worst I’ve seen happening was 3-4 lobbies in one (probably just 2-3 and one that ended and restarted), even with different maps, despite saying “denmark” or something like that and when it loads it is “sinai”.
It can also separate you from a squadmate, even if you are in a 2, 3 or even 4 man squad, which ruins any teamwork you were planning to do.
This error has been in various forms in EC since at least 2020. I am not confident enough to say it was there before.
At least they fixed the sound bug… mostly. But now we have the “floating balls of fire” instead.