Release Notes for JMRI 5.13.1 release
Date: June 30, 2025
From: Bob Jacobsen
Subject: Test Release 5.13.1 of JMRI/DecoderPro is available for download.
Notes:
This is a test release. Please
post a note
if you encounter any new or old bugs!
And please back up your JMRI files before installing this, in case you want to go
back to an earlier version.
This is the next in a series of 5.13.* test releases.
It requires at least Java 11 to work.
We recommend that you use Java 17.
(See our page on downloading Java)
We expect this series to end in the next JMRI production release in December 2025.
(See the tentative release schedule)
Some of the changes involved are quite extensive.
They may require a certain amount of experience before they are working well.
Therefore, this test release should be considered experimental.
We would appreciate your feedback on it.
JMRI is now only available under the
GNU General Public License. For more information, please
see our
copyright and licensing page.
Update From Older JMRI Versions
If you are currently using a version older than JMRI 5.0, please follow these instructions carefully:
- Is your current version older than JMRI 4.12?
If so, then update to JMRI 4.12 first, and ensure everything works correctly: check
start-up, check things you need to be working, and check the JMRI log as well) before doing anything else.
Store your configuration and panel files under a new name and use those from now on.
Then continue with step 2.
If you are currently using JMRI 4.7.3 or earlier on Linux or macOS (Windows doesn't need this),
then it's very important
that you update to JMRI 4.12 and
carrying out the migration process described in the JMRI 4.12 release note
before updating to any later release.
- Is your current version older than JMRI 4.20?
Then update to JMRI 4.20 first, and ensure that works correctly (check
start-up, check things you need to be working, and check the JMRI log as well) before doing anything else.
Save your preferences again.
Store your configuration and panel files under a new name, use those from now on, and go on to step 3.
- Is your current version older than JMRI 4.24?
Then update to JMRI 4.24 first, and ensure that works correctly (check
start-up, check things you need to be working, and check the JMRI log as well) before doing anything else.
Save your preferences again.
Store your configuration and panel files under a new name and use those from now on.
- Is your current version older than JMRI 5.0?
Then update to JMRI 5.0 first, and ensure that works correctly (check
start-up, check things you need to be working, and check the JMRI log as well) before doing anything else.
Save your preferences again.
Store your configuration and panel files under a new name and use those from now on.
- You can then install this release.
Following this multi-step order of updating via stable major releases safeguards you against possible migration issues
that can arise from skipping these versions.
New problems with this release
New warnings for this release:
Older warnings
See the
JMRI 5.12 release note for more warnings predating the 5.13 development series,
including pointers to various migration issues.
These may be relevant to you if you're updating from an earlier version;
we strongly recommend you update to at least
JMRI 5.0
before installing this test release.
See
instructions above.
- Since JMRI 4.99.1
This test release, and all subsequent ones, require the use of
Java 11 or later.
We recommend that you use Java 17.
Java 8 is explicitly not supported.
There's more information on this migration on the
JMRI Tech Road Map and
JVM Capabilities pages.
- If you're using a Firefox web browser and opening JMRI
help files locally (not over the web), a Firefox bug
can sometimes cause it to enter a loop. There's a
workaround in
this JMRIusers post.
- Since JMRI 5.11.3
There's been a change to how OpenLCB turnouts are
addressed when using the MTT addressing short cut.
Turnouts 253,254,255, 510, 511, 512, 765, 766 and 767
will be addressed differently. If you're using any of these
via e.g. MTT253, you will need to change the address. If you've
been having trouble getting those addresses to work, this change should
fix that.
- Since JMRI 5.11.5
OperationsPro program file locations were changed in
JMRI 5.11.5. Start up actions
involving operations windows from previous releases no longer work. You'll need to remove them and
add them back if needed.
Download links:
These files are located in the
JMRI 5.13.1 GitHub release.
The
full list of included changes is available from our
GitHub code repository.
Hardware Support
CBUS
- When WiThrottle is asked Share / Steal / Cancel? or Share / Cancel ? , the main
JMRI Throttle silent Steal / silent Share options are checked for preferred behaviour.
- The Console Filter is now displayed as a check-box tree.
LocoNet
- Resolved a Console log 'Error' message that could be seen when
using the Slot Monitor's "Clear All Non-InUse Slots" button.
Layout Editor
NX - Entry/Exit Tool
- Fixed a bug which could sometimes cause extraneous messages
about failure to create a multipoint route even though one was available.
LogixNG
- The class jmri.jmrit.logixng.Category has been split into
jmri.Category and jmri.jmrit.logixng.LogixNG_Category.
Meters and MeterFrames
- The shutdown process has been modified to detect changes to the meter settings.
OperationsPro
- Fixed a bug where a train build would hang after the upgrade to 5.12 and there were also built trains created with an older version of JMRI.
- Added quick service for classification/interchange tracks. This is an experimental addition, looking for testing and feedback.
Preferences
- The Shutdown preference help has been updated. The store request now includes
a Cancel option which cancels the shutdown process.
Scripting
- Upgrade YAAT to 3.4. The @include statement has been added.