Charge Delay (500 ms?)exist or not?
It's so clearly it is exist.
Any evidence supports it is not?
Can I use another move Before the charge move's animation ends,which compensate the delay? any video analysis exists?
The word "Charge Delay" comes from here:
Professor_Kukui said: “Currently using 500ms charge-up time (the time it takes you to long press before firing a special attack) and 50% crit damage bonus. I assume the charge-up time because I have never been able to successfully sneak the charge-up time while a gym is doing a Pokemon switch or while I'm winding down from another animation. It always fills the bar but does nothing, and then I always have to do it again unless I started the long press in a time when I would otherwise have been able to quick attack. This might be because a hit flinches the Pokemon (which doesn't seem entirely depending on you animation-cancelling correctly on client-side, as the server might still register an attack at you that you can't see until the next sync) as much as it might be because you cancelled the animation.”(https://docs.google.com/spreadsheets/u/1/d/1hcFo7-UGWx1k1u1BHOvDhq8foPeRr7YbX2jLjjJK0Qw/htmlview?usp=sharing&sle=true#)
It's so clearly it is exist.
Any evidence supports it is not?
Can I use another move Before the charge move's animation ends,which compensate the delay? any video analysis exists?
The word "Charge Delay" comes from here:
Professor_Kukui said: “Currently using 500ms charge-up time (the time it takes you to long press before firing a special attack) and 50% crit damage bonus. I assume the charge-up time because I have never been able to successfully sneak the charge-up time while a gym is doing a Pokemon switch or while I'm winding down from another animation. It always fills the bar but does nothing, and then I always have to do it again unless I started the long press in a time when I would otherwise have been able to quick attack. This might be because a hit flinches the Pokemon (which doesn't seem entirely depending on you animation-cancelling correctly on client-side, as the server might still register an attack at you that you can't see until the next sync) as much as it might be because you cancelled the animation.”(https://docs.google.com/spreadsheets/u/1/d/1hcFo7-UGWx1k1u1BHOvDhq8foPeRr7YbX2jLjjJK0Qw/htmlview?usp=sharing&sle=true#)