|
Post by fadgewacker on Apr 16, 2020 10:33:09 GMT -5
Has anyone played any rounds yet? Nah. Golf is for girls...
|
|
|
Post by donkeypuncherben on Apr 16, 2020 12:51:33 GMT -5
Have you tried to deliberately mix in left side cone and right side cone ball strikes, and then, play the push or pull accordingly? Like in real golf, close your stance to enable draws, or open your stance to enable fades. When I angle the controller to the to the inside (left) my thumb pressure shifts ever so slightly and induces left side cone (within cone), and draws. Likewise, if I shift the angle of the controller to the right, the opposite is true in that I will always hit right side cone (within cone), for fades. The technique "usually" works great for avoiding nasty obstacles/OB, the only caveat being, if I accidentally hit it straight then I'm still safe (if approaching a pin), just a little bit too far away.
I do this on some shots because if I am trying to swing a fraction right it is much less likely I will miss left or vice versa. I can do it and usually end up on my desired side of center without much trouble keeping it in the cone However, there was a contingent in the threads about the push swing certain that anything other than trying to swing as straight as possible every swing is not playing the game as it was intended.
|
|
|
Post by rob4590 on Apr 16, 2020 13:27:34 GMT -5
As if by magic.........poof! Now you see him - now you don't.....
|
|
Theopen
Weekend Golfer
Posts: 143
TGCT Name: Brian Ayers
Tour: Beer League
|
Post by Theopen on Apr 16, 2020 13:38:21 GMT -5
I've never really understood the fear/worry of hitting "too straight" ... I often have rounds where 90% of my shots look like this: That looks pretty straight, but it's not ... just a slight veer to the left at both ends of the swing. If it were too straight, I would have been pulled a long time ago. Granted, I use a mouse (FWIW), and the input data is certainly different compared to a controller ... but I honestly don't see how you can hit it straighter than that with a controller and get pulled by the API. It's my understanding that the API checks for inhuman levels of straightness (as in, disabling the X-axis entirely). So, I just have to cock my brow a bit when I see all the excuses for how/why it's the controller's fault.
|
|
|
Post by cseanny on Apr 16, 2020 13:54:31 GMT -5
donkeypuncherben I've read all that, however, the caveat is, it's only foul play if you're out of the cone on every shot (and to one side). My technique is a skill based shot, within the cone. The two don't compare.
edit: And I finished Q-School, struggling a bit with my putting, and finished at -57. 20th place is -47 so I'd need -61 under to Qualify for PGA, hence, if my API is good, I'll be joining Euro. I did hit MANY shots outside of the cone (not on purpose either!), so Euro is just fine. A bit ironic that when I plan for a slight draw/fade, I do it within the blue, but when I'm trying to hit it straight, I'm having a bit more deviation o_^.
|
|
|
Post by alexandre on Apr 16, 2020 14:01:48 GMT -5
I believe doesn't shoot 30% of the shots like that. Even the weather is perfect. If so, I think the API would take it out of the tournament. Look at the second round of this tournament. Virtually no wind. And with a lot of straight lies. Whoever shoots the way above, with all the natural calculations (and simple, as we are almost windless) would always put the ball next to the hole. It would be at least -18. I do not doubt that he is capable, I only doubt that this will happen. I've never really understood the fear/worry of hitting "too straight" ... I often have rounds where 90% of my shots look like this: That looks pretty straight, but it's not ... just a slight veer to the left at both ends of the swing. If it were too straight, I would have been pulled a long time ago. Granted, I use a mouse (FWIW), and the input data is certainly different compared to a controller ... but I honestly don't see how you can hit it straighter than that with a controller and get pulled by the API. It's my understanding that the API checks for inhuman levels of straightness (as in, disabling the X-axis entirely). So, I just have to cock my brow a bit when I see all the excuses for how/why it's the controller's fault.
|
|
|
Post by fadgewacker on Apr 16, 2020 14:25:53 GMT -5
Have you tried to deliberately mix in left side cone and right side cone ball strikes, and then, play the push or pull accordingly? Like in real golf, close your stance to enable draws, or open your stance to enable fades. When I angle the controller to the to the inside (left) my thumb pressure shifts ever so slightly and induces left side cone (within cone), and draws. Likewise, if I shift the angle of the controller to the right, the opposite is true in that I will always hit right side cone (within cone), for fades. The technique "usually" works great for avoiding nasty obstacles/OB, the only caveat being, if I accidentally hit it straight then I'm still safe (if approaching a pin), just a little bit too far away.
I do this on some shots because if I am trying to swing a fraction right it is much less likely I will miss left or vice versa. I can do it and usually end up on my desired side of center without much trouble keeping it in the cone However, there was a contingent in the threads about the push swing certain that anything other than trying to swing as straight as possible every swing is not playing the game as it was intended.
Pretty sure that the only thing that there was ever anything that could have approached an exception being taken to was that you said you always played for a specific miss when fully lofting Ben, but it’s a good story... Playing the odd push or pull isn’t something I generally do on purpose, if in need to miss something I cut or draw away from the trouble... horses for courses. If people intentionally play one way misses for the majority of their shots, they will have a high probability of getting DQ’d... everyone knows why.
|
|
|
Post by crushtastic on Apr 16, 2020 14:59:33 GMT -5
The -17s are at 63...I don't think we will make it. 😥
|
|
|
Post by Doyley on Apr 16, 2020 15:04:31 GMT -5
The -17s are at 63...I don't think we will make it. 😥 My ears perked up but then I realize you didn't say the -8's.
|
|
|
Post by fadgewacker on Apr 16, 2020 15:16:52 GMT -5
I've never really understood the fear/worry of hitting "too straight" ... I often have rounds where 90% of my shots look like this: That looks pretty straight, but it's not ... just a slight veer to the left at both ends of the swing. If it were too straight, I would have been pulled a long time ago. Granted, I use a mouse (FWIW), and the input data is certainly different compared to a controller ... but I honestly don't see how you can hit it straighter than that with a controller and get pulled by the API. It's my understanding that the API checks for inhuman levels of straightness (as in, disabling the X-axis entirely). So, I just have to cock my brow a bit when I see all the excuses for how/why it's the controller's fault. I agree, and rarely do you find that a legit full swing, no matter how seemingly straight, gets pulled... flicks are another thing. The more I think about these issues, I think it’s primarily putting... maybe the data points get condensed or something, but the more unexplainable pulls, urge and Tyler, are both on putting (Tyler primarily and urge completely IIRC)...
|
|
|
Post by donkeypuncherben on Apr 16, 2020 16:25:29 GMT -5
I do this on some shots because if I am trying to swing a fraction right it is much less likely I will miss left or vice versa. I can do it and usually end up on my desired side of center without much trouble keeping it in the cone However, there was a contingent in the threads about the push swing certain that anything other than trying to swing as straight as possible every swing is not playing the game as it was intended.
Pretty sure that the only thing that there was ever anything that could have approached an exception being taken to was that you said you always played for a specific miss when fully lofting Ben, but it’s a good story... Playing the odd push or pull isn’t something I generally do on purpose, if in need to miss something I cut or draw away from the trouble... horses for courses. If people intentionally play one way misses for the majority of their shots, they will have a high probability of getting DQ’d... everyone knows why. Yes that is what I do fully lofting, sometimes partially lofting, sometimes without lofting. I'm not outside where the cone would be but I am definitely trying to have a bias away from one side so I know the ball won't go to that side of my aim point. It makes no sense that this would be an OK shot to play without loft but not with loft.
|
|
UrgeToFly
Caddy
Posts: 61
TGCT Name: Charlie Kelly
Tour: PGA
|
Post by UrgeToFly on Apr 16, 2020 17:08:10 GMT -5
I've never really understood the fear/worry of hitting "too straight" ... I often have rounds where 90% of my shots look like this: That looks pretty straight, but it's not ... just a slight veer to the left at both ends of the swing. If it were too straight, I would have been pulled a long time ago. Granted, I use a mouse (FWIW), and the input data is certainly different compared to a controller ... but I honestly don't see how you can hit it straighter than that with a controller and get pulled by the API. It's my understanding that the API checks for inhuman levels of straightness (as in, disabling the X-axis entirely). So, I just have to cock my brow a bit when I see all the excuses for how/why it's the controller's fault. I agree, and rarely do you find that a legit full swing, no matter how seemingly straight, gets pulled... flicks are another thing. The more I think about these issues, I think it’s primarily putting... maybe the data points get condensed or something, but the more unexplainable pulls, urge and Tyler, are both on putting (Tyler primarily and urge completely IIRC)... Yep, that is correct. My rounds were just fine from tee to green then putting got me pulled. I use a normal grip (right thumb on the right stick).
|
|
|
Post by jtcurrent on Apr 16, 2020 19:05:15 GMT -5
I've never really understood the fear/worry of hitting "too straight" ... I often have rounds where 90% of my shots look like this: That looks pretty straight, but it's not ... just a slight veer to the left at both ends of the swing. If it were too straight, I would have been pulled a long time ago. Granted, I use a mouse (FWIW), and the input data is certainly different compared to a controller ... but I honestly don't see how you can hit it straighter than that with a controller and get pulled by the API. It's my understanding that the API checks for inhuman levels of straightness (as in, disabling the X-axis entirely). So, I just have to cock my brow a bit when I see all the excuses for how/why it's the controller's fault. Oh my god your swing is so much better than mine it’s ridiculous. Congrats for being able to do that...I only dream of those lines.
|
|
Theopen
Weekend Golfer
Posts: 143
TGCT Name: Brian Ayers
Tour: Beer League
|
Post by Theopen on Apr 16, 2020 19:07:34 GMT -5
Well, then I guess my best theory would be the difference in the input data. I know I've seen the HB devs talking about it in regards to how they handle that data between each device. A mouse has a much higher polling rate and sends back a lot (LOT) more X/Y data to the game. They use smoothing (averaging) to get a swing line based on a subset of points in that data (in relation to the speed/timing of your swing). Those data points are what the API uses (presumably). So, you get a +/- of your offset to "0" on the x-axis in either direction. Even though my swing line looks relatively straight, it could have a lot of +0.05, for instance ... and only results in maybe 30-40% of points that crossed right on "0". On the other hand, a controller sends back much fewer data points, so if you did have a fairly straight swing, your likelihood of getting a higher percentage of "0" values is increased. Do you happen to frequently have short lines while putting? A shorter swing means that less data points were sent to the game. I know I often have really tiny lines on really close putts (~5ft). But, since a mouse sends back a lot more data anyway, the odds of too many zeroes is less likely. On a controller, I guess you'd need a fuller swing even on shorter putts to make sure more data points are sent back. I have no idea how many data points the TGCTours API receives, though. So, it guess it depends on whether or not the API limits could be relaxed enough to help genuine swings that just happen to be pretty straight, while still catching any cheats/exploits/hacks/deliberatelyBrokenControllers/etc. Only the admins would know. Personally, I'm a lot more worried about catching the cheaters on their long/approach shots. Because, when I'm shooting as straight as that picture, I can nail the approach to within 5-10 ft. every time (our frequent VF/VF green conditions notwithstanding). So, at that distance, even a crooked putt will usually still go in. So, if someone were to swing honestly/fairly on their woods/irons/wedges, and then, for some reason, switch to a cheat for their short putts?! ... I don't care. I'm much more interested in stopping 'em before they get near the hole
|
|
UrgeToFly
Caddy
Posts: 61
TGCT Name: Charlie Kelly
Tour: PGA
|
Post by UrgeToFly on Apr 16, 2020 23:26:21 GMT -5
Well, then I guess my best theory would be the difference in the input data. I know I've seen the HB devs talking about it in regards to how they handle that data between each device. A mouse has a much higher polling rate and sends back a lot (LOT) more X/Y data to the game. They use smoothing (averaging) to get a swing line based on a subset of points in that data (in relation to the speed/timing of your swing). Those data points are what the API uses (presumably). So, you get a +/- of your offset to "0" on the x-axis in either direction. Even though my swing line looks relatively straight, it could have a lot of +0.05, for instance ... and only results in maybe 30-40% of points that crossed right on "0". On the other hand, a controller sends back much fewer data points, so if you did have a fairly straight swing, your likelihood of getting a higher percentage of "0" values is increased. Do you happen to frequently have short lines while putting? A shorter swing means that less data points were sent to the game. I know I often have really tiny lines on really close putts (~5ft). But, since a mouse sends back a lot more data anyway, the odds of too many zeroes is less likely. On a controller, I guess you'd need a fuller swing even on shorter putts to make sure more data points are sent back. I have no idea how many data points the TGCTours API receives, though. So, it guess it depends on whether or not the API limits could be relaxed enough to help genuine swings that just happen to be pretty straight, while still catching any cheats/exploits/hacks/deliberatelyBrokenControllers/etc. Only the admins would know. Personally, I'm a lot more worried about catching the cheaters on their long/approach shots. Because, when I'm shooting as straight as that picture, I can nail the approach to within 5-10 ft. every time (our frequent VF/VF green conditions notwithstanding). So, at that distance, even a crooked putt will usually still go in. So, if someone were to swing honestly/fairly on their woods/irons/wedges, and then, for some reason, switch to a cheat for their short putts?! ... I don't care. I'm much more interested in stopping 'em before they get near the hole If you are asking me, I actually take the same length swing on putts as I do on full shots. I pull all the way down and up to the plastic, even on tap-ins.
|
|