Forums

Maybe this is proof it is wgt

• andyson 6,415 Posts

  Sun, Jul 27 2014 8:43 AM

  alosso:

  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.

  Since during a game the server gets the shot input data from the game client, then runs the physics model for the input data producing the shot data and sends that data to the game client on our PC, I see no reason why a replay doesn't have the same info a game shot has.  The game client merely renders the shot, fetching the needed files and photos whether its a game shot or replay.  Doesn't matter IMNSHO.

  Your test replays both hit a tree so the questionable file(s) never were fetched.  In other words, the camera #2 photo in the original replay was never used in your 2 replays alosso.

   

• PaulTon 10,731 Posts

  Sun, Jul 27 2014 9:18 AM

  No wonder CSI Olympic never made it to our screens.

  Forensic examination of a decent shot - riveting.

• andyson 6,415 Posts

  Sun, Jul 27 2014 9:33 AM

  PaulTon:

  No wonder CSI Olympic never made it to our screens.

  Forensic examination of a decent shot - riveting.

  Deserves a Gibb's head slap...

  

   

• alosso 21,070 Posts

  Sun, Jul 27 2014 9:58 AM

  andyson:

  Your test replays both hit a tree so the questionable file(s) never were fetched.  In other words, the camera #2 photo in the original replay was never used in your 2 replays alosso.

  My bad - naively I thought it must be the same views...

  So, it's either the precise view or the shot itself. Since the shot needs not to be executed for the irregular behaviour, it should be the picture or it's surroundings.

  Coincidentally, cam 2 of the original replay produced a few script errors (without shooting).

  It was

  - b.scorecardresearch.com/...
  - js.moatads.com/...
  - and a wgt.com address which I clicked away too quickly.

• dedBuNNy 1,919 Posts

  Tue, Jul 29 2014 4:47 AM

  Bitching about shot animations with this game is futile and really there isn't anything WGT can do about it, it's the game itself. 

  Flash does not handle any type of even remotely high-res or even standard-res image rendering/serving. Never has, it was never  designed  to do so. It's a vector animation tool. I've been working with it since in was a plugin for Director way way back. 

  Track any website which is using Flash as it's primary build and you'll usually find either one of two things. Large/poorly optimized images being served up or bad audio. This 'game' has both. This isn't an executable game, it's a Flash based game in a browser. The fact that it plays at all is actually quite a feat, that it plays as poorly as it does is no surprise at all. Wrong platform for the job. Not even taking into consideration what vem is doing to it. 

  The only thing that would 'fix' it is if they spent massive amounts of money and built a totally 'private Internet' dedicated to it, even then it would still have issues.

  You want to see what's going on with the game, run Scout against it. TM just shows your machine. 

   

• Romax 1,876 Posts

  Wed, Jul 30 2014 10:33 AM

  I have always believed the outcome of the shot was decided the second you click, otherwise how could they incorporate a " heartbeat" in the Blitz mode ? Also, the last drained putt is always delayed a few seconds which tells me the shot is decided on impact. I have often wondered though why the "heartbeat" sometimes doesn't start until the ball is almost there.

  There's likely a reason, but I don't know what it is.

• dedBuNNy 1,919 Posts

  Thu, Jul 31 2014 3:39 AM

  Romax:

  I have always believed the outcome of the shot was decided the second you click...

   

  It  absolutely is, as soon as you release the last state on the meter. Everything else is just visuals.

  That's why the SpeedBoost things work, just running the animations/visuals faster.

   

• roaddawgstyle 305 Posts

  Fri, Feb 13 2015 5:46 PM

  Just thought this one needed to be bumped up, because nobody from wgt came anywhere near this post.

  To all the people on here saying I am chirping about the result of the shot I am not one thing in my post suggests wgt altered the results I am just pointing out that WGT always wants to blame disconnects and choppy camera views and meter issues on us saying the problem is on our end, but anyone who watches this video sees the jerky camera view suggest the problem is on wgt's end.