[Csantucci]

Aldarion, I hope I was clear that after having installed 150.2 you have to apply the patch of my above post.

[Aldarion]

Sucess. The train fulfilled all the jobs until entering pool and indicating "train terminated"

I'll try to test in other cases, like getting out of pool and things like that...

[Csantucci]

Great, thanks, I have inserted the patch into 150.2 which is now 150.3.

[joe_star]

Thank you Carlo! With your diff file and Git repository I have merged the changes in my personal fork (which is in sync with unstable - and some personal modifications)

The changes seem working well so far although it does seem unstable is missing some of the power/panto related changes which as you mention were pulled from it at some point.

Loving this :)

[joe_star]

Had to make some harmonization of the light code as well which differs between master unstable and NYMG, but after doing that it's been mostly smooth sailing with autopilot as well as train switching. I've only seen some suspicious behaviour on door opening/closing by AI in autopilot but suspect that may have to do with my code integration.

[Aldarion]

Hi Carlo.

Can I ask you to take a look at the last error just in the end of this log file, please?!

It's probably not realated the new autopilot feature, but has I've tried to use the feature to check on some rolling stock's service rotation instead of placing an observer train in one spot....

Attached File(s)

•  OpenRailsLog.txt (129.23K)
  Number of downloads: 29

[Csantucci]

Hi,
Sorry for the late response, but I oversaw your post. Can you try applying the attached patch to ORNYMG 150.3?
 PlayerTrainfix.zip (2.46MB)
Number of downloads: 32

In the meantime I have created an Autopilot for Timetable PR for the Unstable release. Unfortunately at the moment it fails being built with that release, due to a conflict with a preceding PR.
That PR includes only the Autopilot for Timetable, and not the other Timetable features that I have added in ORNYMG. Such features will eventually be included in later PRs, when the base PR would be merged.

[jugondavidlisto]

I've been searching, but i'm not sure if it has been mentioned in any thread. Basically, i'm trying to create a circular line that departs and returns to the same station.

I know that in TSRE5, if you try to create an activity and the route (without using the reversal point) of the train passes again through the same station, the program considers it as a stop, maintaining the chronological order of the route and adjusting the times.

Currently, to replicate this in timetable mode, i have to split the service into two different trains before passing through the same origin station again. Is there any possibility to include in the same station name two completely different times with a format like "08:00 09:00", indicating that, without the hyphen, it is expected to return to that station but with a different time?

[Aldarion]

lol. I even forgot this cause I had to go back to track laying.

But yes, I'll try it this weekend for sure!

Cheers

[Angelo Rosa]

Hi jugondavidlisto,

I dont know if it would work, but i would try to insert in that station 2 platforms, one nammed XXX outboud, and then another one XXX inboud.

In xxx outbound you would insert 08:00 and in xxx inbound insert 09:00.