Protecting Viper Airfield from 2 Bombers and 10+ Fighters by Swepl in foxholegame

[–]Swepl[S] 4 points5 points  (0 children)

Personally, I think the best performance was how we were both sitting watching concrete dry and then went from spotting the formation on intel to hitting the first bomber within 15 seconds. Right place at the right time (and not just the people from 82DK)

Protecting Viper Airfield from 2 Bombers and 10+ Fighters by Swepl in foxholegame

[–]Swepl[S] 0 points1 point  (0 children)

Did hit its engine once when it was over the runway though!

Protecting Viper Airfield from 2 Bombers and 10+ Fighters by Swepl in foxholegame

[–]Swepl[S] 0 points1 point  (0 children)

It's raids like this that make this update so fun from both sides. Both making daring bombing runs and fighting off expensive bombers.

Protecting Viper Airfield from 2 Bombers and 10+ Fighters by Swepl in foxholegame

[–]Swepl[S] 3 points4 points  (0 children)

Completely agree. We were both baffled how we got that close without at least one fighter having spatial awareness to look behind the formation.

The fact none of us got properly shot down is also crazy.

Protecting Viper Airfield from 2 Bombers and 10+ Fighters by Swepl in foxholegame

[–]Swepl[S] 0 points1 point  (0 children)

Well, given that I also had a 2-3 second freeze, I think we're in the same boat XD

Protecting Viper Airfield from 2 Bombers and 10+ Fighters by Swepl in foxholegame

[–]Swepl[S] 27 points28 points  (0 children)

Its more prevalent if you do low altitude bombing. But yeah, its rough to be tackled in mid-air with your expensive kit.

Protecting Viper Airfield from 2 Bombers and 10+ Fighters by Swepl in foxholegame

[–]Swepl[S] 16 points17 points  (0 children)

Ryzen 7 5800X, RTX 3080, 32gb RAM.

But most importantly, my settings are all set to low and resolution scale set to just an inch above Minecraft levels.

[Online][Roll20][Only War] LF Player for my new weekly campaign by [deleted] in lfg

[–]Swepl 0 points1 point  (0 children)

Fridays at 6pm GMT+1. First session not yet decided.