Paul,
I forgot to mention that this will also affect UK users of the Timetable tool.
Dave Sand
toggle quoted message
Show quoted text
On Dec 12, 2018, at 2:22 PM, Dave Sand <ds@...> wrote:
Paul,
The 4.13.7 test release and the 4.14 production release will use the original values for UK scales. This will eliminate the problem for other UK Dispatcher users who are waiting for the production release.
Since you have already changed, I recommend that you change to a US scale before updating and then change back. Or remember to reset the scale after updating before trying to run trains.
Dave Sand
On Dec 11, 2018, at 6:02 PM, Dave Sand <ds@...> wrote:
Paul,
Thanks for pointing out the scale issue. The Dispatcher stored the British scales as UK-? but referred to them using UK_? I did not catch that when I defined the standard scale list.
Dave Sand
On Dec 11, 2018, at 2:43 PM, paul@... wrote:
This appeared to be fine until I ran an autotrain in dispatcher, when I got multiple null pointer exceptions. The train failed to run as normal and stop at the end. Fortunately I was aware of the 'new standard scale process' and its relevance to the timetable tool and spotted that there are dispatcher changes associated with this too. It seems that if you are using one of the scale settings impacted by this process (e.g. British N) then you need to check your scale settings for both the timetable tool and dispatcher options as a migration step. The scale setting in dispatcher options was cleared. Resetting it fixed the problem.
Regards
Paul