The limits are not relevant to the size or composition of the module itself, but the size and uniformity (type) of the individual files is what matters as Brent has pointed out.
In your preferences try also to turn off high image scaling as this requires more memory I have a mod at 60mb w/ 1500 images and it chugs along without no problems, so it would seem that your module's construction needs to be reexamined if you don't want to cut anything out - such as cutting your boards into smaller sub boards joined together, eliminate duplication and optimize module build etc. _____ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of benw_h Sent: Sunday, October 21, 2007 8:07 AM To: [email protected] Subject: [vassalengine] Re: What are the best ways to stop memory heap errors? OK thanks - I can't actually work out how to increase the memory allocation, and obviously cutting stuff is not very useful as it effects the game. Are the limits relevant to what's on sreen or to everything in the module? I might be able to split the extensions into another module and treat it as two seperate games. Not very elegant, but I am a bit desperate! --- In vassalengine@ <mailto:vassalengine%40yahoogroups.com> yahoogroups.com, "Brent Easton" <[EMAIL PROTECTED]> wrote: > > Ben, > > >....and do any of the changes you make effect saved games already in > >progress? So far I've reduced the colours of all the maps. > > Reducing the number of colors in the map can reduce your file size in the module (as long as you reduce it to <= 256 colors, make it indexed and save it as a PNG), but this will have no effect on the memory required by VASSAL to display those maps. > > The number and size of maps, counters and cards is really the only issue. > > > > > All of my > >pieces are already only 1kb (does it matter how many colours they are > >if they are already this small?). I'm still getting out of memory > >errors. Does the sheer number of images in the module (even if not > >displayed) effect this? The mod is about 25Mb (5+5 per extension), with > >probably around 5-600 piece images, 8 maps (with multiple boards in > >most cases), and another 200 cards. Any advice? AT present I've truned > >my attention to increasing the memory allocation... > > __________________________________________________________ > Brent Easton > Analyst/Programmer > University of Western Sydney > Email: [EMAIL PROTECTED] > [Non-text portions of this message have been removed]
