I think it's a combination of things. It's easier to point a finger at the software thinking it is the problem but I think what we are seeing is that mods are becoming more advanced demanding more resources and power, the memory tweak is problematic for a lot of people and users are still running machines that are not quite the latest tech. All these factors combine and add up to a feeling the software is the issue when really it isn't although we may be stretching its limits as far as modules go with the current traits
Oops - well Brent beat me too the punch there in his latest reply -he knows the program better :-) _____ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Gary Krockover Sent: Sunday, February 04, 2007 6:38 PM To: [email protected] Subject: Re: [vassalengine] Re: More questions I'm with you on this one Brent, VASSAL loads fast and the screen refresh after scrolling is instantaneous. Zooming out can be a little slow, but we're talking like 10-20 seconds on average and after you've zoomed out once, it does so again instantly. So, I'll be curious to see what the issues are for some people and what, if anything can be done to help in those situations. I think that the one thing that might come to mind is having the memory allocation set in the preferences; or was that another option already - thought I saw it but maybe people grouped it with this one? GJK At 06:18 PM 2/4/2007, you wrote: >It is interesting that the most voted for option is to make VASSAL 'faster and more responsive'. > >I am very interested to hear from you all exactly which bits of VASSAL need to be made 'faster and more responsive'. > >Was it just a 'warm fuzzy feeling' type vote, or are there specific options/actions/components/traits that you feel need attention? > >Cheers, >Brent. [Non-text portions of this message have been removed]
