[ebnertra000]

I'm trying to come up with a new signal system, but I get this 'Key not found exception error every time I attempt to load the testing route for the set. The error definitely makes it appear that something in the signal script file is at fault, but as the log doesn't give any other errors in the script file, I have no idea where to look. Attached is the log. The test route may also be sent if requested

Attached File(s)

•  OpenRailsLog.zip (4.08K)
  Number of downloads: 245

[roeter]

Apparantly, there is a default draw state missing somewhere.
No need to provide the complete route but if you can provide sigcfg.dat and sigscr.dat I should be able to find out what's wrong.

Regards,
Rob Roeterdink

[ebnertra000]

Thanks for the tip. I actually found it almost immediately once I knew what to look for. I had a draw state named 'yellow' that should have been named 'yel'. At least now I know what to look for if I get that

[ebnertra000]

Another question: Does the variable 'next_nsig_lr ();' work on signal types that aren't NORMAL? I should think it would, but it doesn't seem like it. Unless I'm doing it wrong, which is very possible

[roeter]

The function next_nsig_lr() will work on any signal type, but it must be remembered that the function can only search ahead as far as a path has been cleared for an approaching train. The function will not search beyond the end of that path, e.g. it will not search beyond a normal signal which is at state STOP.
This restriction may affect the outcome of this function.

Regards,
Rob Roeterdink