Page 1 of 1
| TT Trent 2009 v.3.9, problem 6M111 (PROBLEM FIXED) 05/01/2011 at 14:26 #2200 | |
Charlytos
268 posts |
Problem is over train 6M111, mentioned by me on old forum. Arrives to Nottingham FRP over 1 hour delay, indirect problem with 0D501 which arrives Nottingham UM over 15 minutes delay. Cannot make departure to GL line because 6M111 is stopped on junction. I sent it by FL line to Beeston South siding, fixed. Next problem is with loco 0M11 from 6M111, arrives to Nottingham any free platform and after reverse to join 6M111. Great problem found, simulation doesn't accept send loco where is 6M111. If move 6M111 to next GL signal, then can to send the loco well, but cannot to make the join from both trains. Question, how can to make the join on this case, for my reason is a great bug of this timetable!... Log in to reply |
| TT Trent 2009 v.3.9, problem 6M111 (PROBLEM FIXED) 05/01/2011 at 14:26 #13095 | |
|
Charlytos
268 posts |
Problem is over train 6M111, mentioned by me on old forum. Arrives to Nottingham FRP over 1 hour delay, indirect problem with 0D501 which arrives Nottingham UM over 15 minutes delay. Cannot make departure to GL line because 6M111 is stopped on junction. I sent it by FL line to Beeston South siding, fixed. Next problem is with loco 0M11 from 6M111, arrives to Nottingham any free platform and after reverse to join 6M111. Great problem found, simulation doesn't accept send loco where is 6M111. If move 6M111 to next GL signal, then can to send the loco well, but cannot to make the join from both trains. Question, how can to make the join on this case, for my reason is a great bug of this timetable!... Log in to reply |
| TT Trent 2009 v.3.9, problem 6M111 (PROBLEM FIXED) 05/01/2011 at 22:58 #13103 | |
BarryM
2158 posts |
Charlytos said:Question, how can to make the join on this case, for my reason is a great bug of this timetable!...Edited By: Charlytos Not a bug as such. The train should be 350m long for the engine to be able to run around its train.. Barry Barry, Sydney, New South Wales, Australia Log in to reply |
| TT Trent 2009 v.3.9, problem 6M111 (PROBLEM FIXED) 06/01/2011 at 13:48 #13109 | |
|
Albert
1315 posts |
If the sim does not accept running to 6M111, set the points of the route by left- and right-clicking, then make sure the loco is facing correct side Up/Down. Open F2 Train List, right-click 0M11, and choose Signalling -> Authorise to pass signal at danger. This is a workaround for routes that can't be set. On older sims (e.g. NLL and Stafford) this might end up in a train standing over the points, which does not drive in either direction anymore and has to be removed. In newer sims (every scrolly as far as I know) you can safe do this. AJP in games Log in to reply |
| TT Trent 2009 v.3.9, problem 6M111 (PROBLEM FIXED) 07/01/2011 at 00:16 #13114 | |
|
BarryM
2158 posts |
Albert said:If the sim does not accept running to 6M111, set the points of the route by left- and right-clicking, then make sure the loco is facing correct side Up/Down. Albert, this may work with old sims. Trent is a new sim. The train is too long for the engine to run around at this location. Barry Barry, Sydney, New South Wales, Australia Log in to reply |
| TT Trent 2009 v.3.9, problem 6M111 (PROBLEM FIXED) 07/01/2011 at 18:22 #13128 | |
|
Charlytos
268 posts |
Friends, loco 0M11 is stopped on platform 4, because the UM is on use. I proved to change section points of junction manually, but continues not canning to send loco to join with 6M111. Playing this timetable Trent 2007 v. 3.7, I modified destination for 6M111, no send it to PRL line and send it to UM line, modifing time entrance how has over 1 hour delay, then entrance 1 hour before. Changing point for loco 0M11, front UM line to signal 284/2 reverse to signal 256 and reverse to UM line, canning to join just so. But from v. 3.9 has default point pass and destinations for 0M11 and its train 6M111. Log in to reply |
| TT Trent 2009 v.3.9, problem 6M111 (PROBLEM FIXED) 10/01/2011 at 14:16 #13163 | |
|
Charlytos
268 posts |
Found cause of problem with loco 0M11. Train 6M111 had routed its ahead track to next signal. By that reason when created route for loco 0M11 from Nottingham 4 to FRP point where was 6M111 received next message: call on not allowed. Put off track selected ahead 6M111 and could to create well route for 0M11. This was personal mistake, when 6M111 arrived to platform 6 before select track to PRL line, I added the next section track by if would be necessary. Resuming details, found cause mistake and had to begin new session. Log in to reply |
| TT Trent 2009 v.3.9, problem 6M111 (PROBLEM FIXED) 18/01/2011 at 10:59 #13223 | |
|
Charlytos
268 posts |
Well friends, I fixed problem mentioned in previous messages of this threat over 6M111 and loco 0M11. Cause of problem over 6M111 was its length 350, as put BarryM. Put it to 150, then if occupies well position between FRP zone signals. Starting right uncouple loco 0M11 and after coupled by its rear. Detailed summary, problem fixed. Log in to reply |
| TT Trent 2009 v.3.9, problem 6M111 (PROBLEM FIXED) 21/03/2011 at 10:53 #14144 | |
|
KurtDS
49 posts |
The length of the train is not the problem, changing the length is not the solution, but cheating. What you do need to do is manually cancel the route at Mansfield Junction, because the conditions for TORR has not been satisfied. The controls won't allow a calling on from a signal in rear, if the signal ahead has a route set, even if that signal is at danger. I am sure this is in the manual. Log in to reply |