Thanks for mentioning that, Gary. I didn't even know that it was necessary to redo this setting after downloading each update. I thought this was a once-and-done thing.
Perhaps this tidbit of information should be added to the Wiki?!? Thanks. Kevin ----- Original Message ----- From: Gary Krockover To: [email protected] Sent: Thursday, December 28, 2006 4:34 PM Subject: Re: [vassalengine] VASSAL Memory Issues A dialog box that prompts you for memory allocation each time you install (updates or the full install) would be nice. I'm always having to go back and modify the AMvassal.jnlp file after each update to bump that value up - and if I forget sometimes, then I start to get the out of memory errors. GJK At 03:18 PM 12/28/2006, you wrote: >Hi guys. > >I'm still going into VASSAL and finding players who are running out of >java memory. Some of the larger modules such as DAK II are impossible >to run without altering the VASSAL shortcut, something a lot of gamers >struggle with. Is there anything which can be done from a release >perspective to either always run the app with -Xmx512M or at the very >least pop-up an error message with a walk-through of how to fix? > >cheers! > >Ben [Non-text portions of this message have been removed]
