MK131

[D3adCZE]

Hello,

recently on Berloga in 109G14, and sometimes with 109G6, mg131 machineguns stop shooting when I get ~150 meters behind an enemy, and only the cannon works. When I get out of shooting position, the machineguns work again. Am I the only one who is experiencing this?

Thank you gentlemen.

Edited August 17, 2018 by CSAF-D3adCZE

[6./ZG26_Gielow]

Russian bias? !?! ?

Quote

 

 

[[APAF]VR_Spartan85]

.....Sooooooooooooooo.... I haven’t heard of this before...the machine guns have an issue yeah?

 

 

I think that’s what we were talking about..

Edited August 17, 2018 by spartan85

[Asgar]

8 hours ago, CSAF-D3adCZE said:

Hello,

recently on Berloga in 109G14, and sometimes with 109G6, mg131 machineguns stop shooting when I get ~150 meters behind an enemy, and only the cannon works. When I get out of shooting position, the machineguns work again. Am I the only one who is experiencing this?

Thank you gentlemen.

Do you have any specifics for the bug? steps to reproduce?

5 hours ago, Bilbo_Baggins said:

 

Blue guns have been plagued with this critical bug for some time now. Is there a reason why hasn't it been fixed? 

 

Luke,

 

You know exactly what he's talking about if you claim to be an official tester

 

never heard of or seen this bug. ammo disappearing from guns cause you're close to enemies? are people just starting to shoot at things from 1km away and run out before they get close? because i never had ammo disappear on me in the hundreds of ours i played the BoX games and in the 10s of hours i've played the current update. offline and online.  

same goes here: Do you have any specifics for the bug? steps to reproduce? 

 

P.S.yeah he totally "claims" to be a tester, i'm sure the made his tester batch himself with some crayons

[D3adCZE]

Video here:

 

Will find a way to reproduce it. Gimme few hours.

Edited August 17, 2018 by CSAF-D3adCZE

[Asgar]

okay... 100% honesty, hold on to your butts... that video is useless. 

all we see is a reply in 3rd person, no ammo indicators can be seen, so you guns might as well just have run dry. people tend to shoot MGs first and with the 131s that's a good way to run dry on MG faster than with the cannon. 

for all we know you flew at that enemy and only pressed the "fire cannon" button and that's it. there is really no telling what happened. but thanks for going through the effort to make and upload a video. 

[D3adCZE]

8 minutes ago, 6./ZG26_Asgar said:

okay... 100% honesty, hold on to your butts... that video is useless. 

all we see is a reply in 3rd person, no ammo indicators can be seen, so you guns might as well just have run dry. people tend to shoot MGs first and with the 131s that's a good way to run dry on MG faster than with the cannon. 

for all we know you flew at that enemy and only pressed the "fire cannon" button and that's it. there is really no telling what happened. but thanks for going through the effort to make and upload a video. 

Yes, I understand, hope this will show the issue better. Working on how to reproduce it.

 

[Asgar]

this is just an idea, since we have some WW1 kites now. maybe, just maybe the gun jam mechanic somehow transfered to the WW2 planes, if you encounter it again, try the reload button/combination "LAlt+R" and see if that gets the MGs working again. 

Edited August 17, 2018 by 6./ZG26_Asgar

[D3adCZE]

Will test it, thank you.

[Cybermat47]

AFAIK no-one else is experiencing this, so it could be that your install is corrupted somehow. I wouldn’t recommend reinstalling until you’ve gone through every possibility, though.

[RavNg00se]

I have been experiencing this issue as well, was actually searching the forum for existing posts yesterday. I have only noticed this issue with the mg131 though. 

 

For me I havent paid any attention to distance from enemy, the only thing i have noticed is that if i press the mg button, it often fires for 0.5 seconds and then stops.

Pressing the button again several times does nothing, until a few seconds later (anywhere from 5-20) when it starts working again.

If i remember correctly, its pretty much the same if i press "fire all guns", but the times it has been blaringly obvious was when I was only trying to fire mg.

 

I noticed it when the 109G-6 came out and also experience the issue in the G-14.

 

 

[Asgar]

is this something you only notice offline, online or both?

 

8 minutes ago, RavNg00se said:

I noticed it when the 109G-6 came out and also experience the issue in the G-14.

 

since the G-6 release? I feel more and more like agreeing with Cybermat that this might be a corruption issue, because if this was a general issue we should've had more reports on this by now

Edited August 17, 2018 by 6./ZG26_Asgar

[D3adCZE]

27 minutes ago, 6./ZG26_Asgar said:

this is just an idea, since we have some WW1 kites now. maybe, just maybe the gun jam mechanic somehow transfered to the WW2 planes, if you encounter it again, try the reload button/combination "LAlt+R" and see if that gets the MGs working again. 

So, I have noticed few things.

 

1) The bug only appears when pulling lead to shoot at the enemy when closer than ~200 meters. I guess it might have to do something with Gs.

2) However, when I tried to test it only Gs trigger this bug, the test was negative, almost blacked out and I was still able to shoot.

 

My guess is that the game checks the distance from enemy and G's, when I am close enough, it checks the G's I am pulling and if(Gs > CONST) it jams the guns. However it automatically "unjams" them when I fly away from the enemy, again certain distance.

 

This has been observed offline and online on Berloga, since G14 is nowhere else. Will test 190 A8 now.

 

Edit:

It happens with 190 A8 as well. Will perform some tests on bombers.

Edited August 17, 2018 by CSAF-D3adCZE

[Cybermat47]

9 minutes ago, CSAF-D3adCZE said:

My guess is that the game checks the distance from enemy and G's, when I am close enough, it checks the G's I am pulling and if(Gs > CONST) it jams the guns. However it automatically "unjams" them when I fly away from the enemy, again certain distance.

 

Interesting idea, you should check with one of the testers or developers to see if such a mechanic exists.

[PainGod85]

Is there historical precedent for the MG131 failing to cycle under load?

[Gunsmith86]

9 minutes ago, PainGod85 said:

Is there historical precedent for the MG131 failing to cycle under load?

No 

[PainGod85]

Just now, Gunsmith86 said:

No 

 

Yeah, that's what I thought as well.

[Asgar]

yeah, for german standard, pretty big amount of propellant (so lots of energy to cycle), robust mechanism and a very reliable electrical trigger system. there shouldn't be any issues with the 131

Edited August 17, 2018 by 6./ZG26_Asgar

[RavNg00se]

I can add that I experience this issue flying straight and level and not pulling any Gs. Its been the most frustrating when tailing an unaware enemy on his six, open up and only a short burst comes out (out of mk108 ammo). Had it happen both online and offline, pretty consistently too (about once per 2 sorties at the very least).

 

 

[PainGod85]

So it's probably not related to G load. Interesting issue.

[D3adCZE]

Ok gentlemen, thanks for feedback and help. Found out that the problem was between joystick and the game. More precisely the config. After switching from Logitech 3D to T.16000M game somehow managed to sneak my trigger button into reload button. So if anyone sees this issue, look into the key mapping and check weapon reloads.

Moreover, G2 couldnt reload it's weapons? Because I did not have these issues with MG17.

[Cybermat47]

Just now, CSAF-D3adCZE said:

Ok gentlemen, thanks for feedback and help. Found out that the problem was between joystick and the game. More precisely the config. After switching from Logitech 3D to T.16000M game somehow managed to sneak my trigger button into reload button. So if anyone sees this issue, look into the key mapping and check weapon reloads.

Moreover, G2 couldnt reload it's weapons? Because I did not have these issues with MG17.

 

Interesting. Glad to hear that the issue is resolved.