Tips
In order to run this mod,
users must be running Vassal 2.5 (upon its release) or version 2.5b3.
Until the release of 2.5, users can obtain
2.5b3, or any of the latest Vassal beta versions at http://www.vassalengine.org/beta/
It is important that players
are running the correct version. This mod will not function correctly if you
are using Vassal 2.4.2 or lower.
This mod is graphic
intensive, with lots of pieces. Users may experience long load and/or synch
times depending on the amount of available RAM either player has (generally
512mb or less).
If you are experiencing “dragging”
or slow movement/responses of the cards or playing pieces, there is a tweak
that you can apply to Vassal to improve performance. I actually recommend this
tweak regardless as it also helps eliminate “Out of Memory” errors that may
occur given the complexity and graphics in my mods.
This tweak is based on Windows OS but should be similar for Macs and/or Linux
systems.
On your machine look for a
file called AMvassal.jnlp . This file can usually be found in a location similar to this :
C:\Documents and Settings\Administrator\ApplicationData\Sun\Java\Deployment\cache\javaws\http\Dwww.vassalengine.org\P80\DMws\AMvassal.jnlp
Open the AMvassal.jnlp
with an editor (word, notepad etc.) and you will see a bunch of html tagged
coded jibberish.
Look for a particular section
that reads:
<j2se version="1.4+"
max-heap-size="256m"/>
Change the max heap size to match up to your current
memory. Here is mine for example:
<j2se version="1.4+"
max-heap-size="1024m"/>
As an alternative if you keep background apps running you
can change this line of code to read something like this:
<j2se version="1.4+"
initial-heap-size="256m" max-heap-size="256m"/>
Regardless which method you choose, the total heap
size cannot exceed your physical memory in your computer
Also anytime you update Vassal the AMvassal.jnlp
file will have to be re-edited (so I’m told).
Any questions, suggestions and/or bugs send an email
to timothy.mccarron@sbcglobal.net
.