Looky1173
commented
1 year ago Imported from https://bugs.launchpad.net/or/+bug/1222657/comments/1
| Property | Value |
|---|---|
| Posted by | Gerry (gerry-s-u) |
| Date posted | Mon, 09 Sep 2013 06:13:20 GMT |
Closed Looky1173 closed 1 year ago
Looky1173
commented
1 year ago | Property | Value |
|---|---|
| Posted by | Gerry (gerry-s-u) |
| Date posted | Mon, 09 Sep 2013 06:13:20 GMT |
Looky1173
commented
1 year ago | Property | Value |
|---|---|
| Posted by | Peter Gulyas (pzgulyas) |
| Date posted | Mon, 09 Sep 2013 08:37:26 GMT |
Please attach log files unzipped next time.
Looky1173
commented
1 year ago | Property | Value |
|---|---|
| Posted by | cjakeman (cjakeman) |
| Date posted | Sun, 15 Sep 2013 19:18:20 GMT |
Hi Gerry,
Wondered if this was due to changes I made in v1720 and 1721, but your log file disproves that comprehensively.
Would you mind helping me pin it down a bit further by trying the attached versions of RunActivity which I've extracted from the SVN repository? I've uploaded these executables to https://dl.dropboxusercontent.com/u/31895483/Open%20Rails/2013-09-16.zip
Please report here which, if any, fail and upload the log file.
Thanks,
Chris
Looky1173
commented
1 year ago | Property | Value |
|---|---|
| Posted by | David C. Jones (dcjones2) |
| Date posted | Sun, 13 Oct 2013 20:37:49 GMT |
Dear Ross,
Thank you for this message. I am still not sure how the bug system operates, so please forgive me if I send this to you, in this format It is an attempt to make a modest contribution to the fixing of my own bugs - but for the benefit of others also. I really do wish to be a resource for you all and not just a damned nuisance. Thanks for your tolerance. Thanks also for your hard work in helping us.
After receiving some information on the various versions of the Open Rails, I attempted to run the following on Open Rails X1716 (Debug) - latest I had - and using the RailDriver.
[First Class Simulations]...
London South Coast West Coast Express Cross City
The latter two routes (sub-routes?) were connected (by a special small program download) and run together as "WEST COAST MAINLINE - Part 1 (With Cross City)".
All of the activities passed the OR testing OK, when run from the main OR (matrix) contents page.
Many of the activities ran OK. However, some did not. Among those which did not run properly, they all seemed to come up with the first picture, of the stationary view of the train. However, on pressing the "RailDriver - Run/Stop" key, the screen went completely blank in white colour. There was absolutely NOTHING on the screen, so one needed to resort to "Task Manager" from the keyboard. Then, when attempting to use "Task Manager" (from the Keyboard) I received - sometimes momentarily - a screen such as the one that I have attached to this message. (Doc2.docx (255 KB))
The activities which did this were:
London South Coast: 01 Down Brighton Express; 03 Arun Valley Inspection; 04 Unit Substitution; (then I gave up - because it looked as if many would be faulty!) WEST COAST MAINLINE - Part 1 (With Cross City): WC01 London to Birmingham Express; WC08 Sunday Service; CC01 Reddich - New Street; CC02 Longbridge - Litchfield TV; CC03 New Street - Litchfield TV ; CC04 Cross Country Diversion; CC05 New Street - Reddich ; CC09 Narnt Green - New Street; CC10 Fast to Reddich; CC13 Cross Country - Cheltenham; CC15 Longbridge - New Street;
Respectfully, I offer this as a contribution to solving the problem with these routes,
Sincerely,
David Jones
-----Original Message-----
From: James Ross
Sent: Sunday, October 13, 2013 7:57 AM
To:
** Summary changed:
** Tags added: crash
-- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1222657
Title: System.ArgumentOutOfRangeException at ORTS.MSTSNotchController.SetRDPercent (X.1744, RailDriver Interface not working)
Status in Open Rails Tracker: Triaged
Bug description: RailDriver interface does not engage while running specific activities. Occurs on different routes, will run route in explore and most activities. Problem did not exist prior to and including Vx1720. Three logs attached documenting two different routes. Also documents route/act running with Vx1720 but failing with Vx1744 using the RailDriver interface.
To manage notifications about this bug go to: https://bugs.launchpad.net/or/+bug/1222657/+subscriptions
Looky1173
commented
1 year ago | Property | Value |
|---|---|
| Posted by | David C. Jones (dcjones2) |
| Date posted | Sun, 13 Oct 2013 20:44:22 GMT |
London South Coast 03: Arun Valley Inspection - did not respond to controls at all - did not react to the Raildriver Run/Stop Key! Sorry to exclude last time.
-----Original Message----- From: David C. Jones Sent: Sunday, October 13, 2013 4:37 PM To: Bug 1222657 ; James Ross Cc: Peter Gulyas Subject: Re: [Bug 1222657] Re: System.ArgumentOutOfRangeException atORTS.MSTSNotchController.SetRDPercent (X.1744,RailDriver Interface not working)
Dear Ross,
Thank you for this message. I am still not sure how the bug system operates, so please forgive me if I send this to you, in this format It is an attempt to make a modest contribution to the fixing of my own bugs - but for the benefit of others also. I really do wish to be a resource for you all and not just a damned nuisance. Thanks for your tolerance. Thanks also for your hard work in helping us.
After receiving some information on the various versions of the Open Rails, I attempted to run the following on Open Rails X1716 (Debug) - latest I had - and using the RailDriver.
[First Class Simulations]...
London South Coast West Coast Express Cross City
The latter two routes (sub-routes?) were connected (by a special small program download) and run together as "WEST COAST MAINLINE - Part 1 (With Cross City)".
All of the activities passed the OR testing OK, when run from the main OR (matrix) contents page.
Many of the activities ran OK. However, some did not. Among those which did not run properly, they all seemed to come up with the first picture, of the stationary view of the train. However, on pressing the "RailDriver - Run/Stop" key, the screen went completely blank in white colour. There was absolutely NOTHING on the screen, so one needed to resort to "Task Manager" from the keyboard. Then, when attempting to use "Task Manager" (from the Keyboard) I received - sometimes momentarily - a screen such as the one that I have attached to this message. (Doc2.docx (255 KB))
The activities which did this were:
London South Coast: 01 Down Brighton Express; 03 Arun Valley Inspection; 04 Unit Substitution; (then I gave up - because it looked as if many would be faulty!) WEST COAST MAINLINE - Part 1 (With Cross City): WC01 London to Birmingham Express; WC08 Sunday Service; CC01 Reddich - New Street; CC02 Longbridge - Litchfield TV; CC03 New Street - Litchfield TV ; CC04 Cross Country Diversion; CC05 New Street - Reddich ; CC09 Narnt Green - New Street; CC10 Fast to Reddich; CC13 Cross Country - Cheltenham; CC15 Longbridge - New Street;
Respectfully, I offer this as a contribution to solving the problem with these routes,
Sincerely,
David Jones
-----Original Message-----
From: James Ross
Sent: Sunday, October 13, 2013 7:57 AM
To:
** Summary changed:
** Tags added: crash
-- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1222657
Title: System.ArgumentOutOfRangeException at ORTS.MSTSNotchController.SetRDPercent (X.1744, RailDriver Interface not working)
Status in Open Rails Tracker: Triaged
Bug description: RailDriver interface does not engage while running specific activities. Occurs on different routes, will run route in explore and most activities. Problem did not exist prior to and including Vx1720. Three logs attached documenting two different routes. Also documents route/act running with Vx1720 but failing with Vx1744 using the RailDriver interface.
To manage notifications about this bug go to: https://bugs.launchpad.net/or/+bug/1222657/+subscriptions
Looky1173
commented
1 year ago | Property | Value |
|---|---|
| Posted by | Bill Currey (wjcurrey) |
| Date posted | Fri, 25 Oct 2013 02:24:58 GMT |
David, You need to try a version newer then X.1774. There were changes for RialDriver in X.1775 and X.1777. These changes may or may not correct your problems. But before preceding on trouble shooting have to have a newer version of OR running. If the problems continue then will need to start looking at the .eng files for the routes that are not working.
You can get the latest experimental version of OR at: http://www.openrails.org/experimental.html . Looking down the page there is an entry for X.1819 - 18-Oct-2013 for current week. Under that is the zip file to download: Executable binaries - OR_X.zip .
Bill
Looky1173
commented
1 year ago | Property | Value |
|---|---|
| Posted by | David C. Jones (dcjones2) |
| Date posted | Fri, 25 Oct 2013 22:58:42 GMT |
Dear Bill,
Thank you for keeping me up to date with the latest information.
I tried out the routes - in X.1819 - but with the same result, for the one or two I tested - a completely blank screen, when I presssed the "Raildriver/Run-Stop" button on the Raildriver.
This was after bringing up a good picture of the train, after starting the system in X.1819 - 18-Oct-2013.
Sorry to be a nuisance.
David
----- Original Message -----
From: "Bill Currey"
David, You need to try a version newer then X.1774. There were changes for RialDriver in X.1775 and X.1777. These changes may or may not correct your problems. But before preceding on trouble shooting have to have a newer version of OR running. If the problems continue then will need to start looking at the .eng files for the routes that are not working.
You can get the latest experimental version of OR at: http://www.openrails.org/experimental.html . Looking down the page there is an entry for X.1819 - 18-Oct-2013 for current week. Under that is the zip file to download: Executable binaries - OR_X.zip .
Bill
-- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1222657
Title: System.ArgumentOutOfRangeException at ORTS.MSTSNotchController.SetRDPercent (X.1744, RailDriver Interface not working)
Status in Open Rails Tracker: Triaged
Bug description: RailDriver interface does not engage while running specific activities. Occurs on different routes, will run route in explore and most activities. Problem did not exist prior to and including Vx1720. Three logs attached documenting two different routes. Also documents route/act running with Vx1720 but failing with Vx1744 using the RailDriver interface.
To manage notifications about this bug go to: https://bugs.launchpad.net/or/+bug/1222657/+subscriptions
Looky1173
commented
1 year ago | Property | Value |
|---|---|
| Posted by | Bill Currey (wjcurrey) |
| Date posted | Thu, 31 Oct 2013 01:55:05 GMT |
David, I will need to look at the .eng file for the route you are having problems with.
You can find the .eng file where you have MSTS directory installed such as C:\Program Files\Microsoft Games\Train Simulator... or something similar. Depends where you have installed MSTS.
There should be a folder TRAINS\TRAINSET , in the TRAINSET folder there are listed different locomotives such as GP38, DASH9, etc. Locate the engine that you are using; for example in the GP38 folder there is a gp38.eng file ; that is the type of file that is needed.
It would also be helpful along with the attached .eng file , if the OpenRailsLog.txt file was included. This is normally saved on the desktop.
If the 3rd party route is from Making Tracks, I may be able to get the route from an OR developer.
Bill
On Fri, Oct 25, 2013 at 3:58 PM, David C. Jones
Dear Bill,
Thank you for keeping me up to date with the latest information.
I tried out the routes - in X.1819 - but with the same result, for the one or two I tested - a completely blank screen, when I presssed the "Raildriver/Run-Stop" button on the Raildriver.
This was after bringing up a good picture of the train, after starting the system in X.1819 - 18-Oct-2013.
Sorry to be a nuisance.
David
----- Original Message ----- From: "Bill Currey"
To: Sent: Thursday, October 24, 2013 10:24 PM Subject: [Bug 1222657] Re: System.ArgumentOutOfRangeException atORTS.MSTSNotchController.SetRDPercent (X.1744,RailDriver Interface not working) David, You need to try a version newer then X.1774. There were changes for RialDriver in X.1775 and X.1777. These changes may or may not correct your problems. But before preceding on trouble shooting have to have a newer version of OR running. If the problems continue then will need to start looking at the .eng files for the routes that are not working.
You can get the latest experimental version of OR at: http://www.openrails.org/experimental.html . Looking down the page there is an entry for X.1819 - 18-Oct-2013 for current week. Under that is the zip file to download: Executable binaries - OR_X.zip .
Bill
-- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1222657
Title: System.ArgumentOutOfRangeException at ORTS.MSTSNotchController.SetRDPercent (X.1744, RailDriver Interface not working)
Status in Open Rails Tracker: Triaged
Bug description: RailDriver interface does not engage while running specific activities. Occurs on different routes, will run route in explore and most activities. Problem did not exist prior to and including Vx1720. Three logs attached documenting two different routes. Also documents route/act running with Vx1720 but failing with Vx1744 using the RailDriver interface.
To manage notifications about this bug go to: https://bugs.launchpad.net/or/+bug/1222657/+subscriptions
-- You received this bug notification because you are subscribed to Open Rails. Matching subscriptions: BillC https://bugs.launchpad.net/bugs/1222657
Title: System.ArgumentOutOfRangeException at ORTS.MSTSNotchController.SetRDPercent (X.1744, RailDriver Interface not working)
Status in Open Rails Tracker: Triaged
Bug description: RailDriver interface does not engage while running specific activities. Occurs on different routes, will run route in explore and most activities. Problem did not exist prior to and including Vx1720. Three logs attached documenting two different routes. Also documents route/act running with Vx1720 but failing with Vx1744 using the RailDriver interface.
To manage notifications about this bug go to: https://bugs.launchpad.net/or/+bug/1222657/+subscriptions
Looky1173
commented
1 year ago | Property | Value |
|---|---|
| Posted by | David C. Jones (dcjones2) |
| Date posted | Thu, 31 Oct 2013 23:24:15 GMT |
Dear Bill,
Thank you for continuing to try to help me to fix this bug. I really appreciate your kindness and patience.
From the computer where my trains are stored, I have tried to send you what you have requested. I hope it is OK - but let me know if it is wrong, or if you need anything else. I look forward to hearing from you.
One hint that might be useful is shown here, as an earlier fix for my Paddingtoon to Penzance. Here it is, from the Atomic forum: a.. Reply with quote b.. Report this post Re: Routes In Open Rails by slipperman12 on 26 Aug 2013 09:44
Hi David & Mike, Fortunately, it appears that most of the WORLD files are not compressed in this route!
If you open up file w-006281+014867.w (in the WORLD folder) using NotePad, or any other suitable editor, at the very end of it you'll see :
Static ( UiD ( 11 ) FileName ( ""Bracket 180.s"" ) StaticFlags ( 00004000 ) Position ( 485.924 23.6064 848.528 ) QDirection ( 0 0 0 1 ) VDbId ( 0 ) ) )
If you change the FileName line to read : FileName ( "Bracket 180.s" ) then resave the file (make sure it saves in Unicode format), it will start OK in OpenRails. NOTE : the route still starts OK in MSTS with this change!
I haven't checked any further World files, so there may be others which require similar treatment!
Cheers, Ged
----- Original Message -----
From: "Bill Currey"
David, I will need to look at the .eng file for the route you are having problems with.
You can find the .eng file where you have MSTS directory installed such as C:\Program Files\Microsoft Games\Train Simulator... or something similar. Depends where you have installed MSTS.
There should be a folder TRAINS\TRAINSET , in the TRAINSET folder there are listed different locomotives such as GP38, DASH9, etc. Locate the engine that you are using; for example in the GP38 folder there is a gp38.eng file ; that is the type of file that is needed.
It would also be helpful along with the attached .eng file , if the OpenRailsLog.txt file was included. This is normally saved on the desktop.
If the 3rd party route is from Making Tracks, I may be able to get the route from an OR developer.
Bill
On Fri, Oct 25, 2013 at 3:58 PM, David C. Jones
Dear Bill,
Thank you for keeping me up to date with the latest information.
I tried out the routes - in X.1819 - but with the same result, for the one or two I tested - a completely blank screen, when I presssed the "Raildriver/Run-Stop" button on the Raildriver.
This was after bringing up a good picture of the train, after starting the system in X.1819 - 18-Oct-2013.
Sorry to be a nuisance.
David
----- Original Message ----- From: "Bill Currey"
To: Sent: Thursday, October 24, 2013 10:24 PM Subject: [Bug 1222657] Re: System.ArgumentOutOfRangeException atORTS.MSTSNotchController.SetRDPercent (X.1744,RailDriver Interface not working) David, You need to try a version newer then X.1774. There were changes for RialDriver in X.1775 and X.1777. These changes may or may not correct your problems. But before preceding on trouble shooting have to have a newer version of OR running. If the problems continue then will need to start looking at the .eng files for the routes that are not working.
You can get the latest experimental version of OR at: http://www.openrails.org/experimental.html . Looking down the page there is an entry for X.1819 - 18-Oct-2013 for current week. Under that is the zip file to download: Executable binaries - OR_X.zip .
Bill
-- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1222657
Title: System.ArgumentOutOfRangeException at ORTS.MSTSNotchController.SetRDPercent (X.1744, RailDriver Interface not working)
Status in Open Rails Tracker: Triaged
Bug description: RailDriver interface does not engage while running specific activities. Occurs on different routes, will run route in explore and most activities. Problem did not exist prior to and including Vx1720. Three logs attached documenting two different routes. Also documents route/act running with Vx1720 but failing with Vx1744 using the RailDriver interface.
To manage notifications about this bug go to: https://bugs.launchpad.net/or/+bug/1222657/+subscriptions
-- You received this bug notification because you are subscribed to Open Rails. Matching subscriptions: BillC https://bugs.launchpad.net/bugs/1222657
Title: System.ArgumentOutOfRangeException at ORTS.MSTSNotchController.SetRDPercent (X.1744, RailDriver Interface not working)
Status in Open Rails Tracker: Triaged
Bug description: RailDriver interface does not engage while running specific activities. Occurs on different routes, will run route in explore and most activities. Problem did not exist prior to and including Vx1720. Three logs attached documenting two different routes. Also documents route/act running with Vx1720 but failing with Vx1744 using the RailDriver interface.
To manage notifications about this bug go to: https://bugs.launchpad.net/or/+bug/1222657/+subscriptions
-- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1222657
Title: System.ArgumentOutOfRangeException at ORTS.MSTSNotchController.SetRDPercent (X.1744, RailDriver Interface not working)
Status in Open Rails Tracker: Triaged
Bug description: RailDriver interface does not engage while running specific activities. Occurs on different routes, will run route in explore and most activities. Problem did not exist prior to and including Vx1720. Three logs attached documenting two different routes. Also documents route/act running with Vx1720 but failing with Vx1744 using the RailDriver interface.
To manage notifications about this bug go to: https://bugs.launchpad.net/or/+bug/1222657/+subscriptions
Looky1173
commented
1 year ago | Property | Value |
|---|---|
| Posted by | David C. Jones (dcjones2) |
| Date posted | Thu, 31 Oct 2013 23:30:40 GMT |
Dear Bill,
The earlier message contained an irrelevant attachment, sorry. Here it is removed. Sorry to mess you around!
Thank you for continuing to try to help me to fix this bug. I really appreciate your kindness and patience.
From the computer where my trains are stored, I have tried to send you what you have requested. I hope it is OK - but let me know if it is wrong, or if you need anything else. I look forward to hearing from you.
One hint that might be useful is shown here, as an earlier fix for my Paddingtoon to Penzance. Here it is, from the Atomic forum: a.. Reply with quote b.. Report this post Re: Routes In Open Rails by slipperman12 on 26 Aug 2013 09:44
Hi David & Mike, Fortunately, it appears that most of the WORLD files are not compressed in this route!
If you open up file w-006281+014867.w (in the WORLD folder) using NotePad, or any other suitable editor, at the very end of it you'll see :
Static ( UiD ( 11 ) FileName ( ""Bracket 180.s"" ) StaticFlags ( 00004000 ) Position ( 485.924 23.6064 848.528 ) QDirection ( 0 0 0 1 ) VDbId ( 0 ) ) )
If you change the FileName line to read : FileName ( "Bracket 180.s" ) then resave the file (make sure it saves in Unicode format), it will start OK in OpenRails. NOTE : the route still starts OK in MSTS with this change!
I haven't checked any further World files, so there may be others which require similar treatment!
Cheers, Ged
----- Original Message ----- From: "Bill Currey"
To: Sent: Wednesday, October 30, 2013 9:55 PM Subject: Re: [Bug 1222657] Re: System.ArgumentOutOfRangeExceptionatORTS.MSTSNotchController.SetRDPercent (X.1744,RailDriver Interface not working) David, I will need to look at the .eng file for the route you are having problems with.
You can find the .eng file where you have MSTS directory installed such as C:\Program Files\Microsoft Games\Train Simulator... or something similar. Depends where you have installed MSTS.
There should be a folder TRAINS\TRAINSET , in the TRAINSET folder there are listed different locomotives such as GP38, DASH9, etc. Locate the engine that you are using; for example in the GP38 folder there is a gp38.eng file ; that is the type of file that is needed.
It would also be helpful along with the attached .eng file , if the OpenRailsLog.txt file was included. This is normally saved on the desktop.
If the 3rd party route is from Making Tracks, I may be able to get the route from an OR developer.
Bill
On Fri, Oct 25, 2013 at 3:58 PM, David C. Jones
wrote: Dear Bill,
Thank you for keeping me up to date with the latest information.
I tried out the routes - in X.1819 - but with the same result, for the one or two I tested - a completely blank screen, when I presssed the "Raildriver/Run-Stop" button on the Raildriver.
This was after bringing up a good picture of the train, after starting the system in X.1819 - 18-Oct-2013.
Sorry to be a nuisance.
David
----- Original Message ----- From: "Bill Currey"
To: Sent: Thursday, October 24, 2013 10:24 PM Subject: [Bug 1222657] Re: System.ArgumentOutOfRangeException atORTS.MSTSNotchController.SetRDPercent (X.1744,RailDriver Interface not working) David, You need to try a version newer then X.1774. There were changes for RialDriver in X.1775 and X.1777. These changes may or may not correct your problems. But before preceding on trouble shooting have to have a newer version of OR running. If the problems continue then will need to start looking at the .eng files for the routes that are not working.
You can get the latest experimental version of OR at: http://www.openrails.org/experimental.html . Looking down the page there is an entry for X.1819 - 18-Oct-2013 for current week. Under that is the zip file to download: Executable binaries - OR_X.zip .
Bill
-- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1222657
Title: System.ArgumentOutOfRangeException at ORTS.MSTSNotchController.SetRDPercent (X.1744, RailDriver Interface not working)
Status in Open Rails Tracker: Triaged
Bug description: RailDriver interface does not engage while running specific activities. Occurs on different routes, will run route in explore and most activities. Problem did not exist prior to and including Vx1720. Three logs attached documenting two different routes. Also documents route/act running with Vx1720 but failing with Vx1744 using the RailDriver interface.
To manage notifications about this bug go to: https://bugs.launchpad.net/or/+bug/1222657/+subscriptions
-- You received this bug notification because you are subscribed to Open Rails. Matching subscriptions: BillC https://bugs.launchpad.net/bugs/1222657
Title: System.ArgumentOutOfRangeException at ORTS.MSTSNotchController.SetRDPercent (X.1744, RailDriver Interface not working)
Status in Open Rails Tracker: Triaged
Bug description: RailDriver interface does not engage while running specific activities. Occurs on different routes, will run route in explore and most activities. Problem did not exist prior to and including Vx1720. Three logs attached documenting two different routes. Also documents route/act running with Vx1720 but failing with Vx1744 using the RailDriver interface.
To manage notifications about this bug go to: https://bugs.launchpad.net/or/+bug/1222657/+subscriptions
-- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1222657
Title: System.ArgumentOutOfRangeException at ORTS.MSTSNotchController.SetRDPercent (X.1744, RailDriver Interface not working)
Status in Open Rails Tracker: Triaged
Bug description: RailDriver interface does not engage while running specific activities. Occurs on different routes, will run route in explore and most activities. Problem did not exist prior to and including Vx1720. Three logs attached documenting two different routes. Also documents route/act running with Vx1720 but failing with Vx1744 using the RailDriver interface.
To manage notifications about this bug go to: https://bugs.launchpad.net/or/+bug/1222657/+subscriptions
Looky1173
commented
1 year ago | Property | Value |
|---|---|
| Posted by | Bill Currey (wjcurrey) |
| Date posted | Tue, 05 Nov 2013 19:05:18 GMT |
Found failure mode on MSTS standard route Route: Tokyo - Hakone Actvity: Shinjuku to Machida in the Winder Locomotive: Series 7000 LSE Additional note: Locomotive fails on explore route
This engine is similar to the one being used by David Jones
Looky1173
commented
1 year ago | Property | Value |
|---|---|
| Posted by | Bill Currey (wjcurrey) |
| Date posted | Tue, 24 Dec 2013 22:43:36 GMT |
Fix committed X1898 - Fix for RailDriver bug# 1222657 dupe 1225576 exception when RD engaged. Does not correct problems 7000 locomotive combo brake problem bug# 1226592, 1160292
Imported from https://bugs.launchpad.net/bugs/1222657
RailDriver interface does not engage while running specific activities. Occurs on different routes, will run route in explore and most activities. Problem did not exist prior to and including Vx1720. Three logs attached documenting two different routes. Also documents route/act running with Vx1720 but failing with Vx1744 using the RailDriver interface.