horacefithers
New member
Tried setting up a session sand box - meh...
I thought that before I tried setting up sessions on a 100 mile route I should test out my knowledge of session building.
Either session building is really confusing, or I'm trying to do something that's impossible in Trainz, or I'm clueless...
_s___s_ _s____s_
PORTAL-A___z__TM-B__z__S_/_s___s_\_S__z__TM-C__z__S_/_s____s_\_S__s__TM-D__z__PORTAL-E
s - single head signal
z - single head signal for both directions
S - double head signal
The idea:
1) Single track mainline
2) Bidirectional trains
3) Passing sidings to allow opposing trains to pass each other
4) Portals (Portal Basic) at each end source and consume trains
5) Signals are non-permissive from the Searchlight Signal 0x family.
Each train sourced from Portal A has the following commands:
Each train sourced from Portal E has the following commands:
In practice:
I did not:
I take it I'm completely off in the weeds with this setup.
Or, I read somewhere on the forum that people are having portal problems, but I've no idea what those problems were.
I've watched the N3V youtube video for Portals, but it only using traffic in a single direction and therefor isn't a complete example of what I'd like to do.
I've watched the demos on rudysmodelrailway YouTube channel to see how he made signals operate. Again, this was a uni-directional situation. Also, he was pre-assigned siding or main at each station
Does train require a double track mainline for AI trains to pass each other in opposite directions?
Enquiring minds need to know...
Horace (more confused/frustrated than ever) Fithers
I thought that before I tried setting up sessions on a 100 mile route I should test out my knowledge of session building.
Either session building is really confusing, or I'm trying to do something that's impossible in Trainz, or I'm clueless...
_s___s_ _s____s_
PORTAL-A___z__TM-B__z__S_/_s___s_\_S__z__TM-C__z__S_/_s____s_\_S__s__TM-D__z__PORTAL-E
s - single head signal
z - single head signal for both directions
S - double head signal
The idea:
1) Single track mainline
2) Bidirectional trains
3) Passing sidings to allow opposing trains to pass each other
4) Portals (Portal Basic) at each end source and consume trains
5) Signals are non-permissive from the Searchlight Signal 0x family.
Each train sourced from Portal A has the following commands:
- Navigate to trackmark TM-B
- Navigate to trackmark TM-C
- Navigate to trackmark TM-D
- Navigate to PORTAL-E
Each train sourced from Portal E has the following commands:
- navigate to trackmark TM-D
- Navigate to trackmark TM-C
- Navigate to trackmark TM-B
- Navigate to PORTAL-A
In practice:
- the first train generated says it is unable to navigate to its first track mark.
- all other trains reverse themselves after traveling about 1/2 the length of the portal, then delete themselves.
I did not:
- make the sidings directional, because I want trains in either direction to be able to hold the main or take the siding (prototype practice would be to assign main or siding usage depending on the situation - in TT&TO right, class, and direction determine which train takes the siding)
- put the trackmarks on the siding(s) or corresponding main track(s), because I did not want to force the usage or siding or main for an AI train in advance of the train reaching the siding in question.
I take it I'm completely off in the weeds with this setup.
Or, I read somewhere on the forum that people are having portal problems, but I've no idea what those problems were.
I've watched the N3V youtube video for Portals, but it only using traffic in a single direction and therefor isn't a complete example of what I'd like to do.
I've watched the demos on rudysmodelrailway YouTube channel to see how he made signals operate. Again, this was a uni-directional situation. Also, he was pre-assigned siding or main at each station
Does train require a double track mainline for AI trains to pass each other in opposite directions?
Enquiring minds need to know...
Horace (more confused/frustrated than ever) Fithers