Lmorgan007:
Is the jerky meter down to a browser/flash combo, or down to ruining a computer by browsing too much flesh (ahem)?
The reasons for a jerky meter are much more complex than just a browser/flash combo.
How powerful is our computer?, is it single core or multi-core? does it have a separate or integrated video card?, Are your video card drivers up to date?, how much memory does your computer have?, what O/S is it running?, what is your computer doing other than running the game?, then we get to which browser and which version?, and then which version of Flash player? Add to that the settings used in Flash, is hardware acceleration on? And what game settings are you using, is Flash quality high? are flag animations on?
All of the above appear to matter when running WGT's game.
What's strange is, I can run Flash animations much more complex than the apparently simple swing meter, and they run smooth as silk.
Here's an example. If that stutters or is jerky close all WGT windows.
What is it about WGT's game code that makes all the fiddling with our systems necessary?
Well 18 months or so ago PugsAce started this eye-opening thread titled "Flash Optimization of the Game" which posed the question is optimization of the WGT code possible? For those technically minded, the Adobe document
"Optimizing Performance for the ADOBE® FLASH® PLATFORM"
is an interesting read.
As far as I know we never got an answer from WGT whether they've optimized their code per some of the tips in the above document or not.
One last item, concerning whether or not a browser makes a difference, according to the observations noted in this test of Flash frames per second it makes a big difference: Testing Frame Rate of a Flash Movie (that looks very smooth to me btw) You might try that page in different browsers to see what works best. Personally I didn't notice any difference between FF, Chrome or Maxthon 3.