Loading/unloading passengers.

[frogpipe]

Here is a diagram of the station.

<<===X*============================
------@@@@@@@@@@@@@@@@@@@------
>>===X=========================*===

@ = Platform
>> or << direction of train
Equals sign is the track

X = Where it stops as of TS12SP1HF3
* = Where is used to stop in TS12

AI is commanded to go to track 2 (top in this diagram), load, then track 1 (there's a reversing stub on to the left) load, then to a track mark, and repeat. The track mark is very far away from the station, so it goes to the closer common track, reverses, and goes to the next platform.

Pre and post SP1 and all the "Hot Fixes" it stopped as the locomotive reached the far end of the platform, now only the right to left movement does this.

When approaching from the left of this diagram, and moving toward the right, the locomotive stops right as it reaches the platform, leaving all the coaches out on the tracks were the passengers couldn't really board the train.

It can't be the asset, as it's the same asset.

 

[frogpipe]

So...... am I the ONLY one experiencing this?

 

[shaneturner12]

Can I verify that you are using the Load or Terminate Passenger Train command for trains in both directions? If you are, I'd like to know which stations you are using.

Shane

 

[Scottbe8]

It's possible that in SP1, Trainz pays more attention to the direction in which track is laid when handling driver commands. This messes up a potential majority of sessions where track-laying direction was previously not a factor.

 

[JamesMoody]

When approaching from the left of this diagram, and moving toward the right, the locomotive stops right as it reaches the platform, leaving all the coaches out on the tracks were the passengers couldn't really board the train.

Please ensure that you are using a 'load' command for the second stop. If you omit this command, the train will stop at the point it first encounters the platform, rather than in a sensible location to load passengers.

Can you also confirm exactly when you think this behaviour changed? From your message I think you are indicating it was between Hotfix 2 and Hotfix 3 -- am I correct on this point?

Does the train stop in the correct location in the lower platform if it hasn't previously called at the upper platform?

 

[JamesMoody]

It's possible that in SP1, Trainz pays more attention to the direction in which track is laid when handling driver commands.

Definitely not going to be that. This has been a long-standing false rumour throughout the community. The direction of a track only affects the default direction of trackside objects when first placed in surveyor. It has no effect in driver.

 

[frogpipe]

Can I verify that you are using the Load or Terminate Passenger Train command for trains in both directions? If you are, I'd like to know which stations you are using.

Shane

I use Load, I never use terminate passenger train (I don't know what it for, and assume it's for when the train is supposed to stop and go no further)

I'll check on which station it is.

Please ensure that you are using a 'load' command for the second stop. If you omit this command, the train will stop at the point it first encounters the platform, rather than in a sensible location to load passengers.*

Can you also confirm exactly when you think this behaviour changed? From your message I think you are indicating it was between Hotfix 2 and Hotfix 3 -- am I correct on this point?**

Does the train stop in the correct location in the lower platform if it hasn't previously called at the upper platform?***

* I am using a load command.

** Behavior changed between SP1 and HF3 - I know it was right before SP1, and I know I noticed it wrong with HF3 - I don't know if it was working like this post SP1, HF1 or HF2.

*** Don't know, but I can try that.

 

[frogpipe]

Station is:

Stn MN Brewster <171456:100107:2>

---

I also tried moving it to the "left" side and having it approach the lower platform first - I gave it the "goto Track 2, Load, Goto Holding Point, goto Track 1, Load, repeat" commands - whereupon it ran as expected and stopped at the proper locations.

Go figure....

(PS: You'll note that there is a "Goto Track 1, load, goto track 2, load" in that sequence. The two track converge at both ends of the platform, but there are direction markers on the platform tracks, and the junction ahead when sitting on track 1 is much closer then the junction behind resulting in the train pulling forward, then reversing to get to Track 2.)

 

[TrainzDev]

Behavior changed between SP1 and HF3 - I know it was right before SP1, and I know I noticed it wrong with HF3 - I don't know if it was working like this post SP1, HF1 or HF2.

OK, so last build you know it was OK was 49922, and you then went straight to 58414?

Station is:

Stn MN Brewster <171456:100107:2>

OK, so that means that it could be an issue with the change in asset -- it's a builtin station, and 49922 has <KUID:171456:100107:1>, not <KUID:171456:100107:2>. I can't see anything obvious that would cause this, but it's important to note the asset *has* changed.

I also tried moving it to the "left" side and having it approach the lower platform first - I gave it the "goto Track 2, Load, Goto Holding Point, goto Track 1, Load, repeat" commands - whereupon it ran as expected and stopped at the proper locations.

OK, so it's not a general purpose problem, it's something specific to this specific case on this specific platform.

 

[frogpipe]

I made incremental updates between 49922 and 58414 as they were released, but I didn't execute these commands during that time because I was spending my time route building.