YPE HTML PUBLIC "-/ The Sweet Spot Location Ain't The Problemc - LynnBlakeGolf Forums

The Sweet Spot Location Ain't The Problemc

24 Basic Components

 
 
Thread Tools Display Modes
Prev Previous Post   Next Post Next
  #1  
Old 01-01-1970, 12:00 AM
Yoda's Avatar
Yoda Yoda is offline
Administrator
 
Join Date: Jan 2005
Location: Atlanta, Georgia
Posts: 10,681
The Sweet Spot Location Ain't The Problemc

brianmanzella wrote:

You see...no one wants to answer this question:

What about the fact that in a set of PING EYE 2's, still available from PING, the SWEETSPOT is in the SAME PLACE from club to club?

Here is AN answer:

The face would be LESS hook-faced than what homer said in relation to the hookface of the, lets say, three iron, so while the most FORWARD ball position of what YODA is saying would have to move backa bit, the most rearward one would HAEV TO move up more than a bit.



Wonderful! I am happy that Ping has put the Sweet Spot in the same place forall Clubs.

Two questions:

1. How does the 'same Sweet Spot location' in any way change the Clubs' varyinglengths? This is the root of the problem (6-E-2)!

2. Assuming the player favors the 'one Ball location' method -- i.e., hechooses to alter the required geometric Ball Location and make the appropriateAiming Point adjustment -- how does the 'same sweetspot location' in any wayeliminate the required Aiming Point adjustment?

__________________
Yoda
 


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is On
Forum Jump


All times are GMT -4. The time now is 09:21 AM.


Design by Vjacheslav Trushkin, color scheme by ColorizeIt!.
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==