Weapon grouping bug

Just lost a Daredevil to the Angel Burner (Dramiel) thanks to this annoying weapon grouping bug. Had both guns grouped but apparantly only one gun was firing…

Not a big deal, because it was the usual cheap buffer fit as seen from Hateless. But still, this specific bug is haunting me since I started playing in 2016. I kind of made it a habit to ungroup and group all weapon after undocking the first time. Well, this time I forgot to do it.

Anyone else has the same problems with weapon grouping?

Don’t remember to have seen such issue in 10 years. Are you sure only one weapon fired?

You need to be careful with overheating, If one weapon burns, the whole group disables, and you have to regroup to get the working ones together. But this is a different symptom.

Not when the game doesn’t do it’s intermittent one-second micro-freezes every minute.
My bug is Local. The window disappears on dock & undock… that’s one annoying bug.


Fifie recoils at :bug:

After analyzing the logs and the lossmail and comparing with Sisi, yes, I’m pretty sure.

Combat logs shows 24 hits from me to the burner. Killmail shows 136 rounds left on the 2 guns. Each gun can load 80 rounds, so only one round per hit was consumed:

127 to Burner Dramiel - Light Neutron Blaster II - Grazes
163 to Burner Dramiel - Light Neutron Blaster II - Glances Off
267 to Burner Dramiel - Light Neutron Blaster II - Penetrates
269 to Burner Dramiel - Light Neutron Blaster II - Penetrates
324 to Burner Dramiel - Light Neutron Blaster II - Smashes
333 to Burner Dramiel - Light Neutron Blaster II - Smashes
737 to Burner Dramiel - Light Neutron Blaster II - Wrecks
341 to Burner Dramiel - Light Neutron Blaster II - Smashes
150 to Burner Dramiel - Light Neutron Blaster II - Grazes
228 to Burner Dramiel - Light Neutron Blaster II - Hits
301 to Burner Dramiel - Light Neutron Blaster II - Penetrates
225 to Burner Dramiel - Light Neutron Blaster II - Hits
291 to Burner Dramiel - Light Neutron Blaster II - Penetrates
194 to Burner Dramiel - Light Neutron Blaster II - Hits
330 to Burner Dramiel - Light Neutron Blaster II - Smashes
312 to Burner Dramiel - Light Neutron Blaster II - Penetrates
164 to Burner Dramiel - Light Neutron Blaster II - Grazes
242 to Burner Dramiel - Light Neutron Blaster II - Hits
144 to Burner Dramiel - Light Neutron Blaster II - Grazes
149 to Burner Dramiel - Light Neutron Blaster II - Grazes
267 to Burner Dramiel - Light Neutron Blaster II - Penetrates
192 to Burner Dramiel - Light Neutron Blaster II - Grazes
166 to Burner Dramiel - Light Neutron Blaster II - Glances Off
189 to Burner Dramiel - Light Neutron Blaster II - Hits

As always with turrets, the damage has a wide random range (0.5-1.49) but overall I cannot see any issue with the hit chance. Burner was webbed down with a 90% web and with a 83% web and I was keeping at distance 1,700, which is around the optimal.

One heated gun has an alpha of 271 TH + 271 KN. Burner has a resistance of 48.1% TH and 61.1% KN.
271 x 0.519 = 140.649
271 x 0.389 = 105.419

Combined around 246 dmg. Random range from 143 (Graze) to 366.5 (Smash).
This seems to match with the values seen in the logs.

Guns were freshly bought and never used before, meaning they were not pre-damaged or something.

possible your weapons weren’t grouped and one was hidden under part of your overview ?

Also thought about this. But all 3x8 slots are visible and I wasn’t drunk or tired.

Well, I will try to reproduce this behaviour but heaven knows which combination of circumstances caused it.

I managed to reproduce this bug reliably this way:

  1. Take an unfit Rifter from my home station to Jita 4-4.
  2. Use the fitting window to buy all modules and fit the ship.
  3. Group the guns while docked at the station.
  4. Load ammo while docked at the station.
  5. Undock and head to my home system.
  6. Dock at my home station.
  7. Get filaments.
  8. Fly to a safespot.
  9. Enter the abyss.
  10. Fire the grouped weapons.

I uploaded a bunch of screenshots showing the bug in action, and used the in-game bug reporting tool to inform the game masters.

I hope this can help the developers locate the source of the issue and fix it.

Cool, it’s very nice that you managed to reproduce it!

With a clear reproducer there should be a chance for the Devs to tackle this problem. If they get the time for it, that is.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.