NLL Scrolly beta release

I'll post this in the right topic now!

Hi folks, just a little problem I'm having that I can't get to the bottom of.

I've got the NLL Scrolly sim open, and I'm trying to export the 2003 Winter v1.1 TT to TXT using ConvData. The trouble is that it won't convert, no matter what I do. Convdata gives me the message, "Convdata terminated with exit code 1633972".

I tried ConvData on another sim (South Humberside) and it works fine, so what is preventing it from converting on this sim?

Thanks.

Lazzer,
I tried the ConvData on this timetable and it produced the txt file without any errors. I suggest you rename the timetable to something simple like Nll.wtt and try again. If you like, I can send a copy of the file to your email address.
Barry

Ah ha! That is precisely the problem!

ConvData.exe needs to be in the same folder as NLL.exe. It now works. Thanks for that tip. I'll remember that for next time another sim won't work.

Also, trains stopping at Brondesbury Park seem to have trouble getting started if GO22 is at danger when they arrive, just sitting there waiting for RA - presumably related to the station being in advance of the signal but on the same TC.

" said:

Also, trains stopping at Brondesbury Park seem to have trouble getting started if GO22 is at danger when they arrive, just sitting there waiting for RA - presumably related to the station being in advance of the signal but on the same TC.

Without the benefit of the Sim in front of me: if a train stops within sighting distance of a signal (Sim default 300m but can be bespoke) then it will not restart until the signal is off.

Peter

" said:

" said:

Also, trains stopping at Brondesbury Park seem to have trouble getting started if GO22 is at danger when they arrive, just sitting there waiting for RA - presumably related to the station being in advance of the signal but on the same TC.

Without the benefit of the Sim in front of me: if a train stops within sighting distance of a signal (Sim default 300m but can be bespoke) then it will not restart until the signal is off.

Peter

I should've been clearer - the situation is:
Kensal Rise Station - GO22 - Brondesbury Park
On the same TC, in that order.

If GO22 is at danger, the train stops at Kensal Rise, departs, and stops at GO22. The issue occurs when GO22 subsequently clears, and the train moves up to stop at Brondesbury Park - on occasion, the train seems to sit there waiting for RA (other times it moves off without issue). The alternative explanation is that I didn't wait long enough...

Edit: Turns out that trains stopping at Brondesbury Park will not move off until GO21, which is half a mile away, has cleared.

I personally think it is working correctly.

Drivers will not depart a station in reality if they have a red in front of them, as this would be a SPAD risk.

I can think of a few exceptions, mainly involving the use of 6 - 6, instead of 2 - 2.

My gut feeling is that even though the signal may be some way from the station, and unsighted? to the driver whilst at a stand in the station, SimSig code sees a train sat in a station with the next signal red and leaves it there accordingly until the signal clears. I may be wrong, but am not aware that there is any programming into signals to say from how far away they can actually be seen?

I personally think it is working correctly.

Drivers will not depart a station in reality if they have a red in front of them, as this would be a SPAD risk.

My gut feeling is that even though the signal may be some way from the station, and unsighted? to the driver whilst at a stand in the station, SimSig code sees a train sat in a station with the next signal red and leaves it there accordingly until the signal clears. I may be wrong, but am not aware that there is any programming into signals to say from how far away they can actually be seen?

"If there is a platform starting signal, or an associated OFF indicator, you must if possible check that the signal is showing a proceed aspect or the OFF indicator is lit before you give the READY-TO-START signal to the driver."

* TS1 4.6.1: If you cannot clear a stop signal, you must not clear any associated signals on the approach to it until the train has stopped or nearly stopped at each signal in turn.

I personally think it is working correctly.

Drivers will not depart a station in reality if they have a red in front of them, as this would be a SPAD risk.

My gut feeling is that even though the signal may be some way from the station, and unsighted? to the driver whilst at a stand in the station, SimSig code sees a train sat in a station with the next signal red and leaves it there accordingly until the signal clears. I may be wrong, but am not aware that there is any programming into signals to say from how far away they can actually be seen?

Not sure if mentioned before but there isnt a timetable included in this sim and I cant one to work help need please thanks in advance

That updated version is a timetable for the NLL paged. The paged sim has a scrolly(or just broken?) timetable included, which don't work well together. The download fixes the issues with the paged sim's timetable.

Loving the NLL scrolly, looks great across my three monitors :)

Question though, what fixes does the winter 2003 v1.1 make over the original one that is supplied with the sim? Does it fix the various trains that call in wrong routes despite the fact they are routed the right way?

For example I had a 4L78 arrive from Acton East Junction to go to to S.W.S, but when routed that way it stopped at AW146 signal to complain. It wouldnt take any other route untill I cancelled its timetable.

Ive also got a 6M12 stopped at GO19 signal at Gospel Oak Jn complaining of a wrong route. The timetable says its booked via Camden and Temple Mills in order to get to Carlton Rd Jn but it refuses any route set from GO19 signal including its booked route.

All in all tho it very nice!