VASSAL 3.3.0-beta3 Released

General Discussion
1

[size=200]VASSAL 3.3.0-beta3 released[/size]

The VASSAL Team is happy to announce the release of VASSAL 3.3.0-beta3.

[size=150]IMPORTANT[/size]

  • This is a beta release. Things may be broken which worked in 3.2.17. If you find a bug introduced since 3.2.17, please report it.

  • If you save a module in VASSAL 3.3, you will NOT be able to open it afterwards with VASSAL 3.2. We recommend keeping a backup copy of any pre-3.3 modules you plan to modify in 3.3 until you’ve verified that everything works to your satisfaction.

  • Some modules containing custom drawing code may render incorrectly on HiDPI displays. If you are the maintainer of such a module, let us know and we can advise you about what needs updating for 3.3 in your code. (We are aware already that VASL has this problem and are working with its maintainers to update it.)

[size=150]Download[/size]

Linux
Mac OS X
Windows
Other
Source code

[size=150]New in 3.3.0[/size]

Features:

  • 12557, 12613: Compatibility with Java 9+: VASSAL 3.2 would not run with anything newer than Java 8. VASSAL 3.3 now requires Java 11 or later.

  • 12558, 12724: Bundle Java with VASSAL: The Mac and Windows packages now include Java 14. It is no longer necessary to install Java separately when using one of these packages.

  • 12559: HiDPI support: VASSAL now has support for displays with a high pixel density (e.g., Retina displays). On such displays, you should now see correctly sized interface elements and sharper image rendering.

Bug fixes in 3.3.0-beta3:

  • 12732: Use all available rendering hints for text
  • 12731: javax.sound.samples.Clip fails to convert WAV files it can play

Bug fixes in 3.3.0-beta2:

  • 12579: Don’t bundle Java on Linux

Bug fixes in 3.3.0-beta1:

  • 12556: Mass Piece Definer does not sort image names

For changes prior to 3.3.0-beta1, see the change log.

[size=150]Minimum Requirements[/size]

VASSAL 3.3 requires Java 11 or later.

The Windows and Mac packages have an appropriate version of Java bundled with them, so there is no need to install Java separately on those operating systems.

[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.

Report bugs here in the Technical Support & Bugs category at the VASSAL forums or by email to bugs@vassalengine.org.

Cheers,

The VASSAL Team

2

Is beta3 bundled with Java 13 or Java 14? Says 13 above, but I thought you switched it to 14…

3

Thus spake jrwatts:

Is beta3 bundled with Java 13 or Java 14? Says 13 above, but I thought
you switched it to 14…

That was a typo; thanks for catching it.

14 is correct.

–
J.

4

Assuming that no bugs are reported, and testing goes well, when would it be likely that beta3 becomes the new Vassal production version please? Thanks.

5

Thus spake 2D6Wargamer via messages:

Assuming that no bugs are reported, and testing goes well, when would it
be likely that beta3 becomes the new Vassal production version please?
Thanks.

If there’s really nothing to do between now and then, maybe 10-12
days?

I’m waiting for a reply about a test build to address some rare tiling
failures; if I do get a reply soon and the changes worked, that will
go into beta4, as it’s something which needs broader testing. If I don’t
hear back in a timely fashion, then I’m not going to hold up 3.3.0 on it.

–
J.

6

Any further news about beta4? Or is beta3 going to be the last release until full production?

Thanks.

7

Thus spake 2D6Wargamer via messages:

Any further news about beta4? Or is beta3 going to be the last release
until full production?

I’m aiming to release beta4 later this week.

–
J.

8

Any ETA on beta4? No rush, I just am curious on timing because I have a module that I’m actively working on that will be impacted by some of Brent’s pending bug fixes. A rough ETA on timing would help me plan my schedule. Thanks for doing this BTW!

9

Thus spake m3tan:

Any ETA on beta4? No rush, I just am curious on timing because I have a
module that I’m actively working on that will be impacted by some of
Brent’s pending bug fixes. A rough ETA on timing would help me plan my
schedule. Thanks for doing this BTW!

beta4 was released last week. 3.3.0 will be released later this week.

–
J.