[slipperman]

Hi,
A fellow simmer is running the Paddington to Penzance route under the Stable v1.5.1. At a certain point in the route, Open Rails 'stops' - I don't have full details of exactly what happens, but have attached the log file.

I have run the same version of the route (2.5) on my PC using OR versions Stable v1.5.1, Testing v1.5.1-376 and ORNYMG 139 without any such problem, so it seems that it might be an issue with that member's Open Rails setup. Hoping that the cause of the error can be established :)

Cheers,
Ged

Attached File(s)

•  OpenRailsLog-P2P-151-Paul.txt (19.86K)
  Number of downloads: 84

[engmod]

Hi Ged,

>Warning: Unexpected end of file in C:\1MSTS\ROUTES\GWR\WORLD\w-006281+014867.w:line 112

If your install runs clean, then I suggest your friend has a corrupt install.

[slipperman]

Hi Derek,
Many thanks for your reply.
When I run the same path, I get that message in the log, but the final Xna error message isn't displayed. I, therefore, discounted that, and the other .w file errors reported, as the cause of the failure.

Cheers,
Ged

[engmod]

Hi Ged,

The problem starts here:-

>Warning: Unexpected end of file in C:\1MSTS\ROUTES\GWR\WORLD\w-006281+014867.w:line 112

A close brace is found where it should not be.

The other errors cascade from here.

[slipperman]

Hi Derek,
I understand what you're saying, but I get the same World file errors but not the final Xna error.

Over the next couple of days, I will attempt to fix the World file errors, but why don't I get the Xna error??

Cheers,
Ged

[slipperman]

Hi,
I located the problem with World File 006281+14867. A Static entry had double double-quotes around a file name. Replacing each a single double-quotes eliminated the error message from the log.

I have submitted the revised World file to the original user and requested that he rerun the same path and consist, then report back as to whether the Xna error recurred, or not.

Cheers,
Ged

[slipperman]

Hi Derek,
Many thanks :)
I am advised by the other user that he has now run several times through the 'affected' area with no repeat of the crash.

But, I cannot understand why I didn't get the same error reported although the same World file error was reported in my log?
It seems unlikely but could it be because he is running Windows 10 Home and I am using Win 10 Pro?

Cheers,
Ged

[engmod]

Hi Ged,

The only error that means anything is the very first one.
That must be fixed first, then see what happens.

Other errors that come up are incidental and not reliable.

win 10 home and pro are the same code base as shown by the updates being the same.
The only differences are small registry changes.

[Genma Saotome]

I'm rather surprised there was any quotes. Are there odd characters in the file name?

[slipperman]

Hi Dave,
The file name contains a space - FileName ( "Bracket 180.s" ).

Cheers,
Ged