How to Use Portals
m |
(→Configuring an Enhanced Portal: Added new section covering the UDS) |
||
Line 461: | Line 461: | ||
*'''<kuid2:61392:5011:45>''' - correct at the time this document was written | *'''<kuid2:61392:5011:45>''' - correct at the time this document was written | ||
− | |||
− | |||
− | |||
<table width="100%"> | <table width="100%"> | ||
<tr valign="top"> | <tr valign="top"> | ||
Line 469: | Line 466: | ||
</tr> | </tr> | ||
</table> | </table> | ||
+ | |||
+ | ='''Portals and the UDS (Unified Driver Surveyor) Interface'''= | ||
+ | |||
+ | The '''UDS''' is an option for rapid switching, in both directions, between '''Driver''' and '''Surveyor'''. It is available in '''TRS19 Platinum Edition''' and '''Trainz Plus''' only. The '''UDS''' does not affect the operation of portals but it has revealed one previously unnoticed property of portals.<br> | ||
+ | |||
+ | A train that is driven into a portal and later returned to the layout will be returned in the same layer as the portal and not in the trains originally assigned layer. Trains that are produced by a portal will be assigned to the same layer as the portal. This has <span style="background-color: yellow; font-weight: 700;"> possibly always been the case with portals </span> but was probably unnoticed until the arrival of the '''UDS'''. It seems to have no other noticeable effect on trains.<br> | ||
+ | |||
+ | This could become an issue if you make the switch from '''Driver''' to '''Surveyor''' after a train has been '''returned''' to the layout from a portal. For example, if a train is originally in a '''Session Layer''' then it is part of a '''Session'''. If it is returned from a portal then it will now be in a '''Route Layer''' and will be part of the '''Route'''. If you then switch from '''Driver''' to '''Surveyor''' and save the '''Route''' then the train will be saved in the '''Route''' not in the '''Session'''. If this is an issue then the remedy is to open the property dialogue window of any wagon in the train after it has left the portal and change its assigned layer to the correct one. This will set all vehicles in that train to the same correct layer. | ||
+ | <br> | ||
+ | |||
---- | ---- | ||
---- | ---- |
Revision as of 08:24, 2 July 2021
The information in this Wiki Page applies to TANE, TRS19 and Trainz Plus.
Contents |
What is a Portal?
Portals are track objects that can add and remove trains during the running of a Session |
|
The quickest way to find all the train producing and consuming portals in the Surveyor Object Tool window is to set up a search filter. This will sort the portals you want from all the objects named "portal" such as tunnel portals.
|
|
Configuring a Basic Portal
Open the properties window of a portal in the route.
|
Produce Trains
|
|
Construct a Consist
|
Add a Saved Consist
If you have already saved your consists in Trainz using the Trainz Tool then those consists can be quickly and easily added to the portal consist list.
|
Add a Driver
|
For information on adding driver commands see the Trainz Wiki Page at:- |
Consume Trains
To remove trains from the Session
|
For "dead end" portals (those that have no exit) the Accept all trains option is the option that should be used |
Consume Only Specific Trains
After selecting the option Accept trains matching specific criteria a new set of controls will appear
|
An example:-
|
Return Consumed Trains
To return consumed trains back into the Session
|
|
A train that has been returned after entering a portal will return to the Session with any remaining driver commands still in its Driver Schedule. It will then immediately start obeying those commands. |
If the driver command that sent a train to the consuming portal was the final command in its schedule, then it will emerge from the portal with an empty Driver Schedule. It will come to a halt immediately after leaving the portal. |
Configuring an Enhanced Portal
There are a number of portals available on the DLS that have additional features or capabilities that are not found in the basic portals built into Trainz. There are also Session Rules available on the DLS that will give additional features or capabilities to the basic portals.
Quick Portal Manager Standard Edition Rule (SP2 and later)
This is a Session Rule, by pguy, that manages the portals and adds flexible timetables to their operations. It is available on the DLS.
- <kuid2:61392:5011:45> - correct at the time this document was written
Portals and the UDS (Unified Driver Surveyor) Interface
The UDS is an option for rapid switching, in both directions, between Driver and Surveyor. It is available in TRS19 Platinum Edition and Trainz Plus only. The UDS does not affect the operation of portals but it has revealed one previously unnoticed property of portals.
A train that is driven into a portal and later returned to the layout will be returned in the same layer as the portal and not in the trains originally assigned layer. Trains that are produced by a portal will be assigned to the same layer as the portal. This has possibly always been the case with portals but was probably unnoticed until the arrival of the UDS. It seems to have no other noticeable effect on trains.
This could become an issue if you make the switch from Driver to Surveyor after a train has been returned to the layout from a portal. For example, if a train is originally in a Session Layer then it is part of a Session. If it is returned from a portal then it will now be in a Route Layer and will be part of the Route. If you then switch from Driver to Surveyor and save the Route then the train will be saved in the Route not in the Session. If this is an issue then the remedy is to open the property dialogue window of any wagon in the train after it has left the portal and change its assigned layer to the correct one. This will set all vehicles in that train to the same correct layer.
Trainz Wiki
More Tutorials and Guides to Using Trainz |
This page was created by Trainz user pware in July 2018 and was last updated as shown below.