Yesterday, Thissler and I sat down, and tested a mutual theory. (I'm naming it after Thissler of course. as thiss was the victim of it more than I was when we played with sivar previously!) The theory was, it was Disables causing the weapon lockouts.
This theory seems to have panned out, and would also explain quite a lot of times when it used to occur in the past as well. We tested, the following, PSW1, 2 and 3, and Tricobalt weapons.
As you can pretty clearly see, there is no AMS, and no scramble on the map here.
Something to note here, is PSW1 seems to be doing this the most frequently out of the three shockwaves, shockwave 3 seems to knock out the most weapons at once, most frequently.
We eliminated every variable, by pouring through previous footage and this was the only constant, so this is what we tested. It is not (at least not this particular bug) AMS or scramble. It does make sense however for there to be confusion on this, as ships packing scramble also tend to be carrying a PSW1 or 3. Or for it to pop up in subsequent matches, as PSW1 is one of the most reliable methods for disabling extend shields.
The reason we suspect tricobalt does not perform this as reliably (as we could not catch it on camera) is it's stun duration is much shorter, thus the odds of it catching a weapon mid cycle are much lower. This weapon lockout seems to occur, during mid firing animation, or just at the start of the cycle. (most commonly mid point)
Do other disables knock out weapons? I do not know yet. As we did not have the resources to test them all.
I do have more videos of getting PSW to do this, as if the 12 minutes of watching my guns fall silent one by one was not enough already.
Given that this happens in Fleet Events occasionally, that is also unsurprising given the use of shockwave torpedoes by various NPCs, shockwaves by romulan warbirds, which also convers the Vault and all of the reman missions come to think of it, several pve missions as well.
Does this happen in matches with no PSW torps, PSWs, or trics? We simply do not know. This however is by far the most reliably method of capping it on camera that I have seen to date. Perhaps when computer frame rate drops, or during lag spikes you can also catch a weapon mid cycle and cause a lockout, but such a thing is pure speculation on my part, and would be nigh impossible to reliably reproduce (as you can see it was hard enough reproducing this, which is why there is 12 minutes of footage here, and almost 20 minutes of other video footage, during our testing that I have not yet uploaded) you have to catch the weapon cycle just right for this to happen.
This can also cause abilities on your power to tray to white box as well such as Distribute Shields, and bridge officer abilities. I have a second video showing this as well. In the case of abilities on your tray, this only triggers when the ability is started it's initial activation when the box is white, and you have to be stunned during that time to get it to occur most reliably. Distribute shields is the most common because this ability is activated most frequently on the power tray. Other abilities have longer durations, and cool downs so it is less likely they will be caught, but it can happen to them as well.
I have lots more footage of this happening, and even managed to catch distribute shields being locked out on film as well. If need be I can make more movies demonstrating how easy this is to replicate. Do note, this video is 12 minutes long, so you have to be fairly consistent at bumping the buttons over and over again to get it. It does not happen every time psw is hit, though by the end of our last test Thissler and I were able to consistently knock each other's guns silent, by utilizing buff and debuffs as well. (Sub nuc seems most effective here as it lengthens the CD cycle for -everything- including activation, and weapon cycles. Which gives the PSW more time to knock things out)
Nice work. I have also had this happen more and more where I'm hit by disables. The first time noticed it happening was a game where there were lots of boarding parties and marauding force shuttles, so the disables from those also seem to trigger the problem.
Nice work mav, there for the devs Borticus etc I would also like to add that when you saw the white glow around some of the weapons, this also often happens with "Distribute Shields" icon, where I warped out of a PVP match and the distribute shields kept enabling constantly, and the icon kept glowing white around it.
I'm pretty sure both are very well related to each other.
I have seen the "white Box" issues manifest even when one is just trying to activate too many powers too quickly in combat and somehow lock out the "WB' power. This seemed to definately happen to my weapons, torpedoes more often than not, the most.
I've alwsy had to log out and back in to fix it.
Originally Posted by staq16
The Federation may have all the superficial attention - but the game engine has a Klingon heart that lives only for battle.
Originally Posted by smiecho
I'm seroiusly thinking about leaving this game for a while.
Nice shots, I do have a few questions though. I'm sure most of these are on the minds of others that are just to shy to ask them.
1.) Is Lymuv as sexy in real life as in these videos?
2.) Does your ship not have an 8-Track as standard equipment? (teh moosic went away!)
3.) How can you stand yourself for shooting a ship as stunningly good looking as teh Marmot?
4.) Should I change the name to H.O.K. as I'm fairly certain I'm no longer in House of Duecelon?
And some NON questions. Just a note. Swapping weapons out didn't clear anything but the white box. New weapons worked. Old weapons didn't. You could put the old weapons back in and the box is gone, but nothing fires. Tre annoying.
And yes NPC's using PSW torpedo ability cause this also. Sooper annoying.
Cheers and ty for watching.
and Mav, next time get my good side in the closeups. sheesh.
So the problem is basicaly the activation delay/phase of abilities - when they are on regular cooldown, it doesn't happen?
Ablative Armor has a pretty long activation delay (in my exploding LRSV-R experience), could be a power to test this with. If it wasn't for the long cooldown of AA itself - get it wrong once, wait forever for your next try...
It's interesting that weapons "remember" this bug. Seems a lot more of information is stored about the items in your inventory than I'd expect.[/Tangent]
It does seem like the weapons are remembering that they are broken. And the bit about the cooldowns may or may not be accurate. Hard saying not knowing really. I know I've had evasive interrupted it seems almost AS I was activating it. I certainly didn't get very far with it. Normally I do. Its my thing as it were.
And it is sorta funny that this brings us around to CD's again. Not knowing at all how those things are coded in makes anything I would put out there just a wild ass guess. It seems like turrets were going offline most often. That could just mean that they fire more often so they are most likely to be 'caught in the act'.
Turret: "Okay I just fired!"
Turret: "Waiting my turn to fire again!"
Turret: "Waiting my turn to fire again!"
Turret: "Waiting my turn to......now where did I put my nice cup of tea?"
Is it an interrupt on an interrupt and it just sends them over the edge? Not sure but now I need a drink.