[size=200]VASSAL 3.2.0 released[/size]
The VASSAL Team is happy to announce the release of VASSAL 3.2.0.
If you save a module, game, or log in VASSAL 3.2, you will NOT be able to open it afterwards with VASSAL 3.1. We recommend keeping a backup copy of any pre-3.2 files you plan to modify in 3.2 until you’ve verified that everything works to your satisfaction.
If you found it necessary to set a very large maximum heap (> 512MB) for a module with VASSAL 3.1, it should now be possible with VASSAL 3.2 to set a much lower maximum heap and achieve similar or better display performance. 512MB should now be adequate for most modules.
VASL 5.9.2 and earlier are not compatible with VASSAL 3.2.0. Work to update VASL for 3.2 is ongoing.
VASSAL 3.2 is backwards compatible. VASSAL 3.1 is NOT forwards compatible. This means that modules, logs, and saves from VASSAL 3.1 should work in 3.2, but there is no guarantee that modules, logs, and saves from 3.2 will work in 3.1. Therefore, if you write a module, log, or save file in 3.2 DO NOT expect to be able to load it in 3.1.
Current versions of VASL and VSQL are not compatible with VASSAL 3.2.0. Work to update VASL for 3.2 is ongoing.
[size=150]New Features in 3.2[/size]
Levels within a Layer can be moved up or down the level list using buttons. [RFE 1919]
Mass Piece Loader activated by ‘Add Multiple Pieces’ and ‘Add Multiple Cards’ options in right-click menu in Editor. Specify a folder of images, specify a counter template and Vassal will automatically load the images and generate units. [RFE 1927]
Description field added to Toolbar Menu and Multi-Action button components. [RFE 1885]
Specify Keystrokes by name - Key Commands can be entered as single Key Strokes as in earlier versions of Vassal, or can be given a 2 or more character names. Named Key Strokes are essentially ‘invisible’ to users. Vassal guarantees that a unique real keyStroke will be allocated to each uniquely named Keystroke. [RFE 1928]
Decks can specify by Property Expression which pieces are allowed to be dropped onto them. Pieces which may not be added are returned to where the drag started. [RFE 1935]
Decks can now specify a Hotkey for the Reverse and FaceUp/Down command and can customize the Reverse and Re-shuffle menu command names. [RFE 1938]
Counters now support the DeckPosition property. If a piece is not in a Deck, 0 is returned. If a piece is in a Deck, then the position of the piece relative to the top of the Deck is returned. The top piece returns 1, the next piece down returns 2 etc. [RFE 1937]
Support for MP3 sound files. [RFE 1934]
Fix Display/Color handling for Grids and Numberings. Allow Numbering to be visible when grid not visible in Zones. [RFE 1917]
Implementation of BeanShell allowing arbitrarily complex Java expressions to be used in Property Match Expressions, In-line Java expressions and new Calculated Property trait. [RFE 1801]
Display the Log File Comments in the Chat Window when a log file is opened or continued. [RFE 1939]
Global Key Commands created on a Map now have an option to affect counters on all Maps, not just the Map they are created on. [RFE 1902]
Traits that move a counter (Send To Location, Return to Deck, Moved Fixed Distance, Pivot) now update the same location Oldxxxxxx properties that Drag and Drop movement does. [RFE 1792]
Added repeat (loop) option to Trigger Action and Multi-action button. [RFE 1876]
Ensure all commands generated by a single user action are undone by a single click of the undo action. [RFE 2816016]
Option to allow non-owning players to move Restricted Access pieces. [RFE 1789]
Add ‘Snap to Grid?’ option to HexGrid and SquareGrid, defaulting to Yes. Allows Grid Snapping to be turned off for the whole grid. [RFE 2842811]
Streamlined room creation: automatic synchronization on room entry [RFE 1784]
New scenario updater [RFE 1899]
Allow Dynamic Property Select Value list to be dynamic [RFE 1926]
All scaling is now high-quality. Low-quality scaling (in hardware) caused too many graphics glitches on Windows.
The Invisible trait now supports adjustable transparency.
Map images are tiled the first time modules are loaded, to create an image cache. This should dramatically reduce the amount of memory needed to run modules.
Improved display of properties in the Editor [RFE 4323]:
- Display all available properties from all components structured in the
same way as the components of the module are built instead of all the
global properties being dumped in one menu.
- Available Global properties now appear without having to start a game.
Previously, globals like Deck and Zone properties where not available
unless you had started a game.
- Property and component names are sorted, except for the Piece Property
menu where the traits are displayed in the same order they exist in the
- If a menu has too many options to fit on the screen, it is now
scrollable, instead of stretching off the screen and leaving some
- Display all available properties from all components structured in the
Improvements to Layer trait [RFE 4717]:
- Follow Property name may be a BeanShell expression.
- Improved layout for Layer dialog in Editor.
Notify user when image loading fails [RFE 1887]
The following bugs in 3.1.20 are fixed in 3.2.0:
- 4831: Module revision that created log is not displayed in errorLog
- 4820: ExecutionException in ImageSaver due to running out of memory
- 4818: Hide empty TurnTracker launch buttons
- 4807: Vengine.jar should be readable by group and other
- 4793: ChangePropertyButton cannot be cast to GamePiece when creating toolbar button
- 4784: Unable to edit regions within an irregular grid via mouse and arrow keys once created
- 4775: a context menu containing a single submenu is deviously disallowed
- 4764: Losing Player Sides when opening module with different language set
- 4763: Symbolic Dice button window results do not open correctly
- 4690: Hide Pieces Toolbar button causes Toolbar button icons to move
- 4547: Ensure that image data is integer type before casting to DataBufferInt
- 4452: Batik loads com.sun.image.codec.jpeg.TruncatedFileException, which doesn’t exist in Java 7
- 4402: StackOverflowError from recursively generating counter name with Label
- 4322: Bad justification for text labels containing global properties
- 4302: Global Hotkey cannot preserve execution order across server
- 4155: NoClassDefFoundError for com.sun.management.OperatingSystemMXBean
- 3864: IllegalStateException in ReturnToDeck.promptForDrawPile() when no decks exist
- 3745: NPE in SVGImageUtils.getImageSize() in Batik
- 3040: ClassCastException in CommandServer.run()
- 2746: DOMException on malformed SVG input
- 2711: Batik throws DOMException on SVG with flowRoot element
- 2694: Warn (Windows) users to reboot after Java upgrade
- 2671: BMPs are incompatible with memory-mapped images
- 2582: Mask and Peek menu entries are not translatable
- 2556: ImageOp does not support paths
For changes prior to 3.2.0, see the change log.
Please report all bugs in 3.2.0, even if they are bugs which you’ve already reported against other versions. We take your bug reports seriously—they’re the reason we’ve been able to fix so many bugs.
VASSAL 3.2 requires the Java Runtime Envrionment to run.
Linux: Java 6 is required for using VASSAL on Linux.
MacOS X: The recommended minimum Java version for using VASSAL on MacOS X is 1.5.0_08 (a.k.a. Java 5 Update 8) for Macs where Java 6 is unavailable, and Java 6 for Macs where Java 6 is available.
Windows: The recommended minimum Java version for Windows is 1.6.0_21 (a.k.a. Java 6 Update 21). Windows users installing VASSAL with the Windows installer will be prompted to update Java if what they have is older than 1.6.0_35. After upgrading Java on Windows, you must restart your computer in order for Java programs to work properly.
[size=159]Help us test[/size]
Should you find any problems/oddities/bugs, please tell us so that we can
fix them for a future release of VASSAL.
The VASSAL Team