Release Notes for JMRI 2.99.1 release
Date: December 31, 2011
From: Bob Jacobsen
Subject: Test version 2.99.1 of JMRI/DecoderPro is available for download.
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 first in a series of test versions. We expect this series to end in a JMRI 3.0 production release, probably in Summer 2012.
Some of the changes involved are quite extensive. They may require a certain amount of experience before they are working well. Therefore, this test version should be considered experimental.
New warnings for this version:This release, and all later releases in this cycle, require Java 1.6.
Known problems with this releaseThis test release has a problem with preferences on Mac OS X. We do not recommend that Mac OS X users try this test release. This problem is fixed in
There are currently some connectivity issues for Users running Windows v7 64-bit and a Digitrax PR3 interface.
If you are experiencing issues, then please raise a question on the JMRI Users group for assistance
and try JMRI v2.99.2.
Please use these links for downloading:
Changes since production release 2.14
Oscar Moutinho made the following updates to the inControl web throttle app:
- Added Turnouts and Routes.
- Power Off does not block throttle.
- Some icons changed (used from /resources/icons/throttles/).
Matthew Harris made the following updates:
- Updated the NetBeans project file to use JDK 1.6
- Updated the Windows installer to use JRE 1.6 and to no longer install on Windows 98 and ME
Walt Thompson fixed a problem causing panel files with tooltips to fail validation.
Dan Boudreau made the following enhancements and fixes to operations.
- You no longer need a schedule to assign an alternate track to a spur. See "Alternate Track" under Edit Spur-> Tools.
- Added to print locations the ability to analyze how your tracks are consumed by various car types.
- New switch list print option, you can now have a different car format for your switch list. See Print Options.
- The build reports can be read using a text editor. This feature was enabled by using Java 1.6. See Print Options.
- Enhanced the manifest printout for passenger trains. Now when you have a route comment and there isn't any work, only the location's name and route comment is printed.
- "Block cars by pick up location" is now disabled if you use one of the generate custom load features from staging.
- Fixed a minor problem where the track defaults weren't shown correctly when using the "Add Track" button when editing an existing track.
- Fixed a problem when changing a car's road name or road number, sometimes the program would report that the car would not fit on the car's current track.
- Fixed a problem when using the conductor window and canceling a local move.
Paul Bender added a new Generic Consist Manager which will be installed on systems such as the SPROG that implement a command station interface (the ability to send an arbitrary NMRA DCC packet). This version of the Consist Manager uses an NMRA Consist Control packet to create the consist instead of the Operations Mode Programming request used in the previous Generic Consist Manager. This will allow writing the consist address on decoders that support Operations Mode Programming, but do not allow operations mode programming of CV19 (Certain Lenz decoders fall into this category).
Kevin Dickerson made the following updates:
- Fixed an inconsistency issue relating to the saving of preferences in DP3 depending upon the method that it was closed
- Update the EasyDCC interface so that it would be picked up correctly on the DP3 status screen
- Updated the Layout Block Routing Protocol, so that when block traffic flow is updated, this is reflected in the routing table
- Added the ability to delete Signal Mast logic from the Signaling Pairs window
Georgio Terdida fixed a bug that may occur when loading an XnTcp adapter.
Paul Bender fixed the port number display for network connection configurations.
Help pages with external links (e.g. full "http:" links) and of types that the JavaHelp browser can't display are now sent to the user's default web browser for display.