How is the Bf109 supposed to function without guns?

[Bilbo_Baggins]

Ladies and gents, reds and blues,

 

Just wondering how the BF109, mainly the G2, for so long now, is supposed to function without firing guns? This critical problem has been around ever since I can remember now, and you can't help but wonder what the developer's of this sim were thinking when a BF109 is completely unable to participate in the fight without working guns, for this long.

 

Folks have been waiting, and waiting, through updates and fixes, yet this still remains. Why in hell does a BF109 still not have working guns so much of the time? They need to sort this out.

 

Why are they working on new content with total disregard for critical bugs like this? It beggars belief. I would like to know how a BF109 is supposed to participate in a combat flight simulation without any guns please.

 

RGDS

Edited September 22, 2018 by Bilbo_Baggins

[Thad]

Very evasively. ?

 

But I have never experienced this claimed game bug. 

Edited September 22, 2018 by Thad

[JonRedcorn]

Haven't had the gun bug one time in the 250+ hours I have in the game. Flown 109's half of that time.

[ethelward]

It's true I have the gun problem from time to time when playing blue. But one can check the ammo counter before taking off and discovering the bad new in flight; thus reducing the effective impact of the bug.

[BraveSirRobin]

There are 2 very simple solutions to this problem:

 

1.  Look at your ammo counter before taking off

2.  Fly VVS aircraft

 

critical?  Lol

[LeLv76_Erkki]

See the indicators above ammo counters, if they're fully black you have no rounds chambered and the gun bug, regardless of what counters(gray-blue bars) say.

[Willy__]

50 minutes ago, 15th_JonRedcorn said:

Haven't had the gun bug one time in the 250+ hours I have in the game. Flown 109's half of that time.

 

I get on almost half of my flights, happens more on some planes than others(G2 for example), but there's a trick that fix it, while on the loadout screen just choose the one that says "Empty" and then choose back the one with ammo. Sometimes I wonder if the testers and devs actually play the game....

 

Edited September 23, 2018 by Willy__

[BraveSirRobin]

24 minutes ago, Willy__ said:

 

 Sometimes I wonder if the testers and devs actually play the game....

 

 

That’s how they figured out that this isn’t a significant problem.  

[PB0_Foxy]

Had this weird bug tonight flying the G2 on Wings of Liberty

[Bilbo_Baggins]

1 hour ago, BraveSirRobin said:

 

That’s how they figured out that this isn’t a significant problem.  

 

Because it's a blue only problem, and that makes no guns an insignificant problem, despite being a combat flight simulator. Is there ever any end to BSR's apologist drivel?

[BraveSirRobin]

22 minutes ago, Bilbo_Baggins said:

 

Because it's a blue only problem, and that makes no guns an insignificant problem, 

 

No, it's an insignificant problem because there are 2 very simple workarounds:

 

1. check the ammo counter

2.  fly VVS aircraft

[[TWB]Sauerkraut-]

214 hrs and I didn't even know this existed.

[SharpeXB]

I’ve been playing this sim since early access and flown all the 109s a lot. I’ve never seen or heard of this problem. 

[Gambit21]

4 hours ago, Willy__ said:

 Sometimes I wonder if the testers and devs actually play the game....

 

 

Sometimes I wonder why certain people don’t think before they type.

[Finkeren]

6 hours ago, Bilbo_Baggins said:

 

Why are they working on new content with total disregard for critical bugs like this? 

 

I’m sympathetic to those who experience this bug, because it does sound quite annoying. It is, however, also apparently a fairly inconsistent and infrequent bug, that seems to affect only some people or some specific servers, which is likely making it hard to quash.

 

But when you write stuff like above, you lose me completely. How do you know, that the testers and/or devs are showing disregard for this bug? And who are you to demand, that they drop everything on their agenda and stop development on the three different titles they have in the pipeline in order to hunt down one elusive bug?

[Ropalcz]

12 minutes ago, Finkeren said:

 

I’m sympathetic to those who experience this bug, because it does sound quite annoying. It is, however, also apparently a fairly inconsistent and infrequent bug, that seems to affect only some people or some specific servers, which is likely making it hard to quash.

 

Its everything but unfrequent - I see you never fly online. If you are shot down and captured/dead in 109G or 190A and you spawn on the airfield afterwards, you get this bug almost always. (WoL)

 

Its going on for several months but no one sees it as a problem...

Edited September 23, 2018 by Ropalcz

[Finkeren]

18 minutes ago, Ropalcz said:

 I see you never fly online. 

 

Wrong.

19 minutes ago, Ropalcz said:

 If you are shot down and captured/dead in 109G or 190A and you spawn on the airfield afterwards, you get this bug almost always. (WoL)

 

As I said: Appears to be server-specific.

20 minutes ago, Ropalcz said:

 

Its going on for several months but no one sees it as a problem...

 

This is clearly false. Everywhere you look on this forum there are people complaining about this.

 

As for the devs not seeing it as a problem. You have no basis for saying that. At all.

[Bilbo_Baggins]

1 hour ago, Finkeren said:

 And who are you to demand, that they drop everything on their agenda and stop development on the three different titles they have in the pipeline in order to hunt down one elusive bug?

 

Finkeren, with all due respect, who are you to even comment on this bug having never even experienced it- you're never online bud. You say infrequent, but in a G2 this is happening very often. 

Edited September 23, 2018 by Bilbo_Baggins

[RedeyeStorm]

I had this ones, but a long time ago. If I rembember correctly you can solve the problem by reloading (alt r) while on the ground. Before or after engine start I don't remember. 

 

I fly all planes online and usually pick the side that has fewer pilots. End up flying lot's of VVS :). May be why I haven't seen this bug a lot.

 

[Finkeren]

1 hour ago, Bilbo_Baggins said:

 You say infrequent, but in a G2 this is happening very often. 

 

Yet a lot of people who fly 109s online say they never experience it. At the very least it is a very inconsistent bug.

 

As I said: It’s not that I don’t feel for the people who experience it. A bug like this extremely annoying. Nor do I have any problem with people calling attention to it. It’s the demand that the devs drop everything they are working on, until they solve this one issue that bugs me. That’s simply not how it works.

 

 

[LeLv76_Erkki]

I think it only happens online. So far I've only had it in 109 G-2, G-4 and 190 A-3. Occurs maybe every other time on the first flight I start after joining server or a new map has been loaded, and never after its been fixed(by choosing empty loadout, back to brief, back to loadout and choosing wanted loadout).

[Talon_]

I've had this bug once in all my time playing this sim, in a G-2. Never in any other aircraft, blue or red, and it's very simple to avoid by just watching the ammo counters during startup.

 

I think it's hilarious that some posters believe it's "yet another stealth nerf" to German aircraft ?

[=RvE=Windmills]

Does it happen outside of WoL?

[LuftManu]

This only happens on WOL server. It's rather a server bug than a game bug. You should contact them. Funny how this doesen't happen on VVS aircraft on their server.

[=RvE=Windmills]

I've had it happen on an La5.

[CountZero]

15 minutes ago, LF_ManuV said:

This only happens on WOL server. It's rather a server bug than a game bug. You should contact them. Funny how this doesen't happen on VVS aircraft on their server.

 

It happends on other servers also, its game bug

 

 

[LuftManu]

My bad then. I only experienced this bug on WOL, on 109s

[R3animate]

I mainly fly the G2 in Career and the F4 on Coconut's Ex. -- never had this bug occur yet. Might just be WoL.

[Sunde]

3 hours ago, Finkeren said:

 

Yet a lot of people who fly 109s online say they never experience it. At the very least it is a very inconsistent bug.

 

As I said: It’s not that I don’t feel for the people who experience it. A bug like this extremely annoying. Nor do I have any problem with people calling attention to it. It’s the demand that the devs drop everything they are working on, until they solve this one issue that bugs me. That’s simply not how it works.

 

 

It pretty much is tho, this definitely counts as a serious bug. And that should really warrent a hotfix. No its not completely game breaking, but the 109 is one of the backbone fighters and having it randomly disarm is not good at all. 

[Mauf]

As many people have mentioned:

1.Check your ammo counter for the black indicators.

2.In the loadout, switch to empty guns and back to your ammo of choice.

 

It's annoying but it's not hard to avoid. So stop the bias accusations.

 

This sounds very reminiscent of the quick mission bug where restarting a mission put you onto an airfield rather than the altitude you selected. Reselecting the altitude fixed the issue and same seems to apply here. Seems like the game for whatever reason defaults to the empty loadout internally, whether it's caused by the mission from the server side or the game itself.

[-TBC-AeroAce]

MP has had a lot of bugs since the last update. My guess is that this will be fixed by the next update as part of the netcode fix.

[Rolling_Thunder]

I find it hilarious that folk say it's an axis only problem when they only fly axis planes, having no experience of the Soviet side. They claim dev bias when they fly with axis bias, choosing to join the axis side when the teams are stacked 4-1, or more, in favor of the axis. 

Check your ammo counter before tearing off across the fields to get airborne or fly Soviet is sound advice. Sadly few will pay any attention to it and rather Whine about dev bias and feel persecuted.

[Nightrise]

Its happened to me a few times in the g2/g4. My hope is it doesn't happen to me ion TAW 

[SYN_Mike77]

If this is an online only thing, and only on a few servers, how are testers supposed to find it?  Testers, by definition only test the next to be released build.  That build is not on WoL or any other public server.  I've also never heard of it showing up on the test online server.  

 

We can't catch a bug that doesn't exist in the testing world!

[LeLv76_Erkki]

9 minutes ago, Rolling_Thunder said:

I find it hilarious that folk say it's an axis only problem when they only fly axis planes, having no experience of the Soviet side. They claim dev bias when they fly with axis bias, choosing to join the axis side when the teams are stacked 4-1, or more, in favor of the axis. 

Check your ammo counter before tearing off across the fields to get airborne or fly Soviet is sound advice. Sadly few will pay any attention to it and rather Whine about dev bias and feel persecuted.

 

Its not hilarious and it doesnt seem to happen for Allied planes, or even Axis planes other than 109 and 190. We would see complaints of guns not working in general if more different plane types had it. At least 109 and 190 are fortunate to have the counters so the bug can be noticed without test firing. Planes like Yak have so little ammo that I would be furious if I had to test if guns work every time I took off. Its a bug of some kind, unrelated to bias or side stacking.

[HansBlitz]

109s and 190s that take off without pilot noticing no ammo had had the pilot head space vaccum exceed tolerance.

[Guest deleted@83466]

1 hour ago, SYN_Mike77 said:

If this is an online only thing, and only on a few servers, how are testers supposed to find it?  Testers, by definition only test the next to be released build.  That build is not on WoL or any other public server.  I've also never heard of it showing up on the test online server.  

 

We can't catch a bug that doesn't exist in the testing world!

 

Don't get me wrong, I can't stand the whiners who see anti-luftwaffe conspiracies in every glitch, and I don't think this gun bug that they speak of is anywhere near as critical as they are making it sound (because there is a very simple workaround).  However, I really don't like to read statements like the ones I've bolded above.  If there is a bug that exists in an operational environment, then it needs to be looked at in that operational environment, if possible.  The whole purpose of testing software is to catch or prevent bugs from happening in the build version that the consumers actually end up using, not simply preventing them from happening in a pristine test environment.  

 

So I don't side with the whiners crying foul on this one, but if there is a bug (and in this case, there absolutely is a bug), and the testers need to get on WoL or wherever to track it down, then that's what they should do.  It might be on the server side, and nothing to do with the software baseline at all.   But helping to reproduce the bug and producing theories about what factors are triggering it,  is indeed part of what a good software tester does, even after a build leaves the factory...maybe even especially so, because when software goes live, it's no longer a potential problem, it is now an actual problem.

Edited September 23, 2018 by SeaSerpent

[HansBlitz]

Oh and yes I've been guilty of that.

If you notice there's no ammo, exit the mission, go to setup for the plane, select no ammo then select the ammo. That has cleared it everytime for me.

[LeLv76_Erkki]

4 minutes ago, HansBlitz said:

109s and 190s that take off without pilot noticing no ammo had had the pilot head space vaccum exceed tolerance.

 

Its easy to miss as counters still show full ammo. Its only the chambering indicators above the counter bars that have turned fully black to mark no chambered rounds.

[SharpeXB]

10 hours ago, Ropalcz said:

 

Its everything but unfrequent - I see you never fly online. If you are shot down and captured/dead in 109G or 190A and you spawn on the airfield afterwards, you get this bug almost always. (WoL)

 

Its going on for several months but no one sees it as a problem...

If it’s repeatable like that, just make a track and bug report in that forum section.