Version 2.8 - Revision history

Oxalin at 18:31, 26 August 2022

2022-08-26T18:31:12Z

Krizar: Krizar moved page Version 2.8.0 to Version 2.8 without leaving a redirect

2022-08-25T21:10:39Z

Krizar moved page Version 2.8.0 to Version 2.8 without leaving a redirect

Krizar at 21:10, 25 August 2022

2022-08-25T21:10:29Z

Oxalin at 16:47, 21 August 2022

2022-08-21T16:47:49Z

Krizar at 18:05, 19 May 2021

2021-05-19T18:05:16Z

Krizar: Created page with "From Railway Operation Simulator Wiki Jump to navigationJump to search Version 2.8.0 of the railway.exe program was released on the 18th of May, 2021. Changelog: * After se..."

2021-05-19T18:05:03Z

Created page with "From Railway Operation Simulator Wiki Jump to navigationJump to search Version 2.8.0 of the railway.exe program was released on the 18th of May, 2021. Changelog: * After se..."

New page

From Railway Operation Simulator Wiki
Jump to navigationJump to search

Version 2.8.0 of the railway.exe program was released on the 18th of May, 2021.

Changelog:

* After selecting an area of railway in track build mode the track elements now become visible so that the selected area can more easily be filled with a particular element.

* If an area of railway was cut and moved and then cancelled, it used to be pasted in the new position which wasn’t appropriate, so now it’s pasted back in its original position.

* It was found that if a route was set for a call-on into a platform where there was already a train, and that train changed direction, the route was cancelled. It happened because of an earlier change that cancelled stub routes ahead of a train when it changed direction and the excess route beyond the train was no longer wanted, but the route direction wasn’t checked so any route was cancelled. Now the route direction is checked and only routes leading away from the train are cancelled.

* It was found that a route could be set across a level crossing that had only just begun to close to trains if the route setting was done very quickly. The final signal before the crossing stayed at red so trains would be protected but the route was present and shouldn’t have been. The program check routine has now been modified to include routes that are in course of being set in addition to routes already set.

← Older revision		Revision as of 18:31, 26 August 2022
Line 8:		Line 8:
	* It was found that a route could be set across a level crossing that had only just begun to close to trains if the route setting was done very quickly. The final signal before the crossing stayed at red so trains would be protected but the route was present and shouldn’t have been. The program check routine has now been modified to include routes that are in course of being set in addition to routes already set.		* It was found that a route could be set across a level crossing that had only just begun to close to trains if the route setting was done very quickly. The final signal before the crossing stayed at red so trains would be protected but the route was present and shouldn’t have been. The program check routine has now been modified to include routes that are in course of being set in addition to routes already set.
	}}		}}
−
−	~~[[Category:Program Versions]]~~

← Older revision		Revision as of 16:47, 21 August 2022
Line 10:		Line 10:

	* It was found that a route could be set across a level crossing that had only just begun to close to trains if the route setting was done very quickly. The final signal before the crossing stayed at red so trains would be protected but the route was present and shouldn’t have been. The program check routine has now been modified to include routes that are in course of being set in addition to routes already set.		* It was found that a route could be set across a level crossing that had only just begun to close to trains if the route setting was done very quickly. The final signal before the crossing stayed at red so trains would be protected but the route was present and shouldn’t have been. The program check routine has now been modified to include routes that are in course of being set in addition to routes already set.
		+
		+	[[Category:Program Versions]]

← Older revision		Revision as of 18:05, 19 May 2021
Line 1:		Line 1:
−	~~From Railway Operation Simulator Wiki~~
−	~~Jump to navigationJump to search~~
−
	Version 2.8.0 of the railway.exe program was released on the 18th of May, 2021.		Version 2.8.0 of the railway.exe program was released on the 18th of May, 2021.

@@ Line 1: / Line 1: @@
-Version 2.8.0 of the railway.exe program was released on the 18th of May, 2021.
+{{Program Version
+| patch=0
-Changelog:
+| release_date=2021-05-18
+| changes=&#32;
 * After selecting an area of railway in track build mode the track elements now become visible so that the selected area can more easily be filled with a particular element.
 * If an area of railway was cut and moved and then cancelled, it used to be pasted in the new position which wasn’t appropriate, so now it’s pasted back in its original position.
 * It was found that if a route was set for a call-on into a platform where there was already a train, and that train changed direction, the route was cancelled. It happened because of an earlier change that cancelled stub routes ahead of a train when it changed direction and the excess route beyond the train was no longer wanted, but the route direction wasn’t checked so any route was cancelled. Now the route direction is checked and only routes leading away from the train are cancelled.
 * It was found that a route could be set across a level crossing that had only just begun to close to trains if the route setting was done very quickly. The final signal before the crossing stayed at red so trains would be protected but the route was present and shouldn’t have been. The program check routine has now been modified to include routes that are in course of being set in addition to routes already set.
 [[Category:Program Versions]]