The Open Rails Log file is giving many errors of the form"
Warning: Expected end of file in C:\2MSTS\MSTSmini\Chiltern\Train Simulator\ROUTES\Chiltern\WORLD\w-006101+014939.w:line 12
The file in this example is very short and reads:
SIMISA@@@@@@@@@@JINX0w0t______
Tr_Worldfile (
Static (
UiD ( 680 )
FileName ( gwr_milepost_4i.s )
Position ( -636.325 80.5 1014.33 )
QDirection ( 0 -0.505662 0 0.862732 )
VDbId ( 4294967295 )
StaticDetailLevel ( 0 )
)
)
_Skip ( "TS DB-Utility - Version: 3.4.05(13.10.2009), Filetype='World', Copyright © 2003-2009 by ...CarlosHR..." )
As you will see there error is caused by "TS DB-Utility" adding information after the end of the file. The full log file is also attached. Can anything be done to suppress these error reports?
Page 1 of 1
"Expected end of file" Error
#2
Posted 12 December 2019 - 09:20 AM
You can remove the offending lines -- unzip all the w files, then use a Search Replace tool to wipe out the line, rezip the files.
Perhaps, OR should be coded to ignore lines outside of the end bracket on world files...
Perhaps, OR should be coded to ignore lines outside of the end bracket on world files...
#3
Posted 12 December 2019 - 01:35 PM
I think this was actually done a long time ago, but the problem has appeared again.
#4
Posted 17 December 2019 - 03:03 AM
Can this patch be reinstated or must I manually edit hundreds of .w files to remove this TD-DB comment?
#5
Posted 17 December 2019 - 12:43 PM
IIRC this code was added by Jeffery Kraus (Yeo) -- a.k.a. Voldemort -- when he was (briefly) part of the OR team. He had a fixation on his opinion (a default occurrence) that nothing beyond what MSTS should ever be part of OR and wrote a series of tests that threw errors on the discovery of anything he deemed inappropriate. For example, because MSTS would abort when confronted with a non-textured face he regarded OR's application of a neutral gray texture as wrong and wrote code that would throw an error.
Why ANY of that code has been retained is simply beyond my understanding. It should have been removed years ago. At any rate there is (or least there was) a toggle somewhere in the options tabs that allowed you to suppress this sort of nonsense.
Why ANY of that code has been retained is simply beyond my understanding. It should have been removed years ago. At any rate there is (or least there was) a toggle somewhere in the options tabs that allowed you to suppress this sort of nonsense.
Page 1 of 1