Steve,

When setting up a template sometimes you can add 2 events for the same siding or conflicting events or when adjusting consists locations shift it onto another track in the yard. This causes AG to generate a siding location say "3" and the actual consist shows up on "5".

  The way MSTS event window handles viewing events is a lot of work. Is there a way of extracting a list of the events for a route showing all the properties other than opening each event and right click properties when debugging a problem?

Thanks,

Peter

After doing many templates, I fully understand your dilemma.  Every issue which you mention, plus others, has happened at one time or another.  The real problem lies in the MSTS AE, not in AG.  I do not believe that AG can help in any way whatsoever, although the SWLACT file will contain some, but not all, of this information.

In order to keep track of things, I routinely record each and every pick up event, by hand.  For some larger routes, this can be hundreds of pick up events.  AE's limit is about 75.  After that, it chokes and dies.  Consequently, not all events can be resident in the template activity, which might mean that an event must be added again in order to fix something.

I record all details about the event at the time I put the pick up event into AE.  I can think of no way for AG to help with this, but maybe Steve has a suggestion???

Norman,

I too also do what you do as far as events, I no the problem is with MSTS AE not with AG . The reason for the question was to see if anyone had a work around program or method to extract a list of the events as you know MSTS does not do a friendly job managing items like this. 

Thanks for your feed back.

Peter 

Peter,

Adding more than one pickup event won't hurt anything, it's ok.  But adding a pickup event on one track and then accidentally moving the consist to another track will cause problems as you noted -- it will call for pickups from the wrong track.

I REALLY hate having to add these Action Events.  I have tried very hard to figure out how to avoid these but so far haven't figured it out.  Perhaps I can write a program for Microsoft Train Simulator X or Kuju Rail Simulator that won't require this nonsense.  Or I'll figure out the math of how to equate tile and position information to the actual siding, which I have been unable to do.

There may be some sort of utility I could write that will check to confirm that every time a car is said to be located on a certain siding in the CSV file, it actually is there in the .act file. 

Thanks,

Steve