Is there a trigger/rule that will see stationary consists?

[Davie_UCF]

I think I've tried most rules in the past but thought I'd check with the hive mind incase I've missed something.

If you have an ordered list including a trigger check or trackside check which then sets a variable to 1 to show it as occupied the trigger or trackside check only notices a train/consist if it enters/leaves or stops on the trigger.

It doesn't seem to notice if a train is already on the trigger.

What I want is a way of continuously checking if a trigger is occupied.

Any ideas?
Rules ive missed?

 

[stagecoach]

Drive to TM list <kuid2:61392:7004:23> DriveToTrackmarkList v2 (SP2 and later) can check if the TM is occupied and drive to an unoccupied TM in the list.

 

[Davie_UCF]

Drive to TM list <kuid2:61392:7004:23> DriveToTrackmarkList v2 (SP2 and later) can check if the TM is occupied and drive to an unoccupied TM in the list.

Shame those are commands so I can't set variables automatically with them. But it shows the functionality is there, just no rule for it yet

Saying that, maybe I can hide some track somewhere with invisible consists that have commands that check the trackmark and change variables on repeat. It's hacky as hell but it might work.

 

[Davie_UCF]

Shame those are commands so I can't set variables automatically with them. But it shows the functionality is there, just no rule for it yet

Saying that, maybe I can hide some track somewhere with invisible consists that have commands that check the trackmark and change variables on repeat. It's hacky as hell but it might work.

It won't work because it has to be able to drive to said trackmark, can't just check it is occupied, doh'

 

[Davie_UCF]

Actually @stagecoach , I have to thank you as your idea although it doesn't work for me made me think outside the box.

There's a rule that checks if a trackmark is vacant or occupied and jumps to a label. So I have a dummy consist on invisible track somewhere that has a repeating schedule which checks the trackmark and sets a variable if it's occupied or unoccupied.

I did a quick test before I left for work and it seems to work!

 

[Cayden]

Actually @stagecoach , I have to thank you as your idea although it doesn't work for me made me think outside the box.

There's a rule that checks if a trackmark is vacant or occupied and jumps to a label. So I have a dummy consist on invisible track somewhere that has a repeating schedule which checks the trackmark and sets a variable if it's occupied or unoccupied.

I did a quick test before I left for work and it seems to work!

Interested in which rule you are talking about and what you means by “jumps to a label’.

I am not really up to speed on creating sessions so bare with me.

Cayden

 

[Davie_UCF]

Interested in which rule you are talking about and what you means by “jumps to a label’.

I am not really up to speed on creating sessions so bare with me.

Cayden

There's a command on the DLS called 'insert buff label' also, a few different commands that tie with this, such as 'Skip to label' , 'Skip to label if variable x' and 'Skip to label if TM occupied/unoccupied'

Most are made by trev999

So what you can do is have some variables set using the input table rule and then make schedules that can jump to different parts of the schedule according to what variables are set or trackmarks are occupied.

It can be a bit of a mind-f at times. It's like coding but you can only go in a straight line across the commands. It's also really hard to explain, i've opened my route after four years away and trying to understand my own schedules using variables is really hard.

A quick example...
You would have a schedule or list of commands to find a free platform (This is easily done with mission codes now but a good example of basic use of variables).

Skip to label 4 if TM P1 is occupied -- Skip to Label 6 if TM P2 is occupied -- Label 4 -- Set path to P1 -- Autodrive to P1 -- Jump to Label 10 -- Label 6 -- Set path to P2 -- Autodrive to P2 -- Label 10 -- End of commands

It's a basic example. Label 10 is required otherwise it would go through the label 4 commands (to drive to P1) then go straight into label 6, so jump to label 10 ensures it skips over the commands it doesn't need.
Exchange the commands for ones you may use but hopefully it's a simple enough example. Things get really complex!

I really enjoy the mind exercise creating automated sessions gives me, I often hit a wall and then at work, or while in bed at night i'll come up with an idea to make something work using different rules or commands. I find it really rewarding and rarely if ever drive a train in Trainz

 

[Cayden]

There's a command on the DLS called 'insert buff label' ...

Hi Davie,

Thanks for explaining the Insert Buff Label rule. I will have a look at it.

I haven’t may a session in about 10 years, so I am essentially starting back at “square one”. I think my challenge is going to be that my route circa 1880s did not have signals. It was controlled by telegraph and station operators, all “hand and mouth”. However, as the route is an historical recreation, it is only single track. There is passenger and freight through traffic and limited local traffic, e.g., ore to smelter and logging.

The route is essentially finished. I am currently working on filling in the background history but now thinking about operation.

https://doug56.net/CPRMS1880s/

Cayden