Please be on the lookout for errors and unexpected behaviour in this release as there have been many significant program changes, particularly in the timetable functions. I have tested them extensively but it is impossible to test exhaustively, so there may well be new bugs lurking in the undergrowth. Please send me any error files that are generated and let me know of any oddities during use, and I’ll try to make corrections as soon as possible – thanks.
New features:
1. Perhaps the main upgrade here is the addition of a 64 bit Windows version (thanks are due to Krizar here as I hadn’t realised the free Embarcadero compiler was capable of 64 bit compilation). This will (or should) work exactly the same as the existing 32 bit version but if your computer runs 64 bit Windows then you should use the 64 bit version. The 32 bit version should only be used if your Windows version is 32 bits but Windows computers shipped over the last several years have 64 bit Windows. To find out look at this article: https://support.microsoft.com/en-us/windows/32-bit-and-64-bit-windows-frequently-asked-questions-c6ca9541-8dce-4d48-0415-94a3faa2e13d
The 64 bit version will be more future-proof as 32 bit programs are now regarded as legacy software, and although as far as I know there is no intention yet to stop supoporting them that time will come eventually.
In order to avoid ambiguity the program names have been changed from railway.exe to RailOS32.exe and RailOS64.exe. Each release package also comes with a number of .dll and .bpl files, and although some of them have the same names in each release they are different files so please do not get them mixed up or the program won’t work.
Additionally the 64 bit version should be more compatible with non-Windows operating systems. MAC computers in particular have dropped support for 32 bit programs in their later operating systems.
2. Routes can now be truncated from the start as well as from the end. After left clicking the ‘Cancel or truncate a route’ button right click the track element immediately in advance of a facing signal and it will truncate from the start. Also when an automatic signal (blue) route is truncated or cancelled the signals at each end now attach to any existing route that precedes or follows it.
3. The timetable editor now includes the ability to invert a timetable entry to make construction of return journeys easier (this was added at v2.14.0 Supplement 1).
4. The timetable editor now allows more options for new services ‘Sns’ and ‘Sfs’. These can be followed immediately by ‘Fjo’ – finish and join another service, and ‘Frh’ – finish and remain here. These options make it easier to simulate drop off and pick up of wagons and empty coaching stock. Note that these changes can only be used with program versions from 2.15.0.
5. The timetable now includes the ability to change a service description when stopped at a location. A new command ‘dsc’ is available, e.g. 13:25;dsc;Birmingham Snow Hill to London Marylebone. Again this new addition can only be used with program versions from 2.15.0.
6. The floating train information window now includes speeds in mph as well as km/h.
7. Split trains can now vary the mass and power distribution as a fourth element in the split event in the timetable – e.g. 09:25;rsp;2F25;20-30. In this case the mass of the train that splits off will have 20% of the train mass, and 30% of the train power prior to the split. Mass can vary between 1% and 99%, and power between 0% and 100%. If there is no fourth element then the split is 50% for both mass and power as before. Note that these percentages relate to the current mass and power of the train, not its original mass and power.
8. The ability to stop the left hand side warning icons from flashing has been added by a new button below the icons that toggles the flash function.
Bugs and behavioural changes:
1. After a discussion on Discord about brake rates on 23 & 24/01/23 I realised that halving the brake rate for each train after a split was wrong. The brake rate should stay the same so the performance stays the same. To correct that the brake force for each train is now halved, as are power and mass.
2. A bug was corrected as a result of an error reported by BWJM on 10/02/23 where there were two linked continuations with no signal between and trains entering and leaving every minute. The error occurred when the program tried to calculate the delay times to reset the signal immediately before the continuation first to double yellow, then yellow and then green. In this case the program couldn’t find a signal so it threw an error. It was easily fixed – there was no need for an error at all – if it can’t find a signal then it just breaks out of the calculation. Thanks to BWJM for reporting this error.
3. Another bug was uncovered by BWJM, reported on 18/02/23, where a train that was joined at a later time by some empty wagons (represented as a train with no power) had its maximum speed set immediately to the empty wagons’ maximum speed. This was a silly error on my part. When the timetable was first compiled internally and Fjos and jbos were married together, the speed of the jbo train was set to the Fjo train’s speed if it was lower than the jbo’s train. I can only explain it by assuming I had overlooked the fact that this should only occur when the join took place, not when the timetable was compiled. In fact the speeds are set properly anyway when the join takes place so that part wasn’t in error. The fix couldn’t have been easier – I just deleted the speed change. Thanks again to BWJM for reporting this error.
4. FinsburyPark reported an error on 15/03/23, in that when a session with failed points and TSRs was stopped the 10km/h speed limits remained. This was an oversight on my part – I had removed the failure graphic but forgot to reset the speed limit. This has now been corrected. Thanks to FinsburyPark for reporting this error.
Download it here