VASSAL stopped working and 3.2.6 update does not work


I was using VASSAL 3.1.15 for at least 1.5 years no problems at all for the three modules I play. Then all of a sudden when launching VASSAL, the module library window would appear, but after picking a module to launch, the module start page would be blank no graphics and could not do anything.

Updated to VASSAL 3.2.6 today June 22.

Still have problems. VASSAL will launch, the module library will appear, but cannot start module from the library window (not able to select anything in that window). Currently right now when I use ‘File’, ‘Open Module’, nothing happens, no new screen appears. Minutes earlier it would get to the next option, I would pick a module and try to open, and the module start page would have no graphics so cannot begin.

then would have to force quit, as nothing is responding.

I do not get any error log with 3.2.6. The error log I currently see is from 3.1.15. Interestingly, I had looked at the error log when having problems with 3.1.15, and it had a bunch of error messages, but somehow it was overwritten. I copy the only error log I can find at the end of this message.

I did a software update check for my Mac today, and it said my software was all current. I am not aware if any software updates were done at the time the problem started - I did not activate any changes myself to initiate the problems.

Thanks for your help


My details
Macintosh MacBook Pro
OS X 10.6.8
CPU 2.3 GHz Intel Core i5
Memory 4GB
Video Card ?
VASSAL Version 3.2.6 and 3.1.15
Java Version ? The error log says Java 1.6.0_51, but I could not verify this

here is the copy of my error log from 3.1.15 (no log seen for 3.2.6):

22 Jun 2013 11:49:24.478 0 – Starting
22 Jun 2013 11:49:24.480 0 – OS Mac OS X
22 Jun 2013 11:49:24.480 0 – Java version 1.6.0_51
22 Jun 2013 11:49:24.480 0 – VASSAL version 3.1.15
22 Jun 2013 11:49:24.722 0 – Manager
22 Jun 2013 11:49:25.715 0 Module /Users/kurtvannugtren/VASSAL/modules/Crete.vmod not found - Removed.
22 Jun 2013 11:50:31.202 0 – Exiting

This sounds a lot like the issue discussed here:

Please try the latest 3.2.7 development build from here

and see if that fixes your problem


great that fixed the problem it appears, thank you!