New error function in TSRE

[GokuMK]

After fixing these sigcfg errors mentioned above, everything seems to work fine in your route. Error list is very short.

[Vince]

Thanks for that.
Would it be possible to have the error function display the reason TSRE would not load the sigcfg.dat file?
Something like: 'ERROR IN SIGCFG line nnn'

I did review the TSRE log.txt file line by line last night . . .took a while (900KB) but while I did see some [I] items in there about undefined token in sigcfg but nothing firm about the errors you found deep in the sigcfg.dat file. HOW you found those errors is what has got my curiosity up????

Looking through the file looking for typographical errors is VERY hard so how'd you find them?
Much thanks for your continuing work with your editor.

best regards,

[GokuMK]

I use TSRE source code, so I can adjust it to find these errors.
I think that OR log shows good info about sigcfg file errors.

[mnowosad]

Hello . Taking advantage of my free time at Independence Day in Poland, I allowed myself to correct the sigcfg.dat file and the PRR_EAST_REG-2 route using the new TSRE5_v0.699 Tools / Error & Messages function. Most of TSRE5 bugs fixed automatically, manually removed levitating objects like "Object seems to be located too far from it's Tile. -Xxxxx -xxxxx". I am sending the link to the patch file - please test on a copy of the route. Greetings, Marek

https://mega.nz/file/acAlnSAB#xHxAtUnI8u4WhJLzFonsiZWxf9xp1nKOvDCK6x-PaCY

Object too far.jpg
Object too far2.jpg
prr_east no errors.jpg
Open Rails 2020-11-11 07-46-02.jpg
Open Rails 2020-11-11 08-40-40.jpg

[Vince]

Thank you.
I will wait for Goku's approval of this patch.

regards,

[GokuMK]

Check it by yourself. I'm not going to do it.

[Vince]

Sorry Goku but the only 'patches' I would consider must come from you or approved by you.
I've already found the part of the error fix routing does indeed fix these "too far from tile" errors very well.

regards,
vince

[gusthegator]

Bug is inside your sigcfg file, here:



And here:



And here:



And the same kind of errors here too: CLV3LightPermissiveA

TSRE fails to load sigcfg file, so it thinks that all your signals are broken.

Check your files first before reporting TSRE bug.

Before this fix, executable version 0.6952 bypassed those sigdat errors and signals loaded in properly. Until I saw this forum post. That was a goto for editing signals on the PRR. Thought outdated at this point, it works for the PRRbeta aswell.

[GokuMK]

Before this fix, executable version 0.6952 bypassed those sigdat errors and signals loaded in properly

Older TSRE versions didn't load sigcfg file completely, so these broken entries were skipped.

[gusthegator]

Older TSRE versions didn't load sigcfg file completely, so these broken entries were skipped.

That explains why some signals never showed. I've looked over my sigdat files more closely. Many errors have been fixed since then. Keep up the good work on this editor Goku.

[eric]

Does this error function only work on signals? I've yet to see anything appear in the window, and enabled the two settings mentioned earlier.

[rdayt]

If you enable both settings TSRE goes ahead and does the repairs when you open it. Hence the name Autofix.
It you want to see the errors first you leave Autofix commented out.

[dforrestc]

If you enable both settings TSRE goes ahead and does the repairs when you open it. Hence the name Autofix.
It you want to see the errors first you leave Autofix commented out.

.... or choose not to save the fixes when closing TSRE5.