Morning all... I have 2 questions about this route... 1. Playing the scenario Shaken not Stirred, upon arrival at Fort William you are required to run round your train... After returning the single line token to Banavie and uncoupling from my train, I move forwards into the neck / headshunt & change ends... Changing the points, I get a notification that I am now under the control of normal signals... Pressing TAB gives me approval to pass the signal at danger. I move the light engine forwards but when I do so I fail the scenario because I've passed a signal at danger...!!! I've attempted this 4 times now & have even saved my progress once arriving in FW so I can retry starting in the headshunt but I still fail...!!! I've had a good look around but can't see any signal even though I have approval to pass the signal at danger... What am I doing wrong??? The second question pertains to my general driving style & wonder how drivers deal with this in real life... When descending gradients (generally in double figures 1:99 etc...) dynamic braking obviously doesn't come into it (unlike US locos) however when it comes to controlling my train speed I find the train brake "too severe" and have resorted to using the loco brake only to control my speed... Would this be considered normal practice in the real world & if not how is it actually done in the real world??? Apologies if my post is a bit on the lengthy side!!! Eric
Don't have the route so this is a guess but do you need to use Ctrl+Tab to pass a signal behind you? I find that TS's idea of which end is the front and which is back can be quite independent of which cab you are in and how your reverser is set and one can lose track.
I've had the same problem. After trying several times, it is the ground position signal at the far end of the track that causes the SPAD. If I remember, after hanging ends and setting the route, bring up the taskbar screen and select the request to pass "behind" you.
Don't forget that no matter what YOU do in the scenario, the front of the loco or consist is set at the beginning of the scanerio itself, so even if you change ends "the front" as far as the dispatcher is concerned hasn't changed, so in this case CTRL+TAB will allow you to pass the signal Best thing to do I find is to determine when the brakes actually start to apply (sometimes it's at the 30% mark rather than 0%) and when going downhill keep a tight rein on the braking, not allowing the speed to drift more then .3 or.4 above the limit before putting the brakes on a bit to slow things down
Nope... Suggestions on here don't seem to work... Still SPAD when trying to run round the train / empty stock... Does anyone have any other ideas??? Eric
Inver... Not been on TS22 in ages tbh... not had much time of late... I'm on holiday from work this & next week so hopefully I'll get chance to go on it at some point... Eric
If you're not sure bring up the F1 overlay. You can see if signals in front of you or behind are on danger if the buttons on the right are highlighted.
Well I had a go at this scenario this morning and finally managed to solve the mystery, which appears to be caused by a technical issue. I pulled into Fort William, uncoupled and pulled forward of the crossover, beyond the leverframe, and looked at the track layout overview to reverse both the crossover points. Then, like everyone else, upon reversing the 37, I immediately encounter the SPAD and game over. Reloading from just before that point (thank heavens for F2!), I looked about the area, to determine which signal could possibly be causing the SPAD. All I could see were two ground signals at red along the crossover line and it's neighbour. (Remember the reference to 'conventional signals' in the scenario advice at that point means you are following these physical signals, and not applying for a new RETB token, which can also be used for shunting manouevres strictly within station limits.) So I explored further along the track in the direction of those signals, when I noticed that the second set of points in the crossover hadn't been reversed, despite me doing so in the track overview: I checked the overview, and the route seemed correctly set. So I reversed the points manually using the lineside lever. Low and behold the ground signal clears and I am able to reverse and pull around my train, with no TAB or CTRL+TAB required (the earlier SPAD must have been related to the red ground signal due to the half set crossover). From that point, the scenario can easily be completed, pulling forward with the train, then reversing using TAB at the signal below at the station end of approach (see cleared shunt signal) to get permission to bring the train into Platform 2 for berthing. Naturally, I threw away all my points with time taken figuring this out (a 1,700 point penalty for a few minutes lateness?!), but it just proves the scenario can be done. Presumably it's some sort of coding issue underlying this bug? Can a patch or something be issue to resolve this? Now if only someone could install RETB on an AP Class 37.....
Part of my tardiness was caused by this lineside stag, complete with sound effects, which I'd never noticed before on the route! Incidentally, it was also a nice change to see a more typical type of bus on the route, instead of the usual red London double decker buses that seem to run all over rural Scotland!
Inver... Not had chance to be honest... Keep poking me.. The weekend will be my next chance to get on TS... Eric
On first arrival go up to but not beyond the "reversing marker", shown next to the track and also on the tape as a "signal". After decoupling, moving the loco forward and changing ends, use the lever frame to change the points and wait for the shunt signal to clear. You do not have to ask permission to pass a signal at danger.
The previous reply in this thread was 17 Jan 2022 - over two years ago - they might have solved the problem as nothing was asked again
They didn't solve the problem because nobody seems to have realized the cause of the SPAD, which was going beyond the reversing marker before uncoupling. It is not a glitch. It's a pity the manual doesn't explain about the reversing marker. The signaller mentions the reversing marker as you approach the station and I had to figure out what they meant.
How can you be definite ("They didn't) and then be assumptive ("nobody seems")? Not every issue mentioned in forums gets reported as being eventually solved, and after 2 years it's reasonable to assume that nobody's now not that bothered about it. There are plenty of ongoing discussions to contribute to, no need to search through the archives to find old ones!
I didn’t go searching through the forums. I was trying to do this scenario and none of the posts here could help me. I remember the signaller mentioning the reversing marker and nobody mentioned it in this discussion so I investigated and it became obvious to me when I saw it.
Like yourself this is a new user to the forum. They believe they have helped provide a solution to an original thread. It would be nice to either say nothing or be positive. Respectfully
