[messages] Edit: Re: [General Discussion] VASSAL 3.2.16 Released

uckelman uckelman at nomic.net
Sat Dec 31 19:50:50 CET 2016


[This message has been edited.]

[size=200][b]VASSAL 3.2.16 released[/b][/size]

The VASSAL Team is happy to announce the release of VASSAL 3.2.16, which
which fixes several problems found in earlier versions.


[size=150][b]IMPORTANT[/b][/size]

* 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 6 is compatible with VASSAL 3.2. VASL users, please upgrade!

* If you are using MacOS X 10.8.3 or later, you may see the message
"VASSAL-3.2.16.app is damaged and can’t be opened. You should move it
to the Trash." The problem is NOT that your download was corrupt, but
rather that MacOS is preventing you from running VASSAL. To start
VASSAL, control-click or right-click the app bundle's icon and select
Open from the menu. You'll see a dialog asking whether you want to open
VASSAL. Select "Open". Thereafter, you should be able to start VASSAL
normally.

* Oracle's Java 7 and 8 have very poor rendering performance on some
MacOS X systems, particularly Yosemite. If you are experiencing this,
please use Apple's Java 6 instead.

[size=150][b]Download[/b][/size]

[url=http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.16-linux.tar.bz2]Linux[/url]
[url=http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.16-macosx.dmg]Mac
OS X[/url]
[url=http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.16-windows.exe]Windows[/url]
[url=http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.16-other.zip]Other[/url]
[url=http://downloads.sourceforge.net/vassalengine/VASSAL-3.2.16-src.zip]Source
code[/url]

[size=150][b]Recent Changes[/b][/size]
The following bugs in 3.2.14 are fixed in 3.2.16:

* 12524: Images retile unnecessarily due to bad timestamp
* 12522: Deck shuffling logged incorrectly

The following bugs in 3.2.14 are fixed in 3.2.15:

* 11864: Relative $INSTALL_DIR in VASSAL.sh breaks paths for
documentation 
* 11769: NPE in Deck.getState()

For changes prior to 3.2.15, see the change log.

Please report all bugs in 3.2.16, 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.

[size=150][b]New Features in 3.2[/b][/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
    counter.
  - 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
    properties inaccessible.

* 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]

[size=150][b]Minimum Requirements[/b][/size]

VASSAL 3.2 requires the Java Runtime Envrionment to run.

Linux: Java 6 or later 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 or later for Macs where Java 6 is available.

Windows: The recommended minimum Java version for Windows is 1.6.0_45
(a.k.a. Java 6 Update 45). Windows users installing VASSAL with the
Windows installer will be prompted to update Java if what they have is
older than 1.6.0_45. After upgrading Java on Windows, you must restart
your computer in order for Java programs to work properly.

If you've installed Java 7 on Windows and thereafter VASSAL fails to
launch: The Java 7 installer does not uninstall Java 6, and having both
installed simultaneously prevents both from working properly. Therefore,
check whether you also still have Java 6 installed. If so, removing Java
6 and rebooting will most likely solve your problem.

[size=159][b]Help us test[/b][/size]

Should you find any problems/oddities/bugs, please tell us so that we
can
fix them for a future release of VASSAL.

Report bugs here in the Technical Support & Bugs category at the
[url=http://vassalengine.org/forum/viewforum.php?f=3]VASSAL forums[/url]
or by email to [email]bugs at vassalengine.org[/email].


Cheers,

The VASSAL Team

_______________________________________________
Read this topic online here:
http://www.vassalengine.org/forum/viewtopic.php?p=51054#p51054


More information about the messages mailing list