Forums

*** Meter Hold-time Update ***

• WGTicon 12,511 Posts

  Thu, Feb 7 2013 1:03 PM

  Hi everyone,

  We have made a chance to how meter is working, so I wanted to explain what it does and why.

  We have seen a number of errors in the game when players hold the swing meter too long without swinging so in order to fix those issues we implemented a maximum hold-time for the swing meter.   Right now it is set to 15 seconds.  We will evaluate to make sure this fixes the errors we have seen and will adjust accordingly.  Plus, it will also help speed up game play a bit which is always a good thing.

  -WGTicon

• opyeuclid 6,710 Posts

  Thu, Feb 7 2013 1:15 PM

  Thank you for this info .

  OPY

• renniw52 5,385 Posts

  Thu, Feb 7 2013 1:17 PM

  Oh Lord, now what will happen?  I guess I need to clear my cache again today.

• Games4Ever71 623 Posts

  Thu, Feb 7 2013 1:20 PM

  I never hold my meter for more than 5 seconds. So this does not matter to me.

• alanti 10,564 Posts

  Thu, Feb 7 2013 1:32 PM

  Thanks Icon, once again great to see the communication.

  I personally hold my meter at the top of the swing just to let the CPU usage settle, but a maximum of 2-3 seconds - I am a little bewildered that some hold it for more than 15 seconds!

• Beryman 9,099 Posts

  Thu, Feb 7 2013 1:33 PM

  WGTicon:

  Right now it is set to 15 seconds.  We will evaluate to make sure this fixes the errors we have seen and will adjust accordingly.  Plus, it will also help speed up game play a bit which is always a good thing.

  -WGTicon

  15 seconds is also the amount of time it takes for the meter to quit moving..... as i usually wait for the meter to quit before i swing on putts (to reduce stuttering) it will be very difficult for me ... how about 18 seconds for hold ?

• Oldbayrunner 1,774 Posts

  Thu, Feb 7 2013 2:10 PM

  Well if you did more to stop activity from processing for more than 15 seconds by it processing  faster on your end  then people wouldn't have to hold their swings until it stops so they can get a decent swing meter.

  I use a cpu meter with mine and the major activity in my cpu coming from my browser files are all from the wgt game load portion of it. I have double checked it while it is showing activity by ending the process for that part in my task manager and sure enough as soon as I end it the game screen disconnects. So it is definitely Your end still processing.

  To me this is just another part of your screwing with the game. Your forever taking away what players have to do to be able to play this game more effectively without  taking care of your end of it. Fix it and we wont have to go through this crap. 

• WGTicon 12,511 Posts

  Thu, Feb 7 2013 2:13 PM

  Beryman:

  WGTicon:

  Right now it is set to 15 seconds.  We will evaluate to make sure this fixes the errors we have seen and will adjust accordingly.  Plus, it will also help speed up game play a bit which is always a good thing.

  -WGTicon

  15 seconds is also the amount of time it takes for the meter to quit moving..... as i usually wait for the meter to quit before i swing on putts (to reduce stuttering) it will be very difficult for me ... how about 18 seconds for hold ?

  hi

  right now it will be for 15 seconds as we are evaluating it. we are also collecting feedback to see. 

  I'll keep yours in mind as well.

  -wgticon

• devonnnnn 1,085 Posts

  Thu, Feb 7 2013 2:17 PM

  Thanks Icon yet again for the info :)

• Oldbayrunner 1,774 Posts

  Thu, Feb 7 2013 2:17 PM

  All you have to do to evaluate it is have your engineers play the game with their task manager processes open and they can very well see for themselves what the major activity is and how long it takes for it to process. This isn't just the intial game load but for each and every screen load. The worst is the putting screen, those little dots moving create a lot of cpu activity.

  At least now I know why earlier when I was holding my swing it was releasing.

   

  PS....I ran a stopwatch on it and your engineers can't program time very effective either. out of 10 timing checks I got between 12.7 to 13 seconds.