Hi Bob,
?
I did managed to test your build.
?
At first I faced an error, which is related to the fact that I rely on dispatcher with my autopilot script (I use transits, turnouts setting form there). The error is :?
2025-05-03T10:49:20,355 ptionhandler.UncaughtExceptionHandler ERROR - Uncaught Exception caught by jmri.util.exceptionhandler.UncaughtExceptionHandler [AWT-EventQueue-0]
java.lang.NullPointerException: Cannot invoke "jmri.jmrit.dispatcher.DispatcherFrame.requestAllocation(jmri.jmrit.dispatcher.ActiveTrain, jmri.Section, int, int, boolean, jmri.util.JmriJFrame, boolean)" because "this.mDispatcher" is null
?
So I was not able to create an active train and in my configuration that prevents me from using my autopilot script. What I did to test your build was to create a simpler script that sends alternate speeds commands with some random time between command to 3 trains running at the same time.
?
First things first I used this script under current production release (5.10) and I quickly reproduced the problem of this topic. I then ran the same configuration on your provided build and after a much longer time running I didn't face any issue. Which is great.
?
I don't know then if the error I met with the dispatcher is a regression on your version or my implementation that needs to be upgraded.
?
Anyway seems we are moving forward many thanks.