Script Exceptions, What do I do?

CityRailTrainspotter

SydNSWTrains on Youtube
Most of you should be familiar with that little red button in the right corner when in Driver which is, Script Exceptions. I used to just click the button and close it and it would never return but now it never goes away. I click close and in less than a second it returns and keeps flashing green - yellow - red continuously. It may seem like a small problem but when I record in Trainz and do a screenshot, it is always there sometimes ruining the screenshot or video. The question is, how do I resolve the script exceptions? Any help please. Cheers
6630214337_949cc97a9a_b.jpg

The Script Exceptions button appears in this screenshot. (Image from Australian Screenshots)
 
To be able to advise on script exceptions, you will need to click the red dot and supply a screenshot of the resulting screen (or type out the exception), then double-click the error shown and do the same with the following screen.

Shane
 
I've checked the errors, and it looks like you've got a faulty signal asset - NSW 3asp RD.

I would advise checking if there's an update available for this asset.

Shane
 
Funny this i saw today have no clue what it means.


photostream




photostream


Sorry trying to add screen shots with flicker any help.
 
Last edited:
Kmver - what that is basically telling you is that you need to do an extended database repair.

Shane

P.S. For some Flickr images, it's easier to just post a link to the image.
 
A possible reason for this error could be the deletion of a junction lever, referenced by the signal.

All of these diverging signals (NSW signals by Natvander, light or semaphore) have another problem. After starting the session they sometimes display a wrong aspect. After switching the referenced junction (twice ?) the correct aspect is displayed.

Peter
 
Based on what the error stated, it may well be that one of the signals is confused on what it should be doing, so if it's your own route it may be worth replacing the affected signal with another type.

Shane

There are at least 50 of these signals on my massive route, and the error message doesn't state the name I gave the signal so how am I supposed to find which signal it is amongst all of them?
 
Losing a junction lever is quite common, at least for me. Generally I found out that this is a problem when my AI trains refuse to move.

You could use the Find Object dialog box, change the type to Trackside and select each junction in turn. This should show if the lever is missing.

The script appears to be failing because it is trying to read a value from the Soup (the Trainz database) and the value is not initialised. I noticed that these signals have a setup browser for each instance of the signal and maybe that is not set up correctly. I don't know much about signals so I cannot help with that.

I'd check for missing junction levers first. If that is ok then you might need to look at the settings (in the browser) for each of those signals.
 
I checked if there was any missing junctions, there doesn't seem to be. What do you mean for the second bit?

In Surveyor, select one of the signals then use the question mark icon on it. That brings up the Properties Box which is a browser. There are settings attached to the signal.
 
In Surveyor, select one of the signals then use the question mark icon on it. That brings up the Properties Box which is a browser. There are settings attached to the signal.
The settings only show which junction you chose for that signal and the diverge speed. I did find a 'Signal 3asp RD' with no junction assigned to it, I deleted that but the script exceptions still shows.
Thanks for your help though, Paul.
 
Back
Top