Release Notes for JMRI 5.13.3 release

Date: August 8, 2025

From: Bob Jacobsen

Subject: Test Release 5.13.3 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 June 2025. (See the tentative release schedule)

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:

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

2. 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.
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.
4. 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.
5. 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.

Problems with this release

• Since JMRI 5.11.6 Layout Editor may display images in front of the drawn tracks, obscuring them, instead of drawing the images behind the tracks.

If that affects you, please either wait for JMRI 5.13.4, due out early in September, or pick up a JMRI development build installer from Jenkins. In the meantime, as a workaround you can set the image to level 0 using the pop-up menu on the image.

New warnings for this release:

None Yet

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.11.8 GitHub release.

Changes since Test Release 5.13.2:

The full list of included changes is available from our GitHub code repository.

Hardware Support

BiDiB

• Add "keep-alive" setting for netBiDiB connections.

CBUS

• Improved Node Manager CANCMDB support.

Roco z21/Z21

• Fixes a bug when programming locos.

Control Panel Editor

• Fixed a bug that would cause Markers to be created in random locations.

DecoderPro

• There are two new columns in the DecoderPro main display: "Decoder Manufacturer" and "Decoder Family". These start out hidden. To display them, right or control click in the header of any column, and then put a check next to the column name.
• The individual DecoderPro tab panes can now be detached and independently positioned on the screen. To detach a pane, click on the "two pages" icon on the tab. To reattach, just close the detached window.
• Fixed a bug where changes to the speed table sliders would not remind you if they had not been saved to the roster file.

Dispatcher

• At the end of a PAUSE transit action, set speedby signal, do not blindly restore pre-pause value.

Layout Editor

• Fixed a bug that would cause Markers to be created in random locations.

OperationsPro

• New feature, a non-lead car in a kernel departing staging or spur can now have a custom load that doesn't match the lead car
• Added "hyphen" feature to the train name. The program will drop "-(something)" from the train's name on Manifests and switch lists
• New enhancement, you can now set the maximum length for a track in a pool
• Added G scale 1:24 ratio option in the Setting window, renamed G scale 1:32 ratio "Gauge 1"
• Fix a bug with RWE or RWL and no track assignment, along with using a schedule that doesn't specify car's load

Panel Editor

• Fixed a bug that would cause Markers to be created in random locations.

Preferences

• Prevent duplicate start up entries when adding a WiThrottle start up action.

Roster

• There are two new columns in the DecoderPro display of the roster: "Decoder Manufacturer" and "Decoder Family". These start out hidden. To display them, right or control click in the header of any column, and then put a check next to the column name.

Signals

Signal Heads

• For signal heads using the DCC Signal Decoder, an option has been added to the Add/Edit dialog to copy the set of appearance numbers from another signal head. This can be used to create a custom set of appearance numbers that can be easily applied to new and existing signal heads.

Switchboard Editor

• Adds check to prevent a duplicate Turnout / Sensor / Light UserName being set.

Throttle

• Uses correct connection for non-default Throttle release / dispatch requests.

Warrants

• The getWarrantSpeedMessage() method has been added to the Warrant class. This is a public class that can be used by scripts and LogixNG formulas to get the current Warrant speed message. The message format depends on the Interpretation selection in Preferences ⇒ Warrants.

WiThrottle Server

• Prevent duplicate start up entries when adding a WiThrottle start up action.

Miscellaneous

• Fixed a formating problem in "Report Issue" tool
• Added a link to the JMRI users group in the Help menu

---