|
Post by HeMan1202 on Oct 23, 2018 10:04:37 GMT -5
Based oh what I am seeing, the API in this year's game is really too punishing. The short feedback lines (not reaching the top) can happen if we make a simple error while moving the stick. I feel like that damn API expects perfection on every shot. We are all human here and do have miscues while moving the stick. Hell I get all nervous while playing and start sweating lol, my finger slips on the stick and BAM a short white line happens yet it does not seem to affect the resulting shot sometimes, it'll end up perfect/perfect. I have no clue how many of those we are allowed per round before this API goes nuclear and reports you for being whatever, a possible cheat, a non perfect stick manipulator, I dunno......Bottom line is that HB has made the API too strict in my opinion. With that said, my first round yesterday maybe had two short lines that did not reach the top. Is that enough to get me flagged?? All I know is that this has made the game very stressful while playing. Always thinking about making that white line fill up the meter, it really takes away from where the concentration should be, on making good shot adjustments for the best possible shot. Oh well, plan on playing my remaining three rounds today because I really want to see how the API reacts. Wish me well!! *loads up on sweat rags* My swing results in a shortened line 90-95% of the time and I haven't been flagged (yet) so I don't think you can point to this specifically and say if you have a shortened line you will be flagged. I think there are other factors.
|
|
|
Post by hoos4974 on Oct 23, 2018 10:44:04 GMT -5
Based oh what I am seeing, the API in this year's game is really too punishing. The short feedback lines (not reaching the top) can happen if we make a simple error while moving the stick. I feel like that damn API expects perfection on every shot. We are all human here and do have miscues while moving the stick. Hell I get all nervous while playing and start sweating lol, my finger slips on the stick and BAM a short white line happens yet it does not seem to affect the resulting shot sometimes, it'll end up perfect/perfect. I have no clue how many of those we are allowed per round before this API goes nuclear and reports you for being whatever, a possible cheat, a non perfect stick manipulator, I dunno......Bottom line is that HB has made the API too strict in my opinion. With that said, my first round yesterday maybe had two short lines that did not reach the top. Is that enough to get me flagged?? All I know is that this has made the game very stressful while playing. Always thinking about making that white line fill up the meter, it really takes away from where the concentration should be, on making good shot adjustments for the best possible shot. Oh well, plan on playing my remaining three rounds today because I really want to see how the API reacts. Wish me well!! *loads up on sweat rags* My swing results in a shortened line 90-95% of the time and I haven't been flagged (yet) so I don't think you can point to this specifically and say if you have a shortened line you will be flagged. I think there are other factors. Well there is plenty of variation to my shot feedback lines, that I know for a fact as my shots were landing all over the place and rarely where intended lol Also I heard that the API won't report back until all four rounds are played....have you played all four?
|
|
Epiphanic
Weekend Golfer
Posts: 77
TGCT Name: Nicholas Aakre
Tour: CC-Am/TST
|
Post by Epiphanic on Oct 23, 2018 10:57:02 GMT -5
Furthermore, it would make sense that the API is not only checking how straight your swing is, but how consistent your swings are. It's certainly possible for a human player to get a perfectly (or nearly perfect) straight swing once or twice during a round. But if every swing is perfectly straight, that sends up a red flag. In addition, even if your swings aren't exactly perfect, but they look identical to each other, that's also a possible red flag.
The more I think about it, I believe the "truncated line" isn't a problem by itself. The real potential issue is inhuman consistency on the input (whether it is ridiculously straight or not). If every swing constantly looks like the swing before it (11 decimal places!), that's strong evidence that something is wrong.
The API can't know the reason why the data is what it is. It can only flag rounds that are inhumanly consistent. Whether that's the result of someone cheating with a script or simply because the controller is worn/faulty, is beyond the capabilities of the API.
Bottom line: if a round gets flagged, it doesn't mean you're cheating. All it means is there's something improbable with the swing data.
|
|
|
Post by Cyclerob on Oct 23, 2018 11:04:56 GMT -5
Here are your two rounds that were flagged in the exhibition event: FWIW, I have a hard time seeing this as a "light grip" issue. If the center point of your dispersion was around the middle instead of 5 columns to the right, or you had similar dispersions centered around a different midpoint - since multiple controllers, even if they were all flawed with some manufactured bias, wouldn't produce identical points 5 columns to the right of center in the graph - then maybe. Light touch allows the joystick to mechanically stay in it's center point by only applying the minimum required pressure to move it forward and backward, but I can't really see how such a method would consistently get you 5 cells right of center (on the graph) most often, with multiple controllers.
All of that said...what do I know, the graph/data just doesn't look how I would have expected it to if the issue was all only about this "light touch" swing method.
That graphic is also a by-product of most of my swings don't show completed in the HUD. Basically it doesn't send all the swing data to HB, an HB decision with this version of the game. So TGCTours is getting what looks like part of the swing data in my mind. The API does its job in analyzing what's fed to it. Then all the red lights light up and you're flagged as if you're using a script. Both my less than 2 months old DS4's got flagged, what are the chances of that? I tried my older ones yesterday and I end up with similar swing lines. I posted a video of my first 2 rounds of that event. My scores stayed on the board, so silly me thinking that I was within the parameters and have nothing to worry about I didn't record the last 2, which ended being flagged. I learned after via Jeff that my first 2 barely past the API test. So in essence some people now think that lying when I say that I use stock DS4's, Some other after looking at my videos see a guy with a consistent swing, not much different then theirs. Certainly nothing that they haven't seen before from a better than average player. Anyways... Shopping for cameras on Amazon right now so that I can post vids of me, showing controller being used, my hands and the TV. Hopefully this will clear the fact that I'm no robot!
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Oct 23, 2018 11:07:34 GMT -5
Furthermore, it would make sense that the API is not only checking how straight your swing is, but how consistent your swings are. It's certainly possible for a human player to get a perfectly (or nearly perfect) straight swing once or twice during a round. But if every swing is perfectly straight, that sends up a red flag. In addition, even if your swings aren't exactly perfect, but they look identical to each other, that's also a possible red flag. The more I think about it, I believe the "truncated line" isn't a problem by itself. The real potential issue is inhuman consistency on the input (whether it is ridiculously straight or not). If every swing constantly looks like the swing before it (11 decimal places!), that's strong evidence that something is wrong. The API can't know the reason why the data is what it is. It can only flag rounds that are inhumanly consistent. Whether that's the result of someone cheating with a script or simply because the controller is worn/faulty, is beyond the capabilities of the API. Bottom line: if a round gets flagged, it doesn't mean you're cheating. All it means is there's something improbable with the swing data. Great summary, yes that's exactly what the API is all about. I wonder if the term 'fair play' might be worth amending to 'level playing field', since the former can't escape the association with cheating, so when honest players are flagged when they weren't deliberately doing anything, it can understandably make them extremely upset. To say that the policy is based on assuring a level playing field, i.e. within certain acceptable margins of swing consistency, seems closer to me to be what it's all about.
|
|
|
Post by HeMan1202 on Oct 23, 2018 11:41:21 GMT -5
My swing results in a shortened line 90-95% of the time and I haven't been flagged (yet) so I don't think you can point to this specifically and say if you have a shortened line you will be flagged. I think there are other factors. Well there is plenty of variation to my shot feedback lines, that I know for a fact as my shots were landing all over the place and rarely where intended lol Also I heard that the API won't report back until all four rounds are played....have you played all four? I think you're going to be fine as long as there is variation.
I thought they changed the API gathering to after 2 rounds?
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Oct 23, 2018 11:43:32 GMT -5
Well there is plenty of variation to my shot feedback lines, that I know for a fact as my shots were landing all over the place and rarely where intended lol Also I heard that the API won't report back until all four rounds are played....have you played all four? I think you're going to be fine as long as there is variation.
I thought they changed the API gathering to after 2 rounds?
Last week it was after rounds two and four. This week? idk
|
|
|
Post by hoos4974 on Oct 23, 2018 11:44:15 GMT -5
Well there is plenty of variation to my shot feedback lines, that I know for a fact as my shots were landing all over the place and rarely where intended lol Also I heard that the API won't report back until all four rounds are played....have you played all four? I think you're going to be fine as long as there is variation.
I thought they changed the API gathering to after 2 rounds?
I was told four rounds for Q school, 2 rounds afterwards in the Pro classes and 4 rounds in the CC.... Not sure if that is true or not
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Oct 23, 2018 11:58:12 GMT -5
FWIW, I have a hard time seeing this as a "light grip" issue. If the center point of your dispersion was around the middle instead of 5 columns to the right, or you had similar dispersions centered around a different midpoint - since multiple controllers, even if they were all flawed with some manufactured bias, wouldn't produce identical points 5 columns to the right of center in the graph - then maybe. Light touch allows the joystick to mechanically stay in it's center point by only applying the minimum required pressure to move it forward and backward, but I can't really see how such a method would consistently get you 5 cells right of center (on the graph) most often, with multiple controllers.
All of that said...what do I know, the graph/data just doesn't look how I would have expected it to if the issue was all only about this "light touch" swing method.
That graphic is also a by-product of most of my swings don't show completed in the HUD. Basically it doesn't send all the swing data to HB, an HB decision with this version of the game. So TGCTours is getting what looks like part of the swing data in my mind. The API does its job in analyzing what's fed to it. Then all the red lights light up and you're flagged as if you're using a script. Both my less than 2 months old DS4's got flagged, what are the chances of that? I tried my older ones yesterday and I end up with similar swing lines. I posted a video of my first 2 rounds of that event. My scores stayed on the board, so silly me thinking that I was within the parameters and have nothing to worry about I didn't record the last 2, which ended being flagged. I learned after via Jeff that my first 2 barely past the API test. So in essence some people now think that lying when I say that I use stock DS4's, Some other after looking at my videos see a guy with a consistent swing, not much different then theirs. Certainly nothing that they haven't seen before from a better than average player. Anyways... Shopping for cameras on Amazon right now so that I can post vids of me, showing controller being used, my hands and the TV. Hopefully this will clear the fact that I'm no robot! Most phones have an adequate video recorder - shouldn’t need to go out and buy one. I was called out early on in TGC2 and was in the process of getting footage of myself playing to prove I was legit. In the process we found out that seemingly legit controllers, sold as genuine and with legit XBox marking were actually a 3rd party controller made by PowerA, which had a sight ‘dead zone’ that made perfect shots possible. (Not easy, but possible). Hopefully they get it sorted for you - the fact that you’re willing to be watched playing carries a fair bit of water for me, so I’ll give you the benefit of the doubt till it gets sorted. Cheers.
|
|
|
Post by HeMan1202 on Oct 23, 2018 11:59:54 GMT -5
I think you're going to be fine as long as there is variation.
I thought they changed the API gathering to after 2 rounds?
I was told four rounds for Q school, 2 rounds afterwards in the Pro classes and 4 rounds in the CC.... Not sure if that is true or not Thanks, well I guess I have one more round to play and we will see. Honestly though, I am confident my line has enough variation (more than enough for my liking) to pass API. I really think the issue with flicking forward is the dead zone that allows for consistently straight shots with a shorter line. So I don't really think it is so much the line being short of complete, but how much being short has an effect on shot variation and straightness.
|
|
|
Post by SmilingGoats on Oct 23, 2018 12:15:35 GMT -5
API checks are every 2 rounds for Q-School
|
|
|
Post by hoos4974 on Oct 23, 2018 12:20:13 GMT -5
API checks are every 2 rounds for Q-School Thanks for clearing that up!
|
|
|
Post by Cyclerob on Oct 23, 2018 12:46:20 GMT -5
That graphic is also a by-product of most of my swings don't show completed in the HUD. Basically it doesn't send all the swing data to HB, an HB decision with this version of the game. So TGCTours is getting what looks like part of the swing data in my mind. The API does its job in analyzing what's fed to it. Then all the red lights light up and you're flagged as if you're using a script. Both my less than 2 months old DS4's got flagged, what are the chances of that? I tried my older ones yesterday and I end up with similar swing lines. I posted a video of my first 2 rounds of that event. My scores stayed on the board, so silly me thinking that I was within the parameters and have nothing to worry about I didn't record the last 2, which ended being flagged. I learned after via Jeff that my first 2 barely past the API test. So in essence some people now think that lying when I say that I use stock DS4's, Some other after looking at my videos see a guy with a consistent swing, not much different then theirs. Certainly nothing that they haven't seen before from a better than average player. Anyways... Shopping for cameras on Amazon right now so that I can post vids of me, showing controller being used, my hands and the TV. Hopefully this will clear the fact that I'm no robot! Most phones have an adequate video recorder - shouldn’t need to go out and buy one. I was called out early on in TGC2 and was in the process of getting footage of myself playing to prove I was legit. In the process we found out that seemingly legit controllers, sold as genuine and with legit XBox marking were actually a 3rd party controller made by PowerA, which had a sight ‘dead zone’ that made perfect shots possible. (Not easy, but possible). Hopefully they get it sorted for you - the fact that you’re willing to be watched playing carries a fair bit of water for me, so I’ll give you the benefit of the doubt till it gets sorted. Cheers. I did think about using my phone... But I didn't see myself taping my Samsung S9+ to my forehead to give people my POV while playing. Looking at this one as an option: www.amazon.ca/AKASO-Brave-Underwater-Waterproof-Accessories/dp/B078N26K5Z/ref=pd_aw_sbs_23_2?_encoding=UTF8&psc=1&refRID=E5NZZFC883Z7PSB6NBDRSomething like that with a head harness should do the trick. I don't want to spend GoPro type cash just for this application. The Akaso seems like it's possible to make pretty accurate videos with it and the price is reasonable. Anybody here knows about these?
|
|
|
Post by Coniglio on Oct 23, 2018 12:55:57 GMT -5
I dont mind recording myself with either controller, but is this something admins really want? I mean it wouldnt change the fact to the api its a flagged result
|
|
|
Post by rob4590 on Oct 23, 2018 13:29:59 GMT -5
Surely by the time you've all bought a camera, it would just be simpler (and cheaper) to buy a new legit controller (that you are gonna need to buy to get legal for TGCT anyway)?
|
|