Page 2 of 2
Edinburgh Bugs 24/05/2010 at 16:50 #9362 | |
Peter Bennet
5402 posts |
Just to be clear was this the Edinburgh location and not either East or West? Was it the booked platform? Is this the only train that has a problem? Peter I identify as half man half biscuit - crumbs! Log in to reply |
Edinburgh Bugs 24/05/2010 at 19:04 #9365 | |
GoochyB
222 posts |
Yes, it was the scheduled platform, the 'top' one (21 from memory?), and it was the only train it happened on to me when it was in it's scheduled platform. Similar problems do arise if a train that is scheduled for 20 or 21 is put into an east/west platform, or vice versa.
Log in to reply |
Edinburgh Bugs 24/05/2010 at 20:37 #9367 | |
Peter Bennet
5402 posts |
It's to do with the join- if you remove it then the train stops as expected. I'll need to report it and see what's what. Hmm and if you delete 1S91 so it never enters then 1S86 stops as expected. Right what you need to do is amend 1S91 to default stopping point- which is 'far end' but for some reason it causes problems if you say so. Peter I identify as half man half biscuit - crumbs! Log in to reply |
Edinburgh Bugs 26/05/2010 at 12:43 #9378 | |
truckgirl 66
25 posts |
Gentlemen Iexperienced an unusual failure yesterday whilst playing Edinboro 1993 all my groundframes locked up I was unable to release any of them. Train concerned was 8K04 paint train into dalmeny yard ended up sending service to Millerhill 15 minutes later everything ok. Also 0g25 not accepted by Thornton yard. What went wrong everthing now ok THANKS MARTIN WITHERS
Log in to reply |
Edinburgh Bugs 26/05/2010 at 18:49 #9384 | |
Peter Bennet
5402 posts |
Can you be more specific? When you say they all 'locked up' what exactly does that mean? And from your final comment can I take it it's all fixed now? Peter I identify as half man half biscuit - crumbs! Log in to reply |
Edinburgh Bugs 27/05/2010 at 11:31 #9390 | |
truckgirl 66
25 posts |
Thks for your reply,what happened was unable to release any groundframes by any means particularly dalmuir up gf this problem did occur again at Granthouse I have not had this problem on any other Edinboro tts, other than this it is a fantastic sim even better than Trent which is still my favourite. Regards Martin.
Log in to reply |
Edinburgh Bugs 27/05/2010 at 11:45 #9391 | |
truckgirl 66
25 posts |
Sorry my mistake shld read Dalmeny up gf not dalmuir THKS Martin
Log in to reply |
Edinburgh Bugs 27/05/2010 at 12:11 #9392 | |
AndyG
1842 posts |
The Ground Frames locking section in the Edinburgh manual may help.
I can only help one person a day. Today's not your day. Tomorrow doesn't look too good either. Log in to reply |
Edinburgh Bugs 27/05/2010 at 15:38 #9393 | |
truckgirl 66
25 posts |
Thanks again ground frame problem put itself right everything now ok I did not take any corrective measures at all Many thanks Regards MARTIN
Log in to reply |
Edinburgh Bugs 13/06/2010 at 21:42 #9629 | |
Tevildo
28 posts |
I've just had a rather worrying failure at EU451 - the fully automatic signal on the Down Fife line at Aberdour. The signal went back to red about 10 seconds before 6G28 passed it, giving me an ACOA penalty and the driver a chance to try out his SuperHyperPostWestinghouse brakes. See attached. Log in to reply |
Edinburgh Bugs 05/12/2010 at 18:09 #12789 | |
UKTrainMan
1803 posts |
Possible new bug in Edinburgh, whilst just aimlessly looking around the simulation today I decided to have a bit of fun and divert some trains via Millerhill. Started the 'Edinburgh August 2006 v2.214.1 0445 Start' timetable and played it through for a while, got 5E01 out of Craigentinny and into it's booked platform, played along for a while, removed a few other trains (mainly some freight trains, including some that entered at Millerhill (Niddrie)) and then it came to 0600hrs, got the TRTS for 1E01, routed train out of Waverley as booked, called up Millerhill to inform them of 1E01 being diverted, they accepted it and off it went without a problem to Millerhill. Not long after, 1E01 headcode appears at Millerhill (Monktonhall) on the Up Goods, as expected, but Signal EM587 drops to a Single Yellow, then eventually to a red and suddenly Track Circuit TMLDB (which is the overlap beyond Signal EM587) shows as occupied. Then Track Circuit TMJDA shows as occupied, the message window shows 1E01 as having just passed Monktonhall Jn, then further Track Circuits along the 'fraid I don't have a save of this but if you'd like me to try to recreate it and provide a save before this problem and after then please do let me know and I shall make an attempt at doing so. Any views and / or opinions expressed by myself are from me personally and do not represent those of any company I either work for or am a consultant for. Log in to reply |
Edinburgh Bugs 05/12/2010 at 19:48 #12792 | |
Peter Bennet
5402 posts |
There is a flaw- reported somewhere- in the control logic at Millerhill in that some some hidden points were not lying in the right orientation at the appropriate time. Somewhere else I said that around Christmas I'd give an update on the status of the 3 McSims if revisions had not been released- I'll do that shortly. Peter It's under "known issues" on the WIKI I identify as half man half biscuit - crumbs! Log in to reply |
Edinburgh Bugs 13/12/2010 at 20:43 #12889 | |
gussteedman
3 posts |
Using the 1993 timetable and Edinburgh v2_207. A bit of background first. I had a track circuit failure at Dunbar, effectively locking the route from ED487 on the down line into the platform and cutting off the possibility of passing traffic through on the up line. I decided to switch up traffic to the down line at Stenton, manually switch it into the platform at Dunbar and back to the down line by authorising to pass red signals at ED818 and ED494, and then back to the up line at Oxwellmains. Whether that's a good thing to do, I don't know, but it worked. I only had to do it for one train and then the problem was fixed. The issue occurred when 1S18, an AC powered train from Berwick reached Stenton on the down line. It stopped dead at ED513 reporting unsuitable traction. It could be reversed ok but would not progress past ED513. I have a save game, but since the problem clears away on re-load it seems to be more like an internal value gone wrong. Sorry if this is a known issue, or maybe if I'm missing something somewhere. Cheers, Gus. Log in to reply |
Edinburgh Bugs 13/12/2010 at 21:02 #12890 | |
Peter Bennet
5402 posts |
Just tried and it worked so I guess it was a glitch your end. Peter I identify as half man half biscuit - crumbs! Log in to reply |
Edinburgh Bugs 14/12/2010 at 14:46 #12892 | |
Albert
1315 posts |
Even computers can make mistakes - this has happened here. It does not mean there's something broken - it can happen on every computer and in every program (though it happens more when your computer becomes old).
AJP in games Log in to reply |