AI driver can strand itself before signalling-only station

Bug #419525 reported by Paul Sladen
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bve-route-cross-city-south (Ubuntu)
Medium
Unassigned
openbve (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: openbve

When running the 'HighDetail_323_Summer_2002_0931_Rain_Overcast.csv' diagram of the Cross City-South route under the built-in AI (no plugins), the AI now gets stuck approximately 2.5 metres before "Station 4" (a signalling-only (non-station) point after Northfield).

The AI stops outside the allowed "station" tolerance and so the train does not "arrive", the signal ahead does not clear, and the AI does not attempt to make any further progress (to approach) closer to the signal. (Found in ~1.2.1.1 onwards with the tweaks to the red-light advance whilst in station code).

This should be reproducible by starting up the Class 323 (without plugins) on the XCS route diagram (and others);

    * loading the route
    * jumping to Northfield station and,
    * then engaging the AI.

The train proceed for a minute and will then stop "in the middle of nowhere", shortly before the virtual station "Station 7" and refuse to move any further. If

    * the AI is disengaged,
    * the train manually advanced ~5 metres and,
    * the AI re-engaged

then the signal will have cleared and the train will proceed normally.

Ideally the AI should not completely strand itself.

Revision history for this message
Paul Sladen (sladen) wrote :
Changed in openbve (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Paul Sladen (sladen) wrote :

Work around from Openbve upstream in 1.2.1.3 (an AI driven train is always deemed to have arrived).

Changed in openbve (Ubuntu):
status: Confirmed → In Progress
Revision history for this message
Paul Sladen (sladen) wrote :

Marker "stations" are sometimes only used to control the signalling system and do not need to be stopped at for passenger boarding/alighting. In the XCS route these appear to be incorrectly marked---the following tweak being required across all signalling-only "stations":

  -11375, .Wall 3;1;11, .Sta ;;09.4300;;-1;1;;;1;0;;11,
  +11375, .Wall 3;1;11, .Sta ;P;09.4300;0;-1;1;;;1;0;;11,

as based on the requirements defined in:

  http://mackoy.cool.ne.jp/make/ryfile.html
  http://openbve.trainsimcentral.co.uk/develop/route_csv.html#track_stations

The 'P' denotes to *pass* without stopping, and the extra '0' means to not sound an alarm that the "station" was passed without stopping.

This means that the player will no longer be penalised by having their score reduced for not having stopped and also means that an AI train will no longer slow down more than necessary whilst passing the signalling trigger.

Changed in bve-route-cross-city-south (Ubuntu):
importance: Undecided → Medium
status: New → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package bve-route-cross-city-south - 1.31.04-0ubuntu1

---------------
bve-route-cross-city-south (1.31.04-0ubuntu1) lucid; urgency=low

  * New upstream release, fixes (LP: #419525)
  * debian/rules: fix oggenc quality parameter
  * debian/rules: comment out oggenc stage as openbve=1.2.4.1 uses
    a home-grown .wav only sound loader.
 -- Paul Sladen <email address hidden> Wed, 6 Jan 2009 04:30:00 +0100

Changed in bve-route-cross-city-south (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package openbve - 1.2.4.1-0ubuntu1

---------------
openbve (1.2.4.1-0ubuntu1) lucid; urgency=low

  * New upstream stable version (1.2.4.1) (LP: #444934)
    fixes (LP: #419523) (LP: #419525) (LP: #419530) (LP: #444462)
  * changelog.html: update (1.2.3.3)
 -- Paul Sladen <email address hidden> Wed, 6 Jan 2010 07:58:00 +0000

Changed in openbve (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers