Removed the blanks, shortened the access path, still no luck.
Pool creation troubles
#12
Posted 29 January 2021 - 05:10 AM
well at this point i'm really at a loss.
if you would care to zip the openrailslog.txt file along with the timetable file, pool file and the three paths, i can have a look!
if you would care to zip the openrailslog.txt file along with the timetable file, pool file and the three paths, i can have a look!
#13
Posted 29 January 2021 - 06:12 AM
Heureka, found the problem: there was a blank line on top of the pool-file. Removed the empty line, now it seems to work!
#14
Posted 29 January 2021 - 06:48 AM
Its the simple things that makes us loose some hair! :sign_rockon:
#15
Posted 29 January 2021 - 09:00 AM
You're so right! Onwards to the next task! Trying to master turntables. :wallbash:
#16
Posted 29 January 2021 - 11:10 AM
Not done that yet. Have to build one for my scenery :)
#17
Posted 31 January 2021 - 03:20 AM
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?
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.
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.
#18
Posted 31 January 2021 - 08:56 AM
Can't help you on turntables.
Has for the first problem, it should not happen... I will give you an example and try to go along to see if you're using the same principles.
I have a train departing from station A and arrives on station B, designated "SD3013". On station B there is a swithc of traction. The electric locomotive leaves the consist and goes to a shed (a pool) and a diesel loco comes from it's corresponding shed (another pool) and takes the train and departs.
Train SD3013
Essentialy, I tell the locomotive to leave the coaches (as static) and tunr into another train (SD3013Mloc)
Train SD3013Mloc
And that's it. The thing here is that I separeted the maneuver movement from the main train movement - I splited the movements. Do you do that? It has been highly recomended by roeter and in his own words:
Has for the first problem, it should not happen... I will give you an example and try to go along to see if you're using the same principles.
I have a train departing from station A and arrives on station B, designated "SD3013". On station B there is a swithc of traction. The electric locomotive leaves the consist and goes to a shed (a pool) and a diesel loco comes from it's corresponding shed (another pool) and takes the train and departs.
Train SD3013
Last Station; 17:14 $detach /nonpower /static #dispose; $forms=SD3013Mloc:manobras-Entroncamento
Essentialy, I tell the locomotive to leave the coaches (as static) and tunr into another train (SD3013Mloc)
Train SD3013Mloc
#dispose; $pool=pool-entroncamento-LE
And that's it. The thing here is that I separeted the maneuver movement from the main train movement - I splited the movements. Do you do that? It has been highly recomended by roeter and in his own words:
roeter said:
In many cases, and in particular where reversals are involved, splitting trains works much better and causes far fewer problems.
Splitting a train working into multiple trains in the timetable has no effect on the running of that train, not as AI nor as player train. And there is no need to worry about the total number of trains - timetables can easily handle hundreds and even thousands of trains. Only startup (prerun phase) will take a bit longer, but that's all.
Regards,
Rob Roeterdink
Splitting a train working into multiple trains in the timetable has no effect on the running of that train, not as AI nor as player train. And there is no need to worry about the total number of trains - timetables can easily handle hundreds and even thousands of trains. Only startup (prerun phase) will take a bit longer, but that's all.
Regards,
Rob Roeterdink
#19
Posted 31 January 2021 - 10:28 AM
Yes, the train is split, I read that roeter post, too. The curious fact is that the first loco, sent to the pool stays visible, from the second on, they vanish.
#20
Posted 31 January 2021 - 12:39 PM
Also happenend to me once or twice... I'm having difficulty remebering what was wrong at the time...!