Autopilot mode
#51
Posted 01 December 2014 - 09:10 AM
I have been trying other routes and activities, and I have found that the strange brake pressure behavior is linked to the case where the player train, running under Autopilot, is required to stop and wait at a red signal near the start of the activity. If I click out of Autopilot and back in, the brake pressures (even for the case of just a pair of locos) vanish.
If there is no red signal wait, then everything runs beautifully!
Cheers,
Sid.
#52
Posted 01 December 2014 - 11:10 PM
thank you. I believe I have already solved the problem. However I'm braking my head with the problem of starting in player driven mode. I believed it was a simple thing, but it has consequences on the waiting point management. I hope I will solve this.
Referring to explore mode, no, it is not foreseen. It is however possible to generate a temporary activity with Train Store and run it in autopilot mode as if it were a run in explore mode.
#53
Posted 02 December 2014 - 05:59 AM
is it possible please to enable the Autopilot to stop closer to signals ?
As per my screenie it would be good to see it pull up about half the distance, roughly by the first clump of grass. :furiousPC:
http://i409.photobucket.com/albums/pp177/GeorgeJacksonChurchward/OpenRails2014-12-0201-44-52.png
#54
Posted 02 December 2014 - 07:53 AM
Loco was moving when i saved the activity, when i resumed the handbrake was applied.
Only way i could release it was by taking manual control and then resuming Autopilot.
Logfile attached.
#55
Posted 02 December 2014 - 09:36 AM
Csantucci, on 01 December 2014 - 11:10 PM, said:
Hi Carlo-
I found a temporary fix to the startup problem - if I click ESC (Pause) immediately when OR starts, I can switch out of Autopilot and reduce the throttle to zero in Pause mode before hitting ESC again; then I only have to apply the brakes to regain control.
Cheers,
Sid
#56
Posted 02 December 2014 - 01:37 PM
Updates:
- game now starts in player driven mode; to switch to autopilot press Alt-A as usual;
- signals now correctly shown in cab;
- brakes now showing correctly, at least single-pipe ones. Maybe vacuum ones still have a problem;
- passing directly to manual mode when in autopilot mode now blocked as it should; a warning message is displayed;
- when passing to autopilot the reverser is set in the correct position; so, even if the player left it in the wrong position, OR corrects this;
- saves and resumes now OK also when train stopped at signal because of waiting point.
To Dogbert: it's difficult to see what happened: now I have uploaded a debug version, so also the line numbers in the OpenRailsLog.txt file should be shown.
Train stopping nearer to signal: train now stops at the distance set by OR for AI trains. I know it is a quite high distance. This has been done so to avoid SPADs with AI trains. I also would like to reduce such value. Maybe later I will do some check.
#57
Posted 02 December 2014 - 02:20 PM
No worries in regards stopping distance thanks Carlo.
In regards the Log.txt, i don't really understand much of it.
I have been trying to fix the faulty MEP dmu's that are always reported, for months. :censored2:
#58
Posted 02 December 2014 - 08:15 PM
New start up looks great.
Cheers,
Sid
#59
Posted 03 December 2014 - 12:17 AM
If no major problems or objections arise, I foresee to commit autopilot mode in the mainstream OR within the next 48 hours.
Dogbert,
what is the problem of the faulty MEP DMU's? Do you have a link for the problem report?
#60
Posted 03 December 2014 - 04:40 AM
i am pretty sure there is a reference to the faulty DMU's in the logfile i posted earlier.
Says something about expected to find "(" but found ")" instead.
It is in reference to the MEP Class 105 DMU and the MEP Class 105HC DMU.
Cheers,
Mike.