Forums

Maybe this is proof it is wgt

• TWOMINUSONE 2,580 Posts

  Sat, Jul 26 2014 6:14 PM

  Funny thing is, i see this on almost every shot or putt. But only when i seem to be on a hot 1? Go figure, eh?

• TWOMINUSONE 2,580 Posts

  Sat, Jul 26 2014 6:25 PM

  PaulTon:

  I see slow stuttering ball flight on a couple of camera angles, on an otherwise ordinary shot, what is this supposed to be proof of ?

  Hi Paul. We know you as a good skin on the forums my man, so i wont piss you about. There are those of us who believe that when the ball (shot or putt) is stutering on a replay or in game, then its the game re-configuring the path of the shot or putt. 

  Its easy to follow a smooth path of a ball when it glides effortlessly along a line, but when it stutters like that, then you cant help feeling something is working in the background to alter the flow. 

  Im not a conspiracy theorist in anything in life, but when it coms to WGT, i cant help but think something is amiss.

  Tin foil hat at the ready me thinks.

   

   

• YankeeJim 25,827 Posts

  Sat, Jul 26 2014 6:51 PM

  TWOMINUSONE:

  There are those of us who believe that when the ball (shot or putt) is stutering on a replay or in game, then its the game re-configuring the path of the shot or putt. 

  Really now. You seriously believe this? That surpasses any tin foil observations I've ever seen. For starters, you're talking about a rendering on a local machine that happens well after the shot result has been determined. As soon as you click,  the result is known to the computer but it takes time to turn that into something you can see on your computer-rendering the shot.

  If you look at the replay and just switch between the views without playing it, there's a marked difference in the times between 2/3 and 3/4. There's obviously something amiss with the files being loaded, or whatever, but it sure as hell isn't WGT changing the result of what happens AFTER you clicked.

  There's a delay in the switch from front view to landing view. Congratulations on turning that into a behind the scenes WGT manipulation of the game. Pathetic, IMO.

• jeffdos924 1,085 Posts

  Sat, Jul 26 2014 6:54 PM

  roaddawgstyle:

  WGT keeps saying clear your cache do this do that the problem is not on their end it is our computers.

  Ok so why does everyone who watches this replay see the pauses. Watching it even froze my computer had to close out the window.

  How about you quit blaming it on us wgt and fix the obvious problem on your end.

   OK.. I knew I was probably wasting my time to watch, but I did it anyway. I was really expecting to see something horrific... the ball making a straight left/right turn in to a hazard, maybe flying into an invisible brick wall and dropping straight back to earth, something like that.

  All I saw was replay of a decent drive. Sure, a couple of them showed a jerky ball trail.... big friggin' deal. Replay #2 was absolutely the worst for watching the ball flight ... in the air, but the ball landed smack dab where it landed in all 5 replays .... right in the middle of the fairway.

  Watch the mini map ... nice and smooth, and it looked like the ball was going right where it should have.

   But hey, let's just pile on WGT for such obvious "manipulation".  

   Speaking for myself only, WGT can feel free to manipulate my tee shots into the middle of the fairway every single time I play..... I don't care WHAT the ball flight looks like when they do it.

• TWOMINUSONE 2,580 Posts

  Sat, Jul 26 2014 7:23 PM

  YankeeJim:

   you're talking about a rendering on a local machine that happens well after the shot result has been determined. As soon as you click,  the result is known to the computer but it takes time to turn that into something you can see on your computer-rendering the shot.

  Hey Jim, we have known each other for a long time here, and i have never disagreed with your philosophy on the game, and have at most times agreed with what you have said. But when you say the shot has been determined before or after it has been taken (does it matter?) on a local machine, then do you really believe that the shot is going to be true to the actual input you put in every time?

  We all know about the circle of precision, but surely that circle of precision doesn't take time to figure out a shot after it has been taken? or does it? So what i am saying is that the game has a fast enough scope to deal with a shot once it has been hit, no?

  YankeeJim:

  If you look at the replay and just switch between the views without playing it, there's a marked difference in the times between 2/3 and 3/4. There's obviously something amiss with the files being loaded, or whatever, but it sure as hell isn't WGT changing the result of what happens AFTER you clicked.

  There in lies the problem Jim. If there is a problem with the files, then who is to say that these problems are not affecting most of the people who come on here complaining about the game? Maybe this is the crux of every thing wrong with WGT, and why so many folks see the game as flawed?

  YankeeJim:

  Congratulations on turning that into a behind the scenes WGT manipulation of the game. Pathetic, IMO.

  Thanks Jim, but im not the first. My only wish here is that some folks who dont realise the sh*t we go through to play a decent game of WGT now realise the crap we go through, as in the first posters opinion?

   

• andyson 6,415 Posts

  Sat, Jul 26 2014 8:15 PM

  YankeeJim:

  If you look at the replay and just switch between the views without playing it, there's a marked difference in the times between 2/3 and 3/4. There's obviously something amiss with the files being loaded,

  ^^^^^THIS!

  I monitored my PC's CPU and Memory usage while just switching between cameras 1 and 2.

  

  At the end I switched back to camera 1.  Loading the files for camera 2 is really messed up and drives my CPU to 50% usage and nearly doubles my memory use.

• YankeeJim 25,827 Posts

  Sat, Jul 26 2014 9:15 PM

  TWOMINUSONE:

  But when you say the shot has been determined before or after it has been taken (does it matter?) on a local machine, then do you really believe that the shot is going to be true to the actual input you put in every time?

  As soon as you click, the shot equation is complete and computed immensely faster than any computer can draw a simulation. That is what I mean by a shot being determined. Basically, the math is done and THEN it's up to the local machine to render it. Not before, not during, but AFTER.

  Thinking you're seeing a manipulation of the game in flight is totally preposterous, not to mention impossible. See Andyson's explanation of why this whole situation happened.

• alosso 21,070 Posts

  Sat, Jul 26 2014 11:29 PM

  YankeeJim:

  As soon as you click, the shot equation is complete and computed immensely faster than any computer can draw a simulation. That is what I mean by a shot being determined. Basically, the math is done and THEN it's up to the local machine to render it. Not before, not during, but AFTER.

  QFT!

  Apparently, view#2 of this special replay corrupts the browser operation (FF30 / Flash14)!

  (edited)

  Not only causes it CPU and memory usage to rise significantly and oszillate permanently (other than the other views), it also caused script errors with different sources and sometimes blocked the browser windows.

  But, this doesn't mean anything to the game. The replay only shows the result, it's not the shot itself. For a real test, OLY#14 must be played.

  Edit:

  My replay (from single hole play, red tees) shows none of these irregularties...

  Neither this one from the tips.

• fatdan 3,379 Posts

  Sun, Jul 27 2014 1:17 AM

  If you watch the hole map when you hit a shot you will see where the ball will stop long before it actually stops....

  Go to STA 1 and with an old ball and a tailwind and hit drive you know will go in the hazard...as soon as you hit it go to the menu and end the round while the ball is still in flight...you will find that the ball is lost even though you didn't actually let the ball go into the hazard as the result is determined as soon as you strike the ball....

• mantis0014 8,946 Posts

  Sun, Jul 27 2014 1:48 AM

  Cam2 doesn't play on my puter...  all the other cams do.

  Watching the replay from normal...  I think Cam1...  I think the ball was mm's away from hitting the tree...  hence the lag in the replay.

  I think the game gave ya the benefit of doubt....lol