Richard4168: The clubs name changes, and the ball name changes when we use the spin option. If a person tries to swing while these animations are in motion, their going to get a meter stutter every-time. Flash needs to to settle-down, and make ready for the next command. A slower rate of play would reduce meter problems considerably for a lot of members.
This is essentially correct. A slower, more deliberate style of play will reduce meter problems by allowing your CPU to settle down after taking action on the screen.
I ran some tests of various actions as evidence. I used the same setup to monitor my CPU performance as I have used before. Only the game client Firefox window open, Browser and Flash plug-in process affinity set to CPU 1, low flash quality, aim arc and avatar movement turned on, pretty much nothing going on in CPU 1 other than the game. Browser cache cleared at the start.
Each horizontal line is 10% CPU usage, each vertical line is 5 seconds elapsed time.
Observations:
Changing the spin on the ball or checking our ball type has minimal CPU impact, about a 10% increase and need not be worried about.
Pulling down any of the three menus, main menu, friends, or invite, has minimal CPU impact. WGT did a good job with these animations.
Changing clubs has a significant impact on our CPUs. Anywhere from 5 to 10 second increase in CPU usage of 30 to 50%. I think the reason is because the avatar stance changes and the club on the screen changes rather than the pop-up club menu animation. Room for improvement by WGT IMO. Make sure to wait for the CPU to settle down after changing clubs.
Moving the aim triangle on the mini-map or fairway has a significant impact on our CPUs. About a 5 second increase in CPU usage of 50%. Continuously re-drawing the aim box and arc on the screen is my guess on the reason. Turning the aim arc off only provides a slight improvement. Room for improvement by WGT IMO. Make sure to wait for the CPU to settle down after moving the aim triangle on the fairway or mini-map.
Zoom, move aim marker, zoom back has a huge impact on our CPUs. It takes about 10 seconds to complete the actions with an increase in CPU usage peaking at 70%. The screen image is loaded with the new view, marker moved, and then the original image is re-loaded. I wasn't running full screen either. Worth looking into how images are cached and loaded on the screen IMO, although it should be basic stuff inside Flash. The image size isn't that huge at 120 to 150kb each. Make sure to wait for the CPU to settle down after changing views to aim.
Standing idle on the tee uses about 12% of my CPU capacity. The only animations are on the mini-map, the flag moving and the ball location pulsing on the tee. Hard to believe those two small animations take 12%. What else is going on inside WGTs code when I'm not doing anything? Something WGT could look at and reduce. Kill the flag flapping and ball location pulsing for starters. If idle usage were cut in half to 6% it would save some meter stutters I'd bet.
Right now we should play more deliberately and take our time after some of the above actions.