Unclear error in OpenRailsLog.txt

[Hannes44]

Please could someone in the know clarify what's the problem here -

Thank you in advance.


From the OpenRailsLog.txt:


Information: Expected block terrain_texslot; got error in C:\MSTS-Strecken\Pyhrnbahn\ROUTES\Steyrtalbahn\TILES\-11E0E704.t:byte 9484

Warning: Expected end of block terrain_texslots; got more data in C:\MSTS-Strecken\Pyhrnbahn\ROUTES\Steyrtalbahn\TILES\-11E0E704.t:byte 29394

Warning: Remaining Bytes overflow in C:\MSTS-Strecken\Pyhrnbahn\ROUTES\Steyrtalbahn\TILES\-11E0E704.t:byte 29394

Warning: Expected end of block terrain_shader; got more data in C:\MSTS-Strecken\Pyhrnbahn\ROUTES\Steyrtalbahn\TILES\-11E0E704.t:byte 29394

Warning: Expected end of block terrain_shaders; got more data in C:\MSTS-Strecken\Pyhrnbahn\ROUTES\Steyrtalbahn\TILES\-11E0E704.t:byte 29394

Warning: Expected end of block terrain; got more data in C:\MSTS-Strecken\Pyhrnbahn\ROUTES\Steyrtalbahn\TILES\-11E0E704.t:byte 29394

Warning: System.IO.FileLoadException: C:\MSTS-Strecken\Pyhrnbahn\ROUTES\Steyrtalbahn\TILES\-11E0E704.t ---> System.IO.EndOfStreamException: Über das Ende des Streams hinaus kann nicht gelesen werden.
bei System.IO.__Error.EndOfFile()
bei System.IO.BinaryReader.FillBuffer(Int32 numBytes)
bei System.IO.BinaryReader.ReadUInt16()
bei Orts.Parsers.Msts.BinaryBlockReader.ReadSubBlock() in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\Orts.Parsers.Msts\SBR.cs :Zeile 438.
bei Orts.Formats.Msts.terrain_shader..ctor(SBR block) in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\Orts.Formats.Msts\Terrai nFile.cs:Zeile 275.
bei Orts.Formats.Msts.terrain..ctor(SBR block) in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\Orts.Formats.Msts\Terrai nFile.cs:Zeile 75.
bei Orts.Formats.Msts.TerrainFile..ctor(String filename) in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\Orts.Formats.Msts\Terrai nFile.cs:Zeile 305.
bei Orts.Viewer3D.Tile..ctor(String filePath, Int32 tileX, Int32 tileZ, Zoom zoom, Boolean visible) in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\RunActivity\Viewer3D\Til es.cs:Zeile 373.
bei Orts.Common.ORTraceListener.TraceEvent(TraceEventC ache eventCache, String source, TraceEventType eventType, Int32 id, String format, Object[] args) in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\Orts.Simulation\Common\E rrorLogger.cs:Zeile 123.
bei System.Diagnostics.TraceInternal.TraceEvent(TraceE ventType eventType, Int32 id, String format, Object[] args)
bei System.Diagnostics.Trace.TraceWarning(String format, Object[] args)
bei Orts.Common.ORTraceListener.WriteLine(Object o) in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\Orts.Simulation\Common\E rrorLogger.cs:Zeile 208.
bei System.Diagnostics.TraceInternal.WriteLine(Object value)
bei System.Diagnostics.Trace.WriteLine(Object value)
bei Orts.Viewer3D.Tile..ctor(String filePath, Int32 tileX, Int32 tileZ, Zoom zoom, Boolean visible) in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\RunActivity\Viewer3D\Til es.cs:Zeile 377.
bei Orts.Viewer3D.TileManager.Load(Int32 tileX, Int32 tileZ, Boolean visible) in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\RunActivity\Viewer3D\Til es.cs:Zeile 84.
bei Orts.Viewer3D.TerrainViewer.Load() in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\RunActivity\Viewer3D\Ter rain.cs:Zeile 74.
bei Orts.Viewer3D.World.Load() in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\RunActivity\Viewer3D\Wor ld.cs:Zeile 84.
bei Orts.Viewer3D.Viewer.Load() in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\RunActivity\Viewer3D\Vie wer.cs:Zeile 564.
bei Orts.Viewer3D.Processes.GameStateViewer3D.Load() in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\RunActivity\Viewer3D\Pro cesses\GameStateViewer3D.cs:Zeile 127.
bei Orts.Viewer3D.Processes.LoaderProcess.Load() in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\RunActivity\Viewer3D\Pro cesses\LoaderProcess.cs:Zeile 158.
bei Orts.Viewer3D.Processes.LoaderProcess.DoLoad() in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\RunActivity\Viewer3D\Pro cesses\LoaderProcess.cs:Zeile 138.
bei Orts.Viewer3D.Processes.LoaderProcess.LoaderThread () in e:\Documents\Coding\Jenkins\jobs\Open Rails Unstable\workspace\Source\RunActivity\Viewer3D\Pro cesses\LoaderProcess.cs:Zeile 109.
bei System.Threading.ThreadHelper.ThreadStart_Context( Object state)
bei System.Threading.ExecutionContext.Run(ExecutionCon text executionContext, ContextCallback callback, Object state)
bei System.Threading.ThreadHelper.ThreadStart()


And some more similar warnings....

[longiron]

The only thing I can think of is - the tiles are not subdivided. OR cannot read tiles that are not fully divided into 256 patches. If you don't get a response, I can repost over at ET if you aren't a member.
chris

[Vince]

Running the Route_Riter TsUtils [ICHK] test should help you solve the problem.

[Hannes44]

Thanks for your answers. @vince problem is, I never got route riter to run correctly on my system. I've read countless posts and tried every suggestion I found. Still got the java error and TSUtils don't work either.

[slipperman]

Hi Hannes44,
Although it might be already well-known by others, a recent discovery I've made is that Route_Riter WILL work with only the 64-bit version of Java installed, as long as the specified 'classes' folder is created and populated.

This is with Mike Simpson's final version (v7.6.26) running under Windows 7 Home Premium 64-bit with Java v1.8.0_73

Cheers,
Ged

EDIT : i) Correction to Java version and ii) the same configuration works correctly under Windows 10 Pro 64-bit

[Hannes44]

Hurrah!


Thanks @ slipperman. Route-Riter finally works on my system. It was the 64-bit Java that did it. Next problem: ICHK doesn't check very much, it stops and there is an error roughly translated: route definition ends with a '+' (line=0)another line is missing. Route definition faulty -> Function exit!

What is a route-definition and where can I fix this error?

[slipperman]

Hi Hannes44,
It's in the route's .trk file, probably the Description entry. Each line must end with '+' if there is a following line; the error seems to imply that a line ends with a '+' but there isn't a following line! If that's the case, just delete the '+' and you should be OK.

Cheers,
Ged

[Hannes44]

Thanks slipperman. There wasn't a description at all only two "". Now I inserted one word and Route Riter is checking my route with lots of remarks and infos I'll have to digest for now.

[Hannes44]

I have run Route Riter, corrected the relevant faults but the problem is obviously persistent. @longiron: Please could you repost at Elvas Tower? Also I have no idea, what to do about a tile that is not fully divided into 256 patches and how to detect this fault.

[Vince]

You must use the Route Geometry Extractor (RGE) to fix the undivided tiles.

The RGE Help section has very good step by step instructions on how to do this.
regards,

[Hannes44]

MSTS and the MSTS Editors don't work on my computer

[Vince]

What program did you use to extract the route in the first place?
regards

[Hannes44]

That route goes a long way back. 7, 8 years ago i started it with MSTS editor. After some horrible crashes of the RE I lost interest and with windows 8 on my computer neither MSTS nor the editors worked in a tolerable way. everything was sluggish, horrible graphic quality etc.
Then came OR and it renewed my interest in train-simming and when Goku released his TSRE I blew the spiderwebs from my old routes and began building again. So I know the main problem is probably that there are still remainders of the MSTSEditor crashes hidden in the route, maybe I should start afresh......

[Vince]

Using a route editor that is still very early in development would not be a very safe way to go unless you have ALL tools on hand.
I tried it to add a single sub-tile to my LIRR route but was unable to do so.

Running the proper tests after every editing session to prevent errors creeping in is a safe method. I still do that every day.
You say:

"..., maybe I should start afresh......"

Well then you'd have to use the editors, yes?

I'd respectfully suggest you install MSTS and get the editors working.
When you have a problem simply post a description in the forum and I or one of the other members will assist you.

What tests did you run under Route_Riter?
regards,

[Hannes44]

When I said starting anew, I meant drop the project and wait for fully functioning route editor for OR. As I stated before, I tried for a long time to get the MSTS-RE working in a proper way with all the hints and suggestions one can find on the web, but it didn't work for me. Additionally I have the impression that the MSTS-RE is not much more developed and safer to use than Goku's editor is now.

I did the ICHK test and CLRDB. Btw. the latter rewrote *.w files in a way OR doesn't like very much. The added _skip line at the bottom is obviously irritating OR.