Do MCH's oGCD abilities seem unresponsive to anyone else?

[Greedalox]

During Ixion FATE's, sometimes I can't press barrel stabilizer. It just wont let me even though Gauss Barrel is on. I then try Flamethrower and it works but doesn't fill up my heat gauge. I assume it is some sort of server issue that occurs when too many players are in one location.

Just had these happen to me today lol. Everything but BS and Flamethrower worked fine though.

[Bernkastelx]

Happens to me rarely when I use ley lines, it shows me using the animation then puts it on cd and it doesn't show up. Randomly happens in any content pretty annoying. Also noticed it around the end of heavensward.

[RichardButte]

Added a video of it happening twice to the OP.

Rapid Fire is pressed but fails to execute at 15 sec, Gauss Round at 30 sec:
https://www.youtube.com/watch?v=LBuShjLJChc

[Elnidfse]

like others have said I simply just mash the buttons until it comes out. I usually end up clipping a GCD but what can you do ¯\_(ツ)_/¯

[Cabalabob]

I find that the buttons aren't responsive enough to fit into the tiny wildfire window, it can get a little stressful trying to get everything off in 10 seconds.

I definitely think they could afford to extend wildfire and overheat duration to 15-20 seconds. It would relieve some of that stress and bring mchs damage up a bit.

[Kitfox]

Added a video of it happening twice to the OP.

Rapid Fire is pressed but fails to execute at 15 sec, Gauss Round at 30 sec:
https://www.youtube.com/watch?v=LBuShjLJChc

You're hitting your oGCDs before the previous animation lock is done, so they don't go off. Pay attention to the timing. You can only hit 2 oGCDs max between your GCDs and only one during Rapid Fire. All abilities have variable lengths of animation lock that prevents using other abilities at the same time. It also depends on your latency how fast the server registers that you've hit an ability so your mileage may vary.

I find that the buttons aren't responsive enough to fit into the tiny wildfire window, it can get a little stressful trying to get everything off in 10 seconds.

I definitely think they could afford to extend wildfire and overheat duration to 15-20 seconds. It would relieve some of that stress and bring mchs damage up a bit.

Long WF is extremely clunky to maximize on because sometimes it doesn't fit into fight phases at all and becomes literally a wasted ability when it doesn't have time to explode. I prefer the shorter window.

[Elnidfse]

Long WF is extremely clunky to maximize on because sometimes it doesn't fit into fight phases at all and becomes literally a wasted ability when it doesn't have time to explode. I prefer the shorter window.

There was nothing clunky about developing good timing.

[Clawbriar]

Only ever had this issue with redeploying turrets. Everything else works fine for me.

[Kitfox]

There was nothing clunky about developing good timing.

I vividly recall my raid MCH crying in A11S every time the boss went invulnerable with 2 seconds left on WF due to phase pushes or a target dying before the effect went off. There's no argument that a 20 second window is harder to fit into a fight than a 10 second one, whether you like it or not is up to preference I guess. I like being more flexible.

[Elnidfse]

I vividly recall my raid MCH crying in A11S every time the boss went invulnerable with 2 seconds left on WF due to phase pushes or a target dying before the effect went off. There's no argument that a 20 second window is harder to fit into a fight than a 10 second one, whether you like it or not is up to preference I guess. I like being more flexible.

20 second window? You seem to be under the impression that the wildfire window has changed that much. It takes near 20 seconds to trigger a wildfire now. 10 seconds of prep: split (2.5), slug (2.5) split (2.5) FT (1-3) plus the 10 second wildfire. So now instead of losing your wildfire you get to lose your ammo used to begin your wildfire. The very same ammo you now have to burn constantly to do competent pps. And with the shorter wildfire cooldown now, losing a wildfire (or two) is a bigger dps loss than delaying it ever was.

There was nothing clunky about good timing. When I was starting MCH at the beginning of HW my raid used to always make jokes about how I used to proclaim my wildfire was lost to a jump, "my wild fireeee!" I used to exclaim and this was in anything from dungeons to trials to raids to old dungeons and trials and raids. If HW was like ARR where every the first 3 jumped constantly than it would be a problem. But it wasn't like ARR. It turns out that playing a job for a longer period of time makes you better at making your own rotation so you don't have to worry about losing your wildfire 7 minutes in.

You want to talk about clunky?
Clunky is the fact that ignoring proc's when you're in your 10 second wildfire prep if one triggered beforehand is actually the better idea than trying to capitalize on it because QR won't be up if you do which means you'll lose clean shot. Rendering the beneficial nature of procs completely useless.
Clunky is overheat wildfires. Or rather, post-overheat management of CDs in order to not delay an ammo use, lose a GR or QR over the fight, and adhere to your 30/1 30/1 timings.

There is nothing more flexible about new wildfire:
Adds dying? Adds die pre 10 seconds anyway. Or rather pre 21 seconds, as that is what your wildfire window is in reality.
On the topic of that and fights; this is a pain in the rear in V3S specifically because every add that's not Apanda gets burned way to darn fast.
Invulnerability? Do some of the old HW content lately? Guess where Zurvan is going to be jumping if you adhere strictly to the current popular MCH wildfire rotation.
Flexibility in window? 20 seconds. Assuming you do everything correctly, V2S will fling you in the air during a WF window if you're forced to go to the far side. And now you've lost a wildfire use and have desync'd it from raid cooldowns :P.