Page 1 of 1
| Swindon Bug [Serious Bug!] 13/05/2012 at 22:20 #32320 | |
2W34
58 posts |
Hi all, Got to around 0830 on the 2009 WTT. Simsig has popped this error up rendering Swindon unusable: Access violation at addres 00493EEE in module 'SwinDid.exe' And then... Internal Error: Exception in DrawStringCore I close these windows but no trains move after them. Any ideas? Log in to reply |
| Re: Swindon Bug [Serious Bug!] 13/05/2012 at 22:40 #32321 | |
|
Stephen Fulcher
2078 posts |
Might be worth searching the forum because I am sure this has been mentioned before.
Log in to reply |
| Re: Swindon Bug [Serious Bug!] 14/05/2012 at 15:04 #32327 | |
Steamer
3984 posts |
I've had a problem that sounds a bit like this, my cure was:
"Don't stress/ relax/ let life roll off your backs./ Except for death and paying taxes/ everything in life.../ is only for now." (Avenue Q) Log in to reply |
| Re: Swindon Bug [Serious Bug!] 14/05/2012 at 16:01 #32329 | |
|
MikeW
65 posts |
Yes, I've come across this as well - if I remember correctly it was mentioned in the forum ages ago, but I can't locate the previous posts. I've found that all one usually needs to do is 'Edit timetable' from the F2 display for offending trains, and then just click OK on the timetable edit screen. There doesn't appear to be any need to change anything - just hitting OK knocks the train out of its trance. Can be a bit of a bind when it's very busy - several trains to do this to - but everything seems to work ok from then on (until you next save and reload and then it starts all over again!). Log in to reply |
| Re: Swindon Bug [Serious Bug!] 14/05/2012 at 16:45 #32330 | |
postal
5264 posts 
|
It was reported on the developers' Bug Board on 21/07/2008. Those of us who have been around for a while can certainly remember discussion on the Forum; as the old Forum was stood down and this Forum created towards the end of 2009 if my memory is working properly, the discussion will have occurred on the old Forum and not here. This is presumably why the "Search" here produces no information. On the Bug Board, Clive reported the workround as "Fixed by Edit timetable OK of offending trains" and then later noted the problem as resolved so it is (hopefully) only a problem on the version of the core code used for the SwinDid build. I guess we'll have to live with it until the next upgrade. “In life, there is always someone out there, who won’t like you, for whatever reason, don’t let the insecurities in their lives affect yours.” – Rashida Rowe Log in to reply |
| Re: Swindon Bug [Serious Bug!] 14/05/2012 at 17:09 #32331 | |
|
y10g9
895 posts |
having got this problem alot, i have not noticed this error with swindid after the last version came out afew months ago. 2w34, what version of swindid are you running?
Log in to reply |
| Re: Swindon Bug [Serious Bug!] 14/05/2012 at 17:50 #32332 | |
Peter Bennet
5402 posts |
I remember the 2008 problem but the bug report does not say what the error message was. Anyway, looks like something similar to what we have here was reported (bug 6795) in December 2011 and reported fixed 4 May 2012. Peter I identify as half man half biscuit - crumbs! Log in to reply |