[BUG] Beam and Torp space abilities broken since today's patch

dragonsbite

I did a fleet defense and looked at my logs. 20 people obviously. Was wondering why my beam boat wasn't doing as much damage as expected. Looking at the logs i can see quite a few problems. Some weapon abilities will not allow the weapon to crit while using said ability. Here's a short list of abilities that shows which did NOT allow the weapons to crit while using said ability.

Beam Fire at Will does NOT let weapons crit (confirmed)
Beam Overload does let weapons crit? (sample size to small to confirm)
Torpedo spread does NOT let weapons crit (confirmed)
Torpedo high yield does NOT let weapons crit? (sample size to small to confirm)


I'll update the list after i grab a pizza. Reply if you've looked at your logs and can confirm other things not critting. And remember hitting a shield will never show as a crit. Only hull hits show as crits. So keep this in mind when checking for crits. Right now i can only confirm 100% that Beam fire at will and Torpedo spread have this problem. I'll check beam overload and torp high yield a bit more later. Cannon abilities are working fine in case anyone was wondering.

dahminus

My logs show I'm critting...but the critd seem to be lower

paxdawn

I tested my engineer. In khitomer, infected and cure. My beams still crit but my bfaw does not crit anymore.

So it may be related to abilities not critting.

my DEM crit chance is halved compared to pre patch. Need to test DEM more to get better results.

dragonsbite

Your logs show you're critting what? Please be more specific.

Cit D seems to be fine here. Non fire at will beam array hits are critting for over 7k here. Here's how my beams looked like during that fleet def run.

Plasma beam array fire at will II max hit 3,728 with 3,413 hits and 0% crit rate
Romulan plasma beam array fire at will II max hit 3,759 with 671 hits and 0% crit rate
Romulan plasma array max hit 7,773 with 1,600 hits and 12% crit rate
Cutting beam max hit 7,477 with 478 hits and 10% crit rate

Looking at the logs of the other 19 people during that run shows the same results for torpedo spread and fire at will. Not 1 crit out of 20 people using those 2 abilities.

brandonfl

Okay, just finished testing this one. Here's what I determined. The Crits are there.

The combat log isn't attributing Crits during FAW to FAW. It is attributing them to standard beam attacks.

Method: Had a FAW cruiser shoot at me with nothing but FAW, no standard attacks, while parsing. During this test, you could see the Crits in the flyovers and the Crit Hits were appearing in ACT as standard beam attacks while the Crit numbers on FAW never changed (though swings/hits were changing)

Beam Overload Crits were reporting correctly.

disclaimer: this was a very casual test, I was simply watching for changing numbers at specific times. The data sample is very small. I was also unable to test TS and THY during this test.

dragonsbite

I'm not sure what you're saying. It sounds like you're saying that a FAW crit will show as a regular beam array crit instead of a FAW crit. I just tested this at starbase 234 and you are wrong sir. I do see crits but they were from my cutting beam. At no time did i observe 1 FAW crit via watching the flying text. Nor were any in the in game combat chat nor were there any in the combat log file.

In case you don't understand the flying text it's white=shields. Yellow=hull. A crit will say "Critical" in yellow. But it will only say it for hull damage in yellow and never say it for shield damage in white. No idea why they do it this way. But it is what it is and it's been this way for a long time. If you take damage it's white=shields and red=hull. I'll not spend to much time on this as it may confuse or derail the main point of the post. At that is that torpedo spread and Fire at Will and possibly others do not let your weapons that are firing those abilities to crit at all while using those abilities.

pokersmith1

I think what he is saying is that when FAW crits, the combat log is saying it's not FAW critting, but it's a regular beam attack critting. So obviously this is a display/text error. Maybe more tests are needed.

Also, its more reliable to look at actual combat log data than to watch for the visual indicators.

dahminus

It is a confirmed bug now...

My apologies, the crits I was seeing during bfaw must have been my kcb. I was skewing my own testing...very sloppy on my part.

To the OP, kudos