Can't Make Path Control Work

[FloridaGuy]

Can't Make Path Control Work in TS2009

I started looking into the js-TRF Path Control rule as a possible way to get around problems I was having in getting trains to reliably back into tracks on a yard ladder.

I'm pretty sure I've set up the rule properly thanks to help and suggestions from Trev999 and other posts. I've gotten the automatic names for paths when I save them, and everything looks the way I think it should.

However, whenever my driver gets to the icon that's supposed to invoke the path, the train comes to a screeching halt and the switches are not thrown in the directions called for by the path. After the train stops it's impossible to get it moving again although other trains on the route are unaffected.

I have a signal starting the path and I've tried with and without additional signals in the path but always the same result: it freezes and no switches are set.

I'm obviously missing a key step here or else Path Control doesn't work in TS9.

Can anybody help?

Thanks in advance.

 

[ElStoko]

Command schedule?

What is the Command Schedule for the AI Driver that freezes? Please state the command prior to the Path Control command and what the command after it is, also. Does the Path Control command disappear from the schedule to indicate it has been executed, or does it remain in the schedule at the freeze point? I presume the AI Driver drives to or via a track mark just prior to the execution of the Path Control Command. What is the location of this track mark relative to the start signal listed in the Path Control rule?

 

[FloridaGuy]

Re: Command schedule?

The following Command Schedule for the AI driver is a very simple one I've set up to try to understand Path Control:

Navigate to Trackmark 20
Path Control: set path Yard SW entrance end, don't wait
Autodrive to Yard 4

The train immediately drives to TM 20 and stops. The Path Control command remains. As I said earlier, dragging the PC command out of the sequence does not allow me to regain control.

TM 20 is about 44 feet ahead of start signal "Yard SW entrance" which is about 53 feet ahead of "Junction 3" which turns left onto the yard ladder. The yard tracks branch off to the right on the ladder. Each track is terminated with a bumper and has a Trackmark Yard 1, 2, etc near it's end

The signal is type USA 2 LO2. It shows red on both aspects even though the path command is supposed to set it green. Although this particular configuration does not have signals at each yard track, I've had the identical problem when I've set up dwarfs before and after each yard turnout.

I appreciate your response and hope you can tell me what I'm missing.

Thanks,

Warren

 

[Andyz]

The path-control rule only works with "Autodrive" or similar commands, "Navigate to", or "Navigate to trackmark" commands are ignored by this rule.

Actually you can use this to your advantage, if you want to send a train through your path without it activating the triggers.

Andyz

 

[Andyz]

Oops!

I should have read the post properly, I see you are using "Autodrive".
Did you know that the "k" key will display a pathcontrol console screen, showing the sheduled and running paths?
Also if you are using TRS 2010 dont use the "Quick Drive" method to enter the Driver mode, as this will cause an error in the Path-control Rule.
Always exit to the Routes menu, and select Driver from there.
This is the likely cause of your problem. If the Rule Errors, the path never gets set, and you are waiting for it to get set!
Look for the red dot at the bottom right of your screen.

Andyz

 

[trev999]

The path-control rule only works with "Autodrive" or similar commands, "Navigate to", or "Navigate to trackmark" commands are ignored by this rule.

Andyz

Hi Warren - I was looking for this thread and couldn't find it.

Unfortunately I only have TRS2004 and haven't experienced your problem. Have a look in the Auran\TS1009\JetLog.txt file, that may give some clues.

One thing, though - the Autodrive and Autopilot commands only drive forwards. It can be made to reverse by issuing the "Change Train Direction" command <kuid2:160293:9001:1>.
Normally the train will reverse automatically when you drive to a trackmark behind it so that probably won't help.

Warren, I can only access the internet between 19:00 and 07:00 and it is now 06:50 so don't expect a reply today.

If you'd like to send me an e-mail to trev999@gmail.com I might have something that can solve your problem.

Cheers
Trevor

 

[ElStoko]

Don't control signals

The signal is type USA 2 LO2. It shows red on both aspects even though the path command is supposed to set it green. Although this particular configuration does not have signals at each yard track, I've had the identical problem when I've set up dwarfs before and after each yard turnout.

I believe this is the critical statement: you have instructed Path Control to operate the signal. In my experience, this is a no no. Let the signal automatically respond to the track ahead. I would recommend editing the Path Control module "set path Yard SW entrance end, don't wait" to exclude control of start signal "Yard SW entrance" (and any other signal). This should allow the Path Control command to complete (switch the junctions to the wanted path) and disappear from the Command Schedule. However, if the signal remains red because of a detected obstruction ahead on the set path, then obviously the train will not progress beyond the signal.

 

[FloridaGuy]

Re: Don't Control Signals

In order to set up an instance of the Rule you must identify a starting signal. You then have the options of setting the signal to R, G or Y. You do not have the option of doing nothing. Although G is the aspect I prefer because I want it to go through this signal, I have also tried setting the aspect to R or Y. The result is always the same: the command sequence stops at the Path Control icon and the program freezes. Sometimes only that driver is frozen, other times the program crashes and requires Ctrl Alt Del.

I have also set up simple one board test routes where the only path option is either go straight or turn left, i.e. a single switch. The results are exactly the same.

I am rapidly reaching the conclusion that the Path Control Rule is not supported by TS2009.

Thanks for your suggestion,

Warren

 

[ElStoko]

Oops

My apologies. I was working from memory and had forgotten that I had modified the Path Control Rule script so that the 'Automatic' option offerred to intermediate signals in the path behind the start signal is also offerred to the start signal. It was this edit that permitted me to operate the Path Control Rule in TS2009. If you are bent on using this rule for the development of private sessions (not for release on the DLS or elsewhere), then I could share the edited version with you. Otherwise, why don't you use mutton's Path Rule <kuid2:71155:60006:1>. This definitely works in TS2009. A shortcoming of mutton's Path Rule is that is does not offer the "do not wait" option of brummfondel's Path Control, and so if the driver command to set the path is not immediately executable, the train is stopped (rather than being allowed to move on to the next command) until execution is completed. I have not used atilabarut's Control Path Rule <kuid:131986:158781> and Multi-Path Control-v5 <kuid2:131986:153364:5>, but these could be worth a try.

 

[FloridaGuy]

Re: Oops

Thanks. I'll go after all of them right away and let you know how they work out. Appreciate your help.

Later today: I DL'ed both of Atilabarut's rules and will experiment with them. I also found Mutton's rule already installed on my program so I can try it as well.

Warren

 

[ElStoko]

Oops (again)

I supplied Warren (FloridaGuy) with my edited version of the Path Control rule, and he found that it did not work in TS2009. Here is my e-mail response:

Warren, I tried out a simple test session myself, and find the same script error occurs as you report.
When I was developing sessions for S&C:2009 I was using the Path Control rule extensively in TC3. My recollection was that when I transferred the sessions over to TS2009, the rule didn't work properly until I edited it as per the version I supplied you. I couldn't use it for the S&C:2009 release because I did not have brummfondel's permission for the edit, so I changed over to mutton's Path Rule. At the time rail-sim were developing S&C:2009, Auran were releasing updates to make it run better. There are 2 possibilities: my memory is flawed (more likely), and the edited Path Control never worked in TS2009, or it worked with an earlier version but not with updates that have taken place since then.

The script error that occurs when a Path Control command is executed from an AI Driver's command sequence is:

Thread Exception_ER_NativeCallError,line -1, file pathcontrol_lib.gs

and occurs at line 1071 of pathcontrol_lib.gs:

function $string@PathControl_lib::LibraryCall(string,string[],GSObject);