Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Portal manager rules give orders through some standard portal interface to the portals to emit trains and traps messages from the surveyed portals to catch outgoing train composition. You can have on a route several portals manager only if each portal manager manages a separate set of portals.
Yes it is the designed behavior. This behavior is needed to be compatible with normal session save/restore process. Input/output queues are located in a global library (Quick Portal stack manager library ) which saves/restores the queues in trainz global context at each startup and when leaving trainz.Code:It appears that once a train is in an input/output queue, it will stay there even if emitted by the receiving portal. I also have queues from my original tests, even though I deleted the rule from that route and all the saved sessions, and no currently managed portal uses those queues. Is this correct behavior?
When you rerun a session from a previously saved session, local session data is restored but not the global input/output queue stack. So to be able to rerun a session, input queues are not emptied when read, but the session component in charge of reading the input queue remembers in the session data what it has already read from the queue so that in case of a later save/restore it skips the already read data from the queue. Output processing is also designed to be save/restore compatible as it stacks inside the session data all the queue data from the begining of the session and during save processing will first clear the queue and rewrite all the queue data from the begining of the session.
Doing the things this way, you should be able to save/restore a session with output/input queue and rerun the same scenario with the same data sent to the queue and read from the queue.
The counterpart is that used data remains in global quick portal stack library even if it is no longer used and to enable to clear this remaining data, under trainz global option menu you will see an entry for the global quick portal stack library where you have some links to clear manualy the no longer used queues. Sorry I forget to give this information in the documentation, I will make a documentation update this weekend about this option.
Hope this explains better how the queues work with session save/restore.
Have a nice day.
Pierre.