Page 1 of 2
Edinburgh Bugs 21/03/2010 at 15:12 #934 | |
Helper
20 posts |
Firstly, let me thank everyone involved in producing Edinburgh. Clearly a huge number of hours have been spent in creating and testing it to make it virtually bug free and an excellent sim. Having just lost a weekend to 24 hours of Edinburgh I could only find 3 issues. The first was a program access violation but the program continued! Sadly I didn't get a screenshot of the event. The second was 1S86. It arrived at P21 at Waverley. The supplied TT states it should stop at the near end but stopped at the far end (signal E446) and then kept telephoning me to advise it was waiting at the signal. In the end I reversed it's direction and it then registered that it had arrived at P21 although it remained next to signal E446. When 1S91 arrived to join with 1S86 it hung over the end of the platform due to 1S86 continuing to the end of the platform. The joined train then hung over the end but after joining I reversed direction and the train then trundled into P21 to fit in the platform. The third problem is one I can't resolve. I was scrolling from left to right using the keyboard arrow keys when a popup box appeared notifying me of a train entering at Haymarket TMD. I took my finger off the right arrow key but the sim continued scrolling to the right most position. I then clicked OK to clear the box but the scrolly was then stuck permanantly wanting to scroll to the right. When I selected one of the buttons 1 to 9 or scrolled left, I could see the scrolly immediately trying to scroll right. This meant the sim had become unusable and I had to save the game and re-load it to continue. Log in to reply |
Edinburgh Bugs 21/03/2010 at 15:12 #7572 | |
Helper
20 posts |
Firstly, let me thank everyone involved in producing Edinburgh. Clearly a huge number of hours have been spent in creating and testing it to make it virtually bug free and an excellent sim. Having just lost a weekend to 24 hours of Edinburgh I could only find 3 issues. The first was a program access violation but the program continued! Sadly I didn't get a screenshot of the event. The second was 1S86. It arrived at P21 at Waverley. The supplied TT states it should stop at the near end but stopped at the far end (signal E446) and then kept telephoning me to advise it was waiting at the signal. In the end I reversed it's direction and it then registered that it had arrived at P21 although it remained next to signal E446. When 1S91 arrived to join with 1S86 it hung over the end of the platform due to 1S86 continuing to the end of the platform. The joined train then hung over the end but after joining I reversed direction and the train then trundled into P21 to fit in the platform. The third problem is one I can't resolve. I was scrolling from left to right using the keyboard arrow keys when a popup box appeared notifying me of a train entering at Haymarket TMD. I took my finger off the right arrow key but the sim continued scrolling to the right most position. I then clicked OK to clear the box but the scrolly was then stuck permanantly wanting to scroll to the right. When I selected one of the buttons 1 to 9 or scrolled left, I could see the scrolly immediately trying to scroll right. This meant the sim had become unusable and I had to save the game and re-load it to continue. Log in to reply |
Edinburgh Bugs 21/03/2010 at 17:33 #7582 | |
UKTrainMan
1803 posts |
Helper said:The third problem is one I can't resolve. I was scrolling from left to right using the keyboard arrow keys when a popup box appeared notifying me of a train entering at Haymarket TMD. I took my finger off the right arrow key but the sim continued scrolling to the right most position. I then clicked OK to clear the box but the scrolly was then stuck permanantly wanting to scroll to the right. When I selected one of the buttons 1 to 9 or scrolled left, I could see the scrolly immediately trying to scroll right. This meant the sim had become unusable and I had to save the game and re-load it to continue.This is an issue I have noticed with all the scrolly simulations however I have decided again reporting it as a bug since I don't believe it is, in-fact it is more likely an Operating System issue. You can easily do this by holding down an arrow key then right clicking with the mouse button, for example. In order to stop it from continuously scrolling all you have to do is press the same arrow key again to stop it. In some ways you might be able to see and use this as a useful feature 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 21/03/2010 at 19:38 #7601 | |
Peter Bennet
5402 posts |
1 without further details I can't comment 2 can be looked at 3 as above seems reasonable. Peter I identify as half man half biscuit - crumbs! Log in to reply |
Edinburgh Bugs 21/03/2010 at 19:48 #7603 | |
GoodbyeMrFish
148 posts |
the access violation occurs when trying to click the built in help button key (F1) as far as i know all sims do this. best to look at the wiki, its more in depth anyway
Log in to reply |
Edinburgh Bugs 22/03/2010 at 00:40 #7629 | |
Helper
20 posts |
The access violation occurred again. It refers to a "timer callback". This time I got a screenshot - now trying to work out how to upload it.
Log in to reply |
Edinburgh Bugs 22/03/2010 at 06:28 #7637 | |
Peter Bennet
5402 posts |
Email it to me if you like Email address under 'contact us' Also as you have found it twice now do you have any feedback on what led up to it? Peter I identify as half man half biscuit - crumbs! Log in to reply |
Edinburgh Bugs 26/03/2010 at 16:49 #7850 | |
GMac
71 posts |
Not entirely sure whether both of these are bugs, but they have cropped up: 1. Auto-lower doesn't seem to work on the up line at Halbeath LC (not a major problem, but it does mean it has to be watched to avoid delays). Shunt moves seem to work fine (including down to up moves such as 0J13), but if a main line train approaches from Cowdenbeath I always have to lower the barriers manually. 2. When letting freight out of Bathgate Yard (6M85-A being the train in question), EN586 shows green even though the next signal up the line at Carmondean Jcn (EN581) protecting the entry onto the main is at danger! Wouldn't have thought it should do that unless there was a distant board between the two..... Log in to reply |
Edinburgh Bugs 26/03/2010 at 17:10 #7851 | |
UKTrainMan
1803 posts |
GMac said:1. Auto-lower doesn't seem to work on the up line at Halbeath LC (not a major problem, but it does mean it has to be watched to avoid delays). Shunt moves seem to work fine (including down to up moves such as 0J13), but if a main line train approaches from Cowdenbeath I always have to lower the barriers manually.Confirmed. GMac said: 2. When letting freight out of Bathgate Yard (6M85-A being the train in question), EN586 shows green even though the next signal up the line at Carmondean Jcn (EN581) protecting the entry onto the main is at danger! Wouldn't have thought it should do that unless there was a distant board between the two.....It goes green because there is a repeater (circled red in the screenshot below) signal between it and the red signal. Hope this helps. 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 26/03/2010 at 20:54 #7852 | |
GMac
71 posts |
Re point 2: It's not that one I was referring to, but the previous one (the exit signal from the yard EN586 - very top right directly above the Bathgate platform graphic). That shouldn't show green when 581 (which is green in the shot you attached) is at red, but I've had two freights leave the yard now where that has happened. Glad to know the Halbeath LC isn't just misbehaving for me though....
Log in to reply |
Edinburgh Bugs 26/03/2010 at 23:10 #7854 | |
Peter Bennet
5402 posts |
Both EN581 and EN586 are 2 aspect R/G so there is no Y to be given. Halbeath had a bug in it. Thanks Peter I identify as half man half biscuit - crumbs! Log in to reply |
Edinburgh Bugs 27/03/2010 at 04:09 #7859 | |
Mad Mac
13 posts |
Here's my list so far: 1) 0S25 won't go into Craigentinny from EP622 (driver challenges route). 2) No sub route E444 - E426. Pushing 444 entrance followed by 426 sub exit gets a message "not a valid route", or words to that effect. 3) 1S25-2 - timetable shows it routed via Line W out of Waverley, but at that time, 0A25 is standing there! 4) Odd one - 1E02 called in from Dunbar to say that he would be delayed and asked if I wanted to put ED494 back to red. I accepted the generous offer as 1V41 was scheduled to pass Dunbar before 1E02's estimated departure time. However, the overlap didn't time out in front of ED494, as 1E02 was still in the station and not sitting on the berth of ED494. Possible train length issue? 5) Inadvertently sent 2P08 (Stirling - Newcraighall) down the main line instead of towards Millerhill. Driver didn't challenge the route. Log in to reply |
Edinburgh Bugs 27/03/2010 at 06:44 #7863 | |
Peter Bennet
5402 posts |
Mad Mac said:Here's my list so far: Not a problem I can find and never reported in testing Quote: 2) No sub route E444 - E426. Pushing 444 entrance followed by 426 sub exit gets a message "not a valid route", or words to that effect. Fixed Quote: 3) 1S25-2 - timetable shows it routed via Line W out of Waverley, but at that time, 0A25 is standing there! Looking at TT I think you let 0A25 out too early Quote: 4) Odd one - 1E02 called in from Dunbar to say that he would be delayed and asked if I wanted to put ED494 back to red. I accepted the generous offer as 1V41 was scheduled to pass Dunbar before 1E02's estimated departure time. However, the overlap didn't time out in front of ED494, as 1E02 was still in the station and not sitting on the berth of ED494. Possible train length issue? I'll have a look Quote:
I'm not a fan of invalid route code but I'll have a look at this one. Peter I identify as half man half biscuit - crumbs! Log in to reply |
Edinburgh Bugs 27/03/2010 at 21:55 #7911 | |
Mad Mac
13 posts |
0S25 - I'll go back and try that one again. 0A25 - Mea Culpa! Log in to reply |
Edinburgh Bugs 27/03/2010 at 23:21 #7912 | |
UKTrainMan
1803 posts |
UKTrainMan said:GMac said:2. When letting freight out of Bathgate Yard (6M85-A being the train in question), EN586 shows green even though the next signal up the line at Carmondean Jcn (EN581) protecting the entry onto the main is at danger! Wouldn't have thought it should do that unless there was a distant board between the two.....It goes green because there is a repeater (circled red in the screenshot below) signal between it and the red signal. GMac said: Re point 2: It's not that one I was referring to, but the previous one (the exit signal from the yard EN586 - very top right directly above the Bathgate platform graphic). That shouldn't show green when 581 (which is green in the shot you attached) is at red, but I've had two freights leave the yard now where that has happened. Glad to know the Halbeath LC isn't just misbehaving for me though....:: D'oh! I feel like a right plonka now! :O Let's just put it down to working a late shift at the box. 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 30/03/2010 at 21:22 #8004 | |
DavidB
31 posts |
Firstly thanks for yet another great new simulation. I don't know if this specifically an Edinburgh bug or something that people have found in other simulations, as of yet I have never noticed it before. I have tried searching the forum but each search has pulled up 100s of posts. Whilst playing on the Standard setting using ARS for everywhere except Edinburgh & Haymarket whilst I learnt what was there I have suffered several long track circuit failures that caused very long delays. On two occasions following these delays one of the delayed trains stopped at every signal afterwards regardless of the signal state and I have had to tell the train to "Examine and pass signal at danger". Not sure if I am missing something obvious or not but I thought I would mention it. Dave Log in to reply |
Edinburgh Bugs 30/03/2010 at 21:31 #8005 | |
UKTrainMan
1803 posts |
DavidB said:Whilst playing on the Standard setting using ARS for everywhere except Edinburgh & Haymarket whilst I learnt what was there I have suffered several long track circuit failures that caused very long delays. On two occasions following these delays one of the delayed trains stopped at every signal afterwards regardless of the signal state and I have had to tell the train to "Examine and pass signal at danger".Are you saying that even if the signal was showing green the train would stop and report it as red? 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 30/03/2010 at 21:39 #8006 | |
DavidB
31 posts |
UKTrainMan said:Are you saying that even if the signal was showing green the train would stop and report it as red?Yes! Log in to reply |
Edinburgh Bugs 31/03/2010 at 13:13 #8015 | |
gidil
16 posts |
I had this yesterday! Down right annoying! Log in to reply |
Edinburgh Bugs 31/03/2010 at 16:47 #8016 | |
indian_railways_fan
72 posts |
>Whilst playing on the Standard setting using ARS for everywhere except Edinburgh & Haymarket whilst I learnt what was there I have suffered several long track circuit >failures that caused very long delays. On two occasions following these delays one of the delayed trains stopped at every signal afterwards regardless of the signal state and >I have had to tell the train to "Examine and pass signal at danger". >Not sure if I am missing something obvious or not but I thought I would mention it. Yes I had also come across a similar "bug" but it turned to be a regular albeit slightly mis-leading feature.The key lies in "Examine and pass signal at danger".Once you have given that instruction to the driver,he passes the signal and then stops at the next signal and calls in to say that no obstructions were found on the track.But while the driver is calling in,the F2 train-list shows the train waiting at a red signal and this makes us think that the train is now calling from all the signal posts.To avoid such confusion simply "authorise the train to pass the signal at danger" and you should not have it calling again! Log in to reply |
Edinburgh Bugs 07/04/2010 at 18:32 #8244 | |
Tevildo
28 posts |
One minor problem that I don't think has been mentioned yet - trains to Longannet generate an ARS "7xxx needs to have a manual route set" message, even though the ARS has requested the slot automatically. Otherwise, thanks to all concerned for a most interesting and challenging sim! Log in to reply |
Edinburgh Bugs 17/04/2010 at 12:40 #8598 | |
peterb
452 posts |
A train from Grantshouse up loop to the engineers siding did not challenge the route when it was set to EG434 instead of into the siding. Also, attempting to interpose directly into the berth (not by right clicking the sig) causes the error message 'cannot interpose into a queue berth' at signal EV407 (North Queensferry down), and Edinburgh platform 7.
Log in to reply |
Edinburgh Bugs 17/04/2010 at 13:06 #8599 | |
Peter Bennet
5402 posts |
Tevildo said:One minor problem that I don't think has been mentioned yet - trains to Longannet generate an ARS "7xxx needs to have a manual route set" message, even though the ARS has requested the slot automatically.That's because ARS is not setting the route but a different sort of auto-route setting which works in non-ARS as well as ARS mode- donlt think tehre is any way of supressing the message- so ignore. peterb said: Also, attempting to interpose directly into the berth (not by right clicking the sig) causes the error message 'cannot interpose into a queue berth' at signal EV407 (North Queensferry down), and Edinburgh platform 7.There's a bit on Q berths in the WIKI. Peter I identify as half man half biscuit - crumbs! Log in to reply |
Edinburgh Bugs 23/05/2010 at 13:36 #9344 | |
Adrian the Rock
111 posts |
Helper said:...The second was 1S86. It arrived at P21 at Waverley. The supplied TT states it should stop at the near end but stopped at the far end (signal E446) and then kept telephoning me to advise it was waiting at the signal. In the end I reversed it's direction and it then registered that it had arrived at P21 although it remained next to signal E446... A bit more info re this. Similar thing just happened to me, but when I reversed direction it promptly went to the West end and did the same - in the train list it was showing as 'Waiting at red signal'. After a few unsuccessful attempts to get it to Stop at Edinburgh I tried editing the TT and changing the stoping position to default (while it was still waiting for red signal at the Haymarket end). Immediately I had done this it duly changed to Stopped at Edinburgh and then immediately to Waiting for Joining Train as expected. Log in to reply |
Edinburgh Bugs 24/05/2010 at 07:58 #9355 | |
GoochyB
222 posts |
Adrian the Rock said:A bit more info re this. Similar thing just happened to me, but when I reversed direction it promptly went to the West end and did the same - in the train list it was showing as 'Waiting at red signal'. The same happened for me. I tried abandon tt/run to another tt & reverses of direction but it wouldn't register that it was at Edinburgh. However, when the joining train arrived they started joining without any further intervention (except maybe a reverse to correct the direction that 1S86 was facing after doing the above). Log in to reply |