Wheels65:1. Start with a clean cache (browser & Flash)
Did - always start with clean cache ....
Wheels65: 2. If you're Windows based, use the Task Manager to tell you when your CPU computing at a rate under 100% - if the whole window is green don't try to swing
Use a CPU Usage gadget, on a proper old Quad-Core. CPU was in the LOW teens every shot. The CPU only spiked AFTER the shot was taken, or when it froze....at which point on some occasions it would say "internet connection not working" try again and lo and behold it plays the shot fine. To me, that is overload on the servers processing such that a number of the sessions timed-out and WGT could not process the shots as it had lost the data transfer from the client side back to the server side. All depends on the server config and what level of load-balancing they have in place. Not sure what level of session-state management they have in place.
WGT do have a number of servers, at least 7 I would imagine from the server names I have seen - maybe more. However, I suspect that once you are on a server you stay on it until you log off and log back on again to pick up a different one in the pool. This I have seen when I have had some rouge sessions previously - but eh, I should be able to rely on WGT having enough server pool to cope with peaks.
Wheels65: 3 . and, finally, hold your club at the top of the swing for 2-4 seconds before releasing it
Never had to do this before, why do I need to start now. I try it from time to time, but it is not intuitive - Also did the "practice strokes" suggestion. Also understood that holding the swing any length of time is seen as use of a "cheat mode" - or is that heresay :)
Played perfectly fine this evening, and guess what, I have not changed a darn thing on my side.