piztaker:
SHRUDE:
I use Google Chrome for WGT, it is set to clear everything when i close it, so each time i open it, it is a fresh cache & cookie free browser.
I rarely get meter lag.
Check your flash cache, I bet there's stuff still on it.
Yep. I wouldn't want Chrome-enabled Flash Cache clearing after each browser session (don't know if that's even one of Chrome's features).
Having to reset all the game's options each time I opened the client would be a royal pain.
When I do clear my Flash Cache, I do it thinking that "old files" (corrupted, or not - by what, or whomever) will then be re-freshed with "new/proper files" as they become necessary. Just by confronting the need for these files, while playing the different courses and their conditions, as well as using balls or clubs that may have been "bug-fixed", these "modified files" are added to the cache in place of the flushed ones.
With all the updates that are made (evidenced by the version number changes), I feel that a lot of the problems that people have (myself included) are partially caused by having conflicts between "old cache files" and "new cache files" as they are called-up during a game - the effects ranging from minor delays or screen-stutters, to all-out crashes of the gameclient screen.
These reasons for clearing the cache (which is basically a set of instructions) aren't necessarily as obvious to others as they are to some of us who try to keep-up with at least the basics of how all this works. Those who are "geeks" (and I use that term with the best possible intentions - as I am truly envious of their wide-ranging knowledge and talents) seem to know this stuff innately, and may feel that it is thus "common sense"... which it isn't.
To be safe (to have the least possible problems), I clear my caches after each "published" update, when new courses, items, or features are introduced to the game, and when I experience "hmmmm..." moments. Sure... the new files may cause a slight delay while they are downloading, but I think it's worth having less problems in the long run.
Whether or not WGT's "minor version changes" warrant cache-flushing, I think, is still a matter up for debate. For instance, if a developer has a "Eureka Moment" about a wedge that wasn't programmed properly (initially), and changes the attributes of said wedge, are those files "held for release" until a "major update", or are they snuck-into a minor version change? As there is no published list of version changes, we are left to decide on our own when to update our caches.
Sorry this was so long... but I felt the "detail" was once-again necessary.