Notice to all visitors and members of the Train-Sim.Com message forums: If you plan on using a signature banner in your posts, we would like to remind you that there is a maximum size for banners. That maximum is 450 pixels wide by 120 pixels high, and not to exceed 25k. Your compliance is appreciated. FORUM RULES Problems? There are two common reasons for problems with logging in and posting messages. The first is that you are running a firewall that prevents your messages from being sent to the server. The other is that you have cookies disabled; the DCForum software requires cookies to work properly.
I have transfered this from the MSTS forum as I am told it should be put in here. I know from reading in the forum and my own experience that the "Waiting Point" in setting up paths does not work, although I put 3 or 4 in the path of an AI train to halt at a station and to slow down as it reaches the end of a siding, but what file is this info stored in? All I can find is an entry in the path file increasing the number of "TrPathNodes" which are always the same number. David
I'm not sure you should answer your own question but the answer might help someone else !! I have been experimenting with the waiting point in path editor and I have found that if you go into "Editor and Tools" and put say 10 waiting points in the path where you want the AI train to wait and then go into the "path" file and rewrite the first waiting point numbers into the next 9 the train will stay in one position for the whole time. This may be useful to some folk, but I guess the "Experts" have mentioned this before. David
David it has been discussed before but maybe you have fallen on a different way to get waiting points to work.I myself have put many waiting points together in a line on a path that I want an AI to hold at for say running on dark territory like the Blackfoot Sub route. Might have to look at what you found and Thank you for moving it here.Just Rollin Down The Tracks Dale
This is interesting. I just tried it and it worked quite well. The AI train seemed to wait for x+1 seconds, where x is the number of 'stacked' wait points. This is based on using 4 and 8 wait points. For the first try (4), I used David's method of placing some sequential ones, then editing the .PAT file to copy the TrackPDP entries to be the same for all points. For the 8, I added more TrackPDP entries and TrPathNode entries (and incremented the TrPathNodes count), and resequenced the TrPathNode entries. It wasn't that bad, since I only added four, and the only point after the wait points was the end point (simple short test activity), but I wouldn't recommend this method for any real paths. What might work well would be a utility that could open a path, ask you how long to wait at a wait point, and then insert the additional wait points as requested. I might write such a thing if we can get some more independent verification of this behavior.
