Passenger train stopping at beginning of platform

[AdvancedApproach]

Bumping this thread as I'm having difficulties controlling the stopping trains at <kuid2:500749:211406:3> Platform 200m h76 1g s

 

[AdvancedApproach]

I made a video going the opposite direction to see if this was a one off but clearly it's not.

 

[stagecoach]

It looks as if the triggers have too large a radius.

 

[AdvancedApproach]

It looks as if the triggers have too large a radius.

Can you reduce its radius in the configuration file?

 

[AdvancedApproach]

attached-trigger
{
trigger_track_1_ende1
{
att "a.trig1a"
radius 5
track "track_1"
}

trigger_track_1_fill1
{
att "a.trig1b"
radius 42.5
track "track_1"
}

trigger_track_1_mitte
{
att "a.trig1c"
radius 5
track "track_1"
}

trigger_track_1_fill2
{
att "a.trig1d"
radius 42.5
track "track_1"
}

trigger_track_1_ende2
{
att "a.trig1e"
radius 5
track "track_1"
}
}

The triggers with 42.5 is a bit excessive in my opinion so perhaps reducing it to 20 might work wonders.

 

[p-dehnert]

The only triggers used to stop the train are probably _end1, _middle and _end2. The _fill1 and _fill2 triggers are used to handle the loading and unloading of all the cars that are not at a stop trigger. The _fill triggers need the large radius to fill the remaining space between the stop triggers. The different trigger types are managed by the script.

Peter

 

[AdvancedApproach]

Die einzigen Trigger, die zum Anhalten des Zuges verwendet werden, sind wahrscheinlich _ende1, _mitte und _ende2. Die Trigger _fill1 und _fill2 werden verwendet, um das Be- und Entladen aller Waggons zu handhaben, die nicht an einem Haltetrigger stehen. Die _fill-Trigger benötigen den großen Radius, um den verbleibenden Raum zwischen den Haltetriggern zu füllen. Die verschiedenen Triggertypen werden vom Skript verwaltet.

Peter

Actually, that's not true. I reduced them to 20 and while the train still overshot the platform it was only by a marginal distance. This is before my modifications:

 

[AdvancedApproach]

This is the after:

 

[p-dehnert]

These stations could be configured for 3 stopping positions, which are shown by a marker in surveyor.

- Center -- the middle of the train stops at the center of the station
- A end -- if the train enters from the A end, the last vehicle (locomotive or car) stops at the A end
           if the train enters from the B end, the first vehicle stops at the A end
- B end -- if the train enters from the B end, the last vehicle stops at the B end
           if the train enters from A end, the first vehicle stops at the B end

The breaking force for the AI mode must be sufficient to stop the train within the area of the active trigger. Usually the center (Y=0) of the triggering vehicle is positioned in the trigger area. When using the end triggers, this could leave part of the first/last vehicle outside the platform area.

Peter

 

[AdvancedApproach]

I tried reducing the radius to 10 but that caused AI drivers to blow right past so 20 meters will have to make due.

 

[pcas1986]

I tried reducing the radius to 10 but that caused AI drivers to blow right past so 20 meters will have to make due.

Have you tried reducing the speed limit for the station area?

 

[AdvancedApproach]

Have you tried reducing the speed limit for the station area?

Yes but it still just breezed right on past. Perhaps N3V Games has a minimum radius for passenger platforms. I dropped it from 50 to 20 km/h. I was TrainzDE, who created the asset allowed me to use imperial measurements instead but oh well.

 

[stagecoach]

The only triggers used to stop the train are probably _end1, _middle and _end2. The _fill1 and _fill2 triggers are used to handle the loading and unloading of all the cars that are not at a stop trigger. The _fill triggers need the large radius to fill the remaining space between the stop triggers. The different trigger types are managed by the script.

Peter

The problem is the middle triggers extend over the end triggers so the train sees the middle ones first and ignores the end ones.

 

[p-dehnert]

The trigger areas don't overlap, they just touch each other.

Trigger | Position(X) | Area(X)
_ende1        95m        100m to   90m
_fill1      47.5m         90m to    5m
_mitte         0m          5m to   -5m
_fill2     -47.5m         -5m to  -90m
_ende2       -95m        -90m to -100m

The visible platform could be extended, using one of the matching splines created by TrainzDE (example: <kuid2:500749:221002:2> Platform #2 h76 w4). Searching for "Author = TrainzDE" and "esk" in the top right search field will show more addons for these stations.

Peter

 

[boleyd]

Isn't this something the vendor should acknowledge and repair?
I see the same issue and have chosen to live with it until fixed by N3V..

 

[JCitron]

Isn't this something the vendor should acknowledge and repair?
I see the same issue and have chosen to live with it until fixed by N3V..

This is a content creator problem not N3V's