LAST EDITED ON Jan-23-04 AT 02:42 PM (EST)
I hope the warning below has already been shared in this forum. At any rate, I hope that I describe it altogether clearly (the multitude of variations that TS throws at us causes me to easily become confused!).Many paths that you have created yourself for a given route are updated/modified/revised automatically on an ongoing basis by the AE (EEK!!!) when an editing session of yours in the AE meets the following conditions:1-a) Open the AE for a fresh session in that route, or
1-b) Open an activity (afresh) in that route; and2) Create a (new) path; and (lastly)3) Save your AE editing session.The paths being automatically updated on the ongoing basis needn't be associated to the activity where those editing-session conditions have occurred. As far as I've seen, the PDP and track-node (quote-unquote) numeric data are updated (freaky!!), in addition to the versions ("Serial" line) of the paths themselves. I'd like to post a comparison between a couple of versions of a path that I created myself sometime soon for all of you to see.As far as I can tell, the reason this updating happens is because no hard change had been committed to the activity file itself (e.g., any service removed from the traffic pattern, any service inserted to the traffic pattern, etc. {the activity file contains many details of the associated traffic pattern}). It's as though an ongoing path-editor clipboard is created and thereafter maintained just as soon as the conditions have been met. I'm not certain which of your own paths get swept up into this 'clipboard', but it seems to me to be the following ones:
- all paths associated to the activity that had been updated prior to the AE editing session wherein the conditions occurred; and
- any path you create after having met the conditions.An example of how those conditions can be met is when you create a dummy path (say, within a dummy service) for the purpose(s) of testing, save it, and then immediately save your AE editing session to embed the newly-created path into your route right away. Another way could be that you cancelled out of your AE editing session and start a fresh AE session. The latter example is probably the scenario that's more likely to occur.I'm convinced that this happened to the manufacturers too. If you open up the path that has the filename aftstrmtraffic.pat that was packaged into the MSTS1 activity After The Storm found in the route folder USA1, you'll see that it has a Serial value of 28; this proves MS' whim at selling us their wares from the testing/pilot stage of their overall project. If you mimick this very path by creating it from scratch yourself, you can see that it's 'numeric data' vastly differs from those to your own creation.From now on, I'm going to back up paths I create just as soon as I create them. I wouldn't be surprised if many of you were to discover that paths that you edited only once, i.e., created (period!), now have a serial value higher than 1.I stumbled upon this in my quest to solve the mystery surrounding junctionless path points, which I bounced off somebody in the following message:http://www.train-sim.com/dcforum/DCForumID7/1988.html#aftstrmtrafficFeel free if you'd like me to clarify, I could ramble on and on here . . .Cheers,
goonybirdhttp://www.geocities.com/BourbonStreet/Bayou/4804/ a fictitious network serving London, Weymouth, and points in between
Printer-friendly page | Edit | Reply | Reply With Quote | Top
RE: PITFALL: Path Editor: I hope this warning isn't t, buttercup, Jan-23-04, 03:36 PM, (1) RE: PITFALL: Path Editor: I hope this warning isn't t, goonybird, Jan-23-04, 04:43 PM, (2) RE: PITFALL: Path Editor: I hope this warning isn't t, goonybird, Jan-24-04, 04:05 PM, (4) RE: PITFALL: Path Editor: I hope this warning isn't t, kevarc, Jun-21-04, 09:29 PM, (7) RE: PITFALL: Path Editor: I hope this warning isn't t, goonybird, Jun-21-04, 06:27 PM, (5) RE: PITFALL: Path Editor: I hope this warning isn't t, kevarc, Jun-21-04, 09:26 PM, (6) RE: PITFALL: Path Editor: I hope this warning isn't t, goonybird, Jun-22-04, 01:22 AM, (10) RE: PITFALL: Path Editor: I hope this warning isn't t, kevarc, Jun-22-04, 08:26 AM, (11) RE: PITFALL: Path Editor: I hope this warning isn't t, goonybird, Jun-22-04, 10:43 AM, (12) RE: PITFALL: Path Editor: I hope this warning isn't t, goonybird, Jan-23-04, 10:17 PM, (3) RE: PITFALL: Path Editor: I hope this warning isn't t, kevarc, Jun-21-04, 09:34 PM, (8) RE: PITFALL: Path Editor: I hope this warning isn't t, goonybird, Jun-22-04, 00:49 AM, (9)
Conferences | Topics | Previous Topic | Next Topic