Page 1 of 1

"Not connected to destination..."

Posted: Sat Jan 09, 2016 2:26 pm
by riggs386
Hi... I'm altering the Settle - Carlisle route to pre 1989 configuration around Ribblehead, i.e. double track over the viaduct. I hadn't thought it would be too difficult, even though I'm a semi converted MSTS route builder, but I'm coming up against this problem all the time: I lay the track, everything seems OK., I make a free roam scenario and test everything and it still seems OK. But when I make a standard scenario say, from Horton to Garsdale, (traversing the newly laid section,) I get the error massage above. I've laid the track using the same track rule, checked it over and over all along - and several hundred metres each side of the new section, selected it and everything seems fine (no 'mixed track rules' message anywhere,) but I've obviously done something wrong somewhere... any ideas anyone?

Re: "Not connected to destination..."

Posted: Sat Jan 09, 2016 2:31 pm
by jp4712
Have you pressed the spacebar a few times while in world editor and checked the track directionality?

Paul

Re: "Not connected to destination..."

Posted: Sat Jan 09, 2016 2:57 pm
by riggs386
Thanks... I'll try that and report back.

Re: "Not connected to destination..."

Posted: Sat Jan 09, 2016 3:29 pm
by riggs386
Thanks... that did it. I keep forgetting to use the spacebar - I'm so used to just laying track and if it looks right, assuming it'll be right. I had a short section at the North end of the viaduct that was laid in the wrong direction: I selected it, toggled it and all's well now. The down track was only affected by that short section; the up track was a right dog's breakfast - up and down in alternate places, so it's a lesson well learned! Thanks again.