Is there a limit on the number of commands in a session?

[narrowgauge]

I ask the question because I have two multi command sessions that used to work OK in TRS2004, but in TS12 they both reach a point where a trackmark is ignored and all control is lost. The same trackmarks work well with local testing. I set up an ABCD shuttle as A to C to D to B to A and repeat, where B and C are the trouble spots. This worked without a problem.

If ther is a limit, is it possible to 'chain' shorter sessions together?

Peter

 

[glbotu]

I think it depends on the RAM of your computer. Are you running a large number of trains as well, or just the one. Also, some combination of content sometimes screws with the commands. I've had these sorts of issues occasionally. Have you tried waiting a while? Sometimes what happens is that you tell a train to drive to a station and it doesn't go until the entire line to that station is clear. (This is in TS2010 mind you, things may be different in 12)

 

[narrowgauge]

Thanks, glbotu

I have answered my own question, I savagely reduced the number of commands in the session and still the loco sailed past the track marker.

This session loco is the only one in steam at the time, it is the only session running and the consist is only one loco and three traincars. I set up the same small train local to the problem station. I have reduced the trigger radius to .10m in case there is interference with other trigger, no change.

Too late tonight, I will try more when I am fresh in the morning. I'll try two markers in tandem and see what happens.

Peter

 

[fran1]

Have you moved or replaced the track mark and renamed it exactly the same, if so replace the command in the schedule. Sometimes they're looking for the old TM.
Otherwise the I stands for idiot again.
With regard to the amount of commands I'm using the schedule library at the moment with drive via A B C D for eg and the schedule is named outer.
In the schedule the last command is copy commands from schedule outer so there is a max of 5 commands at one time.
By creating more library schedules you could link them together.

 

[colourlight]

My Library has schedules with 20 or more commands which works fine. The only problm I found was usng the "Copy Command" and "repeat" in the same schedule. When the Copy Command has been used by the AI it must be removed to prevent it being used again.

 

[celje]

The only problm I found was usng the "Copy Command" and "repeat" in the same schedule. When the Copy Command has been used by the AI it must be removed to prevent it being used again.

colourlight

You have not correct setting, see
Can a List of Commands be Created?

 

[celje]

reach a point where a trackmark is ignored and all control is lost.
If ther is a limit, is it possible to 'chain' shorter sessions together?
Peter

Hello narrowgauge

No, there is no limit. If Fran's suggestion don't work (Have you moved or replaced the track mark and renamed it exactly the same, if so replace the command in the schedule) then the cure not exist. About 'chain' see the thread above for colourlight.

regards
celje

 

[Kennilworth]

Hi Narrowgauge

I wonder if this is similar to a problem that I am having with the SCS2006 rule on a small route in TS2010. An oil train is programmed to run between a refinery and an airport with the commands set to repeat after the first run. Everything works fine on the first circuit but after that the train ignores the trackmark and goes on its way out of control. I've tried everything I can think of but so far nothing has worked. A passenger train running on a large circuit on the same route calls at two stations and then repeats. Again all works fine on the first circuit but it doesn't seem to be able to see the trackmark on the second circuit.

The only thing I can think of is that it's the fact that it's a relatively small circuit of about 12 miles that's causing the problems.

I have a much larger and longer route which involves Merry-Go-Round trains running between a coal mine and a power station and this works just fine and will repeat for ever more. It has me baffled.

Regards

Brian

 

[narrowgauge]

I have replaced the trackmark and it was renamed correctly. That made no difference. Th problem occurs at a station on a 2way single line track. There are two trackmarks one at the up end and one at the down. The commands are simple and repeat all the way to the station. Just "navigate to Trackmark" + "Wait 10 seconds" repeated about 15 times over the full length. The problem occurs after about 10 stations, prior to that all the commands have worked. Obviously after it misses that on trackmark it is out of control.

I have tried rotating the trackmark, made no difference.

As it is a sightseeing session there is only one set of commands in use and only one train.

Peter

 

[narrowgauge]

I have run the session again, even speeded up it takes time, and as before, it ignored the trackmark at the station and drove straight through. I cleared the now useless 'navigate to' command and the 'wait' command, and the train continued on and stopped at every other station as it was programmed to do.

It is just the one trackmark that gets missed. I will try adding a 'navigate-via' command prior to the station, may be that will have an effect.

I will not let this defeat me!

Peter

 

[glbotu]

Can I recommend you not only delete the Trackmark, but also the track it's on, just whatever's between the 2 spline points. Make sure you give the Trackmark a different name as well - for good measure.

 

[narrowgauge]

I have found the problem, actually there were two.

Originally the trigger radius had been set to 0.0 , don't know why or how but it was. That was my first suspect, and as it turned out, that was the problem. It was made worse by a very simple error.

When we made the route, we used the group KUID for Franklin Prestage, the force behind the building of the prototype. (not real now, he died quite a while back). I continued to use that while I made the changes, not noticing that I was not overwriting the original file which I wanted to do because the sessions are keyed to the original route.

As it turned out, I was busily changing the trigger radius on a route which was then saved under my KUID. When I tested it, I used the original route which was unchanged and the session didn't work. Simple, really.

The solution - TS12 does not like a zero trigger radius, it probably switches the trackmark off.

Thanks everyone for posting.

Peter

 

[thebadtouch]

Kennilworth, I'm curious to find out if the problem narrowgauge identified is the same problem you were having on your TS2010 route.