@CK: Did you already rule out that the VBS changes are the actual problem (i haven't looked at the differences there in detail, so don't know if that could cause such behavior)?
Is there something in the vbs scripts that could cause this? I never thought that there are instructions for the graphics in it...
The recent VBS change should improve performance, not degrade it, but it's always possible that something did in fact degrade in the process. Here's a detailed explanation of what changed between VBS Core 3.45 and 3.46:
The 'cvpmDictionary' class was originally written (by someone else) as an alternative to Microsoft's "Scripting.Dictionary" object because, at one point, MS had declared that object as "unsafe for scripting" and thus using the Dictionary would pop up security warnings when people started up their tables. The alternative implementation worked around that issue successfully, but at the cost of performance because every time you wanted to look up a key in the dictionary, you had to scan through the whole thing until you found it. That scan was happening hundreds of times a second just to manage the timers, and even more if you used other classes that depended on a dictionary (eg. the magnet, impulse kicker, etc.).
The change I made was to turn cvpmDictionary into just a simple "wrapper" around MS's Dictionary, since it's been many years since that "unsafe for scripting" fiasco happened, and MS has since fixed whatever problem there was with it. Unless you're still running a box on Win98 or some very early build of WinXP, your script host should have long since been updated. MS's Dictionary is much, MUCH more efficient than a VBScript-interpreted-index-based substitute, so wrapping that should make for a significant performance improvement in tables using the VPM core classes.
That said, if you suspect that this script change is responsible for your slowdowns, a really easy way to check this is to take the core.vbs from one of the earlier builds and save it over the core.vbs in the current build. (Rename your current core.vbs to something like "core346.vbs" or "core.vbs.bak" so you can restore it later.) Then just try your table again and see if you have the same issue. Please let us know if doing this does or does not resolve your issue - if it does, then I'll assume that there are other reasons not to use Microsoft's Dictionary object and we can go back to the cvpmDictionary we had before. (Easy enough.)
Top
Contributor
are all trademarks of VPFORUMS.