[jdgremsjr]

I just updated from 3983 to 3991 and now I can't run any activities. The Explore mode and in Explore in Activity mode all works fine. But I've tried 5 activities on five different routes and they have all crashed during Startup. I have saved the logs from three of the routes and have posted them below.


 OpenRailsLog.txt (19.28K)
Number of downloads: 180
 OpenRailsLog1.txt (14.55K)
Number of downloads: 189
 OpenRailsLog2.txt (14.23K)
Number of downloads: 189

[slipperman]

Hi,
It might have nothing to do with it, but why have you got DistantMountainsViewingDistance set to 1000000 (ie 1000 km)? The default appears to be 40km.

Cheers,
Ged

[jdgremsjr]

slipperman, on 27 November 2017 - 10:28 AM, said:

Hi,
It might have nothing to do with it, but why have you got DistantMountainsViewingDistance set to 1000000 (ie 1000 km)? The default appears to be 40km.

Cheers,
Ged

I turned off the distant mountains and it still crashed. I thought that as well

[vince]

I see from the log you posted that you have Data Logger set to true! Logging & Data Logger are two different operations.

The OR Log is enabled by a checkbox on the OR opening screen.
The Data Logger is a different log and is set on the Data Logger Options Tab and carries this warning:

Use Data Logger to record your simulation data ( In-game command F12.)
Please remember that the size of the dump file grows with the simulation time!

As per the warning, running with DATA LOGGER on will soon overwhelm your systems memory . . . The dump size gets bigger with runtime. Ouch!
Try running with NO Data Logger but just have LOGGING set on the OR opening screen. [emphasis added]

regards,
vince

ps. If my reading of the log is in error, please correct me as I am learning too. Thanks.

[jdgremsjr]

vince, on 27 November 2017 - 11:14 AM, said:

I see from the log you posted that you have Data Logger set to true! Logging & Data Logger are two different operations.

The OR Log is enabled by a checkbox on the OR opening screen.
The Data Logger is a different log and is set on the Data Logger Options Tab and carries this warning:

Use Data Logger to record your simulation data ( In-game command F12.)
Please remember that the size of the dump file grows with the simulation time!

As per the warning, running with DATA LOGGER on will soon overwhelm your systems memory . . . The dump size gets bigger with runtime. Ouch!
Try running with NO Data Logger but just have LOGGING set on the OR opening screen. [emphasis added]

regards,
vince

ps. If my reading of the log is in error, please correct me as I am learning too. Thanks.

Just tried what you mentioned, I unchecked all the logging in the data logging tab and it still crashed.

 OpenRailsLog.txt (16.45K)
Number of downloads: 176

[jdgremsjr]

I am going to download a clean version of 3989 and update it to 3991 and see if there is an old patch that is messing with it.

[Csantucci]

X.3991 has a bug. Don't use it and stay to x.3990.

[James Ross]

jdgremsjr, on 27 November 2017 - 07:29 AM, said:

I just updated from 3983 to 3991 and now I can't run any activities. The Explore mode and in Explore in Activity mode all works fine. But I've tried 5 activities on five different routes and they have all crashed during Startup. I have saved the logs from three of the routes and have posted them below.

It's not all activities, but there was a problem with certain data missing in some activities. It's fixed in X3992.

[jdgremsjr]

Csantucci, James Ross;

Thank you for your responses, it is what I figured, a bug. I've reverted back to X.3989 and will wait for X.3992 to become available. Again thank you for all your hard work and developing such a great program and distributing it for free.

[vince]

jdgremsjr, on 27 November 2017 - 11:38 AM, said:

I am going to download a clean version of 3989 and update it to 3991 and see if there is an old patch that is messing with it.

Okay, one thing tried ...no help. But wait . . . there's more . . .
I see also you have UseMSTSEnv set on. Well I'm not too sure about this but I do remember that the one time I tried OR with the UseMSTSEnv option set to ON it gave me trouble. Try running with that option un-checked.

Also I see you have PreferDDSTexture = (user set) True while you also have UseLargeAddressAware = (user set) False. Any particular reason for this?
Running OR can be improved with LAA set true but AFAIK there are no routes presently using DDS textures.
So these options as set provide no hope of improvement at all. . . . I could be wrong about no routes use DDS textures. But the LAA option provided much improved running on my machine. You see where I'm going with this . . . maybe you can speed up the process;

Setup OR with all Options set at default and then try running.

If that still crashes try running a default ugly Dash 9 w/default rolling stock as that engine you're using seems to have problems of which I'm not familiar.
Trying to figure out what's causing an error on a program that's in development (OR) should NOT be tested with anything but known good running rolling stock. Go for a like engine that is known good and doesn't throw hundreds of error warnings at you.

regards,
vince