[roeter]

Hannes44, on 31 January 2021 - 03:20 AM, said:

Another unwanted behavior popped up: the first locomotive enters the pool track, stops at the end and stays there. The second locomotive to enter the pool does that without problems, drives to the first one and then vanishes. I this normal behavior, what can I do, to make the loco stay as static?

Could it be pool overflow? Have you checked the logfile for messages?

Quote

Second question, re turntable pools. It is not very clear, where the access-path has to begin; I understand, clearly not on the turntable, but if I put the starting point a bit away from the turntable I get the information : "access path : szttt-tt-access1 does not start within storage area" in the log-file and storage doesn't work.

That warning is only issued for 'normal' pools, not for turntable pools. Have you set up the turntable pool correctly as *.turntable-or?
As for the access path, it has to run right up to the turntable, there may not be any switches etc. inbetween the end of the access path and the turntable.

Regards,
Rob Roeterdink

[Hannes44]

I don't think it can be overflow, as ist is the first locomotive of the day to be stored in the turntable pool.


Re. Logfile:
After the "access path : szttt-tt-access1 does not start within storage area"
and a second one "access path : szttt-tt-access2 does not start within storage area"

then follows
"poolstt-selzthal.turntable-or not included due to errors in pool definition"

I didn' find any example for a turntable-or pool file so maybe my construction is quite wrong: Could you have a look at it, please?


;#comment
#comment;Turntablepools in Selzthal
#comment;szttt-1142
#name;szttt-1142
#worldfile;w-005583+014723
#uid;1605
#storage;szttt-1142-pool1
#storage;szttt-1142-pool2
#storage;szttt-1142-pool3
#storage;szttt-1142-pool4
#access;szttt-tt-access1
#access;szttt-tt-access2
#settings;force creation
#comment;
#comment;szttt-1144
#name;szttt-1144
#worldfile;w-005583+014723
#uid;1605
#storage;szttt-1144-pool1
#storage;szttt-1144-pool2
#storage;szttt-1144-pool3
#access;szttt-tt-access1
#access;szttt-tt-access2
#settings;force creation

[roeter]

The remark on pool overflow referred to the first pool where 2nd etc. engines disappeared. That is typical for pool overflow.
As for the turntable pool, could you please post the full logfile here? I need to know the full context of the error reports.

Regards,
Rob Roeterdink

[Hannes44]

The situation with the turntable pools is now:
The locomotive drives to the turntable on its path, then changes obviously to the access path, drives on to the turntable, the turntable does not move into the correct position, does not move at all, locomotive crosses turntable, drives on the storage path, stops and vanishes. This is the corresponding log-file. The turntable is working correctly with a player train.

The other, non-turntable pool, is not used atm, but the storage path is long enough to store at least 5 locomotives of the stored variant.

Attached File(s)

•  OpenRailsLog.zip (5.13K)
  Number of downloads: 295

[roeter]

Can you make a screendump of the trackviewer showing both the storage and access paths for the turntable pool?

Regards,
Rob Roeterdink

[Hannes44]

Access path1


Acces path2


Storage paths

[roeter]

I'm lost.
The definitions seem to be correct. The pathing errors in the log file just don't match up. These are warnings for normal pools, not turntable pools. I just tried a very recent unstable version and it works allright. I have no idea why your program version apparently processes the turntable pools as normal pools.

Sorry, but I just don't know how to get on from here. Have you tried the latest unstable version?

Regards,
Rob Roeterdink

[Hannes44]

Thanks for your efforts. I tried now the latest unstable version, still no luck.

[Buttercup]

Are speed and clearance values required? They aren't listed as optional.

[Hannes44]

There is a general 40kph restriction in the whole area, there are no clearances required.