[rickloader]

In the openrailslog.txt are the following lines

TTOutputTimetableFullEvaluation = False
TTOutputTimetableTrainInfo = False
As there is no (userset) it seems this can not be "true" by user options. How can the timetable user enable this please?
Would the "TTOutputTimetableFullEvaluation" give useful information in troubleshooting a timetable?
thanks, rick

[roeter]

Hello Rick,

I fear the options run quite a bit ahead of the actual code.
There are a number of timetable evaluation functions but at present these are coded under Debug flags and therefor not available to general users. The idea is that 'in time' these functions will be accesible through these user options.
But there is no timeline yet as to when that will be.

If you can compile the code it is possible to switch on the debug options. If you are interested, please send me a PM.

Regards,
Rob Roeterdink

[rickloader]

Hi Rob, thanks for your reply and kind offer. However, I don`t yet know how to compile the code, and I don`t want to take up your valuable time. No doubt I could learn to compile, but I`ve promised to share the timetable, and promised dates are slipping!
I wonder though if the tt debug might usefully be enabled through Carlo`s MG version, as this seems to accept a number of experimental options, not on general release.
My timetable became unstable and inconsistent at 250 trains. I am heartened by your debug post showing your timetable at 3000 trains, so I now know that my timetable has scope to be much larger. At the moment I`m reconstructing the timetable, while optimising the route track and signalling. So far so good, but if I run into trouble again, an extended evaluation might be very helpful.
Thanks again, timetable mode gives much enjoyment,
rick