After seeing the "Circle Path" sequence that Annikan posted in the advanced forum I'm curious as to the advantages and disadvantages with using it.
Experimented a bit with it at the range and it feels incredibly "consistent" for lack of a better term. Can you employ a snap release with it or is it just more difficult to prevent accumulator #2 from uncocking when the hands are moving on a circle delivery path? Are many pro's employing it?
After seeing the "Circle Path" sequence that Annikan posted in the advanced forum I'm curious as to the advantages and disadvantages with using it.
Experimented a bit with it at the range and it feels incredibly "consistent" for lack of a better term. Can you employ a snap release with it or is it just more difficult to prevent accumulator #2 from uncocking when the hands are moving on a circle delivery path? Are many pro's employing it?
CG
I believe that's what I do for both "hitting and swinging". It might not be the most powerful, but the "easiest" (how about this term) to control. It's probably not for snap release, but, again, easier to "sustain the lag" (or "to prevent accumulator #2 from uncocking" longer).
__________________ Yani Tseng, Go! Go! Go! Yani Tseng Did It Again! YOU load and sustain the "LAG", during which the "LAW" releases it, ideally beyond impact.
"Sustain (Yang/陽) the lag (Yin/陰)" is "the unification of Ying and Yang" (陰陽合一).
The "LAW" creates the "effect", which is the "motion" or "feel", with the "cause", which is the "intent" or "command".
"Lag" is the secret of golf, passion is the secret of life.
Think as a golfer, execute like a robot.
Rotate, twist, spin, turn. Bend the shaft.
I think that some of the Hardy One Plane guys probably use CIRCLE. This complies with the No Axis Tilt(or very little) that goes along with this technique.
PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
ERROR: The request could not be satisfied
504 Gateway Timeout ERROR
The request could not be satisfied.
We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
Generated by cloudfront (CloudFront) HTTP3 Server
Request ID: CYJ0yH9s5o_i4DhSHLfytivLbkaqW8M2qwPp81hdG_kzbywkxZSQtg==