Forums

Re: Losing Balls - Meter doesn't stop

• soakerdog 7 Posts

  Wed, Oct 14 2015 12:31 PM

  My Computer is Fine, My connection is fine, my timing is good, but it seems every other round or so the meter just keeps going after I click the mouse and I lose a ball. and it has been happening a lot. and it never seems to fail I buy a sleeve of balls and within a hole or two my meter does it to me again. It's bad enough when I hit one in the water on my own but I don't need the extra help. It is really starting to annoy me as well as costing me a lot of money. Anyone else with this issue?

  Soakerdog

• ApexPC 3,164 Posts

  Tue, Oct 20 2015 11:18 AM

  What browser do you use?

  Sounds like what happens when Chrome users leave Pepperflash enabled.

  WGT only supports 3 browsers

  http://www.wgt.com/forums/t/635.aspx

  Supported Web Browsers

  We currently support the following browsers:

  Internet Explorer version 9 and higher - Get the latest version here 
  Firefox version 3 and higher - Get the latest version here Preferred
  Chrome - Get the latest version here  make sure you have pepperflash turned off.

  Also make sure your Flash Player 

  Website Privacy Settings panel

  is empty.

• andyson 6,415 Posts

  Tue, Oct 20 2015 11:23 AM

  ApexPC:

  Sounds like what happens when Chrome users leave Pepperflash enabled.

  If you disable Pepperflash in the latest version of Chrome you cannot play this game, no other Flash is allowed.

  And I might add, Chrome with Pepperflash is what I use to play the game.  It works great.

• wldthng016400 250 Posts

  Tue, Oct 20 2015 5:21 PM

  Try playing one practice hole with the starter ball, then switch back to the paid for ball.

• nutts 12 Posts

  Tue, Oct 20 2015 11:07 PM

  Try the Maxthon browser

• PTrenter 437 Posts

  Wed, Oct 21 2015 4:59 AM

  nutts:

  Try the Maxthon browser

  This is what I use but even with that browser the game client eats up memory faster than a fat bird working through a meat pie.  

  Open up task manager and you'll see the memory usage.  The only workaround I have at the mo is to kill that process and restart Maxthon before each round.