OR crashes to menu while trying to load a certain route

[motormaster532]

Actually, I love this. We are first hand taking part in building a major new train simulator, testers if you will. Providing the way to help make it right.
The powers that be are discussing this @ET. Aware of the hiccup and a solution will be found.

You need to be registered to view. http://www.elvastower.com/forums/ind...ost__p__164315

Can't say that about the old MSTS now can you? That is what makes this exciting to me to be part of it . . . and it shows all what goes into making a quality simulator. . . it's hard. . . but there are a LOT of testers and it's gonna' make a great sim!

enjoy!

Actually,I think it is a great Sim already.So far,with the latest Experimental version,I have had no problems at all.Mind you,so far I have only run Conrail Indy,Niagara Corridor and the GTA,and this with my own brand new custom Activities.The only problem is that with the previous recent releases the VIA F40s will not engage the Dynamic Brakes.All of my other power is fine.I reported it as a bug,so lets see what happens.In order to prevent disappointment about not being able to run certain Routes or Activities with updated versions of Open Rails,I usually keep an old version that I know works as a back-up. Brian

[Vince]

I regressed to version X2600 and the PRR is back in business!** Watchdog was implemented in X2601.

**although there is a problem with some incorrect signal aspects, not a show stopper but it throws schedules off.
I looked at some of the problem signals in the Route Editor and did change one to test. I think OR is interpreting the check box for 'UseAdvancedApproach' distant/permissive signals literally, setting them TO advanced approach aspect no matter what track condition ahead may be. I removed checkbox and right about that time I got into this CTD Watchdog problem discussed above. Yikes!

I thought it was me who blew the route up.

It takes my high end machine with SSHD's THIRTY FIVE SECONDS!!! to do a database save when changing the signals. . .
Then I went through the pain restoring from backup . . . then I saw the thread at ET . . . oh well.. it's okay now.

[baldwin]

Actually, watchdog was first seen in 2619, and I am running 2618.
To answer peaches, there is a way to change the watchdog behaviour, but to do so you need to download from the Subversion repository, change a couple of lines in the Watchdog.cs file and compile to get the program run files.

I am intrigued by the texture behaviour though, because with 8 GB of system ram and 4GB of video ram that should not happen. Although thinking on it a bit more, do you have the LAA option ticked. This will increase the amount of system ram the program is allowed to use. It should be there on the General page of Options.

[peaches461999]

I do have the LAA Option set.

[baldwin]

OK. Now, what size are the textures that go missing. How many of the GE textures are in use.

[peaches461999]

OK. Now, what size are the textures that go missing. How many of the GE textures are in use.

Well the textures that go missing are trackside grasses and loco and various random rolling stock. I have approximately 6 DM tiles using GE so far, and have managed to do about 15 regular tiles with GE textures. And this only happens when I try to use earlier versions of OR. Or with Watchdog won't even load the route now. As well as other completed routes that struggled in MSTS. But my route works perfectly fine if I use MSTS. Seems like maybe the wait time parameters within watchdog are too strict. I'd like to see how OR operates now with all the updates that have occurred since the implementation of watchdog, but with watchdog deactivated. Is there anyway that maybe in the main OR menu screen that, in the future, we can toggle off watchdog for bigger and more detailed routes. Seems with my having no issues testing my route in MSTS, but now I do have issues with OR and watchdog, that maybe it's a step backwards if its making larger routes non operative.

[baldwin]

Watchdog was introduced to try and find loading bottlenecks. Perhaps it is too successful at this. The fact that MSTS loads these textures and OR does not suggests that they are indeed having a bad effect on how OR is operating. Thus far I have only seen grey models when OR has actually run out of memory space to display them. There may be another reason for this. If you have not already done so, I suggest joining the Elvas Tower forums and raise this problem there, if possible giving a location to download the route and test engine for someone to look at.

[peaches461999]

Well the route I'm really having problems with is one I'm currently building. And I have a few tiles with payware and freeware scenery. So I cannot upload it anywhere. As I said, the grey textures only show up if I revert to an older version of OR to try to continue testing my route as it progresses. I don't get the grey textures in the latest downloads, but no version of OR with watchdog will load my route. But it functions in MSTS with frame rates in the mid 30s, and if it was a memory issue, msts would be bogged down much lower than that with this route.

I would have to agree with your statement that watchdog is too successful with the bottlenecks. It needs to allow these bigger routes the proper time to get loaded.

[baldwin]

MSTS is very much a closed book far as how things work, so the OR dev team has had to make some inspired guesses in some areas. MSTS bogs down in the FPS department because it runs on the CPU. The GPU only used to display the results.

Open Rails uses both the CPU and the GPU for calculations, so texture display can be affected if the memory space used to hold them is too small. The space used depends on the texture size. The bigger the texture the bigger the space required. Space used up, no more textures displayed. I had to downgrade some 2048x2048 to 1024x1024 to avoid the grey look.

The texture load will also be dependent of how big your view radius is. I now use 15 tiles which is ample for track level views.

[peaches461999]

from what I've been able to tell, I've never exceeded 3.5 gb of memory. And I bought a rather beefy GPU for this computer.

[peaches461999]

Is there a way I can change the watchdog parameters here just for my system? And if there is what exactly would I need to change within watchdog, to be able to give more advanced routes more time to load up. Because currently, the times watchdog is giving routes to load before it terminates the route loading is a major step backwards and is pushing me back into the 13 year old program that does run more advanced routes.

[erielackawanna]

Hello,

Perhaps I wasn't paying that much attention to the time it takes OR releases to load routes. However, I am noticing that recently it has been taking OR 2618 a lot longer to load larger routes, i.e the route project I am involved in and the PRR Eastern Route. Moreover I am noticing that the gray loading bar often disappears while OR attempts to load the route while the route loading screen displays for a couple of seconds longer. This issue does not occur with the smaller size routes I tested. In regards to smaller size routes, the gray loading bar seems to finish moving across the screen simultaneously as OR displays the route. The gray loading bar seems to be out of sync with the loading of larger routes.

Because currently, the times watchdog is giving routes to load before it terminates the route loading is a major step backwards and is pushing me back into the 13 year old program that does run more advanced routes.

I am confident that the OR team will be able to resolve the issue of post-OR 2618 releases preventing larger routes from running.

[90hd]

Open rails crash to desktop

Hello,

Perhaps I wasn't paying that much attention to the time it takes OR releases to load routes. However, I am noticing that recently it has been taking OR 2618 a lot longer to load larger routes, i.e the route project I am involved in and the PRR Eastern Route. Moreover I am noticing that the gray loading bar often disappears while OR attempts to load the route while the route loading screen displays for a couple of seconds longer. This issue does not occur with the smaller size routes I tested. In regards to smaller size routes, the gray loading bar seems to finish moving across the screen simultaneously as OR displays the route. The gray loading bar seems to be out of sync with the loading of larger routes.



I am confident that the OR team will be able to resolve the issue of post-OR 2618 releases preventing larger routes from running.

Ok Openrails experimental 2629 is working properly, give it a try all my routes that didn"t work are working now..........

[roeter]

In version 2629, the watchdog time-out time is extended from 10 to 60 secs.
In version 2631, watchdog 'pings' have been added to a number of long loops which can occur during the start-up process.
This should restore proper working for all routes, also in timetable mode.

Regards,
Rob Roeterdink

[erielackawanna]

Hello,

Testing the route project I am involved in and the PRR Eastern Region Route using OR v2634, OR crashes to the menu when trying to load these routes. OR can run these routes in v2629.