I just realized that after hitting “This Hallowed Ground” on VASSAL game list, a message saying “Error.set_lower_maximum_heap_heading” pops up.
I tried to change lower and maximum heap (256-512 per default; actually they are, respectively, at 1024-2048 level).
After entering the module, I try to scroll the map vertically and horizontally but a new java message comes out:
"Full memory
VASSAL run out of memory. This modules requires more maximum heaping than setting. Please, put more maximum heaping in Preferences settings, and run VASSAL back".
That’s exactly what I did. Switching from 512-1024 to 1024-2048. In vain…
Any suggestions?
Thx in advance
It will not work on your machine to set your max heap to 2048MB or more,
probably because your machine is 32-bit. When you try to set your maximum
heap to an impossible value, VASSAL tries to find a value which will work,
but probably isn’t optimal. You need to set your max heap to something
less than 2048MB.
I have no problem running this module with 512MB max heap, so long as I
turn on memory-mapped images in Preferences. Try that.
Also, your detailed report of the error message tipped me off that you
were seeing an error message key, not the actual mesasge like you should
be. That bug is fixed in svn5147.
My machine is 32bit running.
I turn on/off memory mapped images in Preferences (turned back to 256-512) but it doesn’t work with This Hallowed Groung. Loading A Fearful Slaughter VASSAL module, no matter if memory mapped images option is on or off, I can see any map of that module…
Where can I download that svn5147 VASSAL version?
Thx for answering
Both A Fearful Slaughter and This Terrible Sound VASSAL modules work great with 256 and 512 initial/maximum heaping. No need to turn “prefer memory-mapped files for larger images?” option on.
I asked a friend of mine to open This Hallowed Ground vassal module up and he had the same problem: running out of memory (he has 1 giga RAM). That’s funny because when my machine had just 1 mega RAM, This Hallowed Ground VASSAL module worked very fine…
Thx for link sending, Uckelman
Two friends of mine share the same problem with THG VASSAL module…
Everyone gets a message about “running out memory”. We can see hex’s identification code all over the blank screen, but there’s no map to be seen…
Our initial/maximum heap settings is 256-512. Their own pc machine have 2Giga RAM.
I had a go at this also because I am on a crippled 1GB XP box at the momement.
With ‘Prefer memory mapped files for large images’ turned OFF, I was able to start a new game once I had increased the Maximim Heap Size to 768MB. Scrolling performance was terrible, but it was playable with patience. Lower Maximum Heap sizes gave an ‘Out of Memory’ error after quite a long wait.
With ‘Prefer memory mapped files forlarge images’ turned ON, I was unable to start a new game at any maximum heap setting, getting the ‘Out of Memory’ error quite quickly.
After playing with this a bit longer, I am finding that no matter what value I set Max Heap to, starting a new game up appears to work, except the map does not appear. I tried 768, 512, 256MB. I can pull a piece and move it about and get movement reports, but no map. After a minute or so, an Out of Memory error pops up.
