Page 1 of 1
| Access Violation 12/12/2014 at 06:20 #66500 | |
Airvan00
129 posts |
Had one of those pesky Access violations, but I have managed to solve it, this is just for information for people who may encounter the same problem The error message ( screen shot attached ) Internal error: Exception : 2N04/6O62. Now 6O62 was a train that I had earlier taken off planned route before returning it to its planned route. I had noticed that for some subsequent trains the ARS had not continued setting a route due to "giving priority to 6O62" However 6O62 was now well past the point of conflict. My theory is that occasionally the ARS has the incorrect position information for a train and causes other trains to "give way" to the errant, train which is now a lot further down the line. My solution is to make the errant train Non ARS. I assume this takes it out of the table. The error message doesn't occur and I can continue without a frozen computer. The simulation just prior to the error message is also attached so you all can see the situation and to completely disprove my theory 
Post has attachments. Log in to view them. Log in to reply |
| Access Violation 12/12/2014 at 12:56 #66511 | |
|
clive
2823 posts |
I can't read that; it's too small on my screen. Please always give the *complete* message.
Log in to reply |
| Access Violation 12/12/2014 at 15:07 #66514 | |
|
TimTamToe
665 posts |
" said:I can't read that; it's too small on my screen. Please always give the *complete* message.Clive I've tried zooming in to the image the original poster uploaded and it looks like the same message that I posted up the other day and that was previously noted in the loader bug topic Gareth Log in to reply |
| Access Violation 12/12/2014 at 20:48 #66547 | |
|
Airvan00
129 posts |
Sorry Clive, here is a better screen shot. running the .ssg file brings up the error message within 5 sec (at least on my computer) Post has attachments. Log in to view them. Log in to reply |
| Access Violation 13/12/2014 at 00:30 #66571 | |
|
clive
2823 posts |
Address 430D27 - that's the same problem as reported in an earlier thread. We don't need any more reports with that address in (in loader 4.3, that is). Thanks anyway. Log in to reply |