[delay]

Hello i download new updates and i have problem, route loading error.

Attached File(s)

•  OpenRailsLog.txt (13.14K)
  Number of downloads: 251

[engmod]

What version of tsection are you using?

[delay]

how do I find out ?

[Paul Pal]

engmod, on 02 November 2014 - 01:15 AM, said:

What version of tsection are you using?

I did not know that tsection version could impact so much. What versions should we use / not use ?
Tks

[copperpen]

I don't think that the tsection has anything to do with the problem. The loader process has been modified and it is the loader process that is the cause of the program not loading. It may be the new Watchdog process that is causing this though.

[JohnnyS]

engmod, on 02 November 2014 - 01:15 AM, said:

What version of tsection are you using?

The global for Trat321 uses tsection build 0027. Though like Copperpen I think this may be irrelevant.

delay said:

how do I find out ?

Open the tsection.dat with a text editor. The build number is shown near the top of the file.

[engmod]

delay, on 02 November 2014 - 01:19 AM, said:

how do I find out ?

In the train simulator\global directory the tsection.dat file is there.
It is a text file, open with any editor (notepad or wordpad), the version number is at the top.
Also give me the date of the file.

cheers
Derek

[disc]

I have the same problem on bigger routes, the game simply don't waits for loading, just quits with "hung" exception, while the loading bar is moving in every second.

tsection

_INFO ( Build 00038 )
_INFO ( verze UZK - 3.20 )
_INFO ( verze TSection.dat - 3.20 )

[Csantucci]

I and other people have an other problem since release 2619: after some seconds of route loading, the loading is interrupted and ORTS returns to the menu window. A subsequent load attempt sometimes has success, and sometimes again returns to menu. After some trials the route gets loaded.

Trying to load to instances of OR to make some MP tests, the second instance continues to return to the menu. I can't use it.

[engmod]

JohnnyS, on 02 November 2014 - 04:13 AM, said:

The global for Trat321 uses tsection build 0027

I would agree that its not the primary cause, but build 0027 is a VERY early build.
If possible everyone should be using the latest build 0044.

Build 0044 is friendly to the British routes just like build 0038.

For Trat321, just check that the author is not using a non standard Tsection.

cheers

[Csantucci]

Csantucci, on 02 November 2014 - 09:00 AM, said:

I and other people have an other problem since release 2619: after some seconds of route loading, the loading is interrupted and ORTS returns to the menu window. A subsequent load attempt sometimes has success, and sometimes again returns to menu. After some trials the route gets loaded.

Trying to load to instances of OR to make some MP tests, the second instance continues to return to the menu. I can't use it.

I had to increase the timeout time to have things loading regularly. I increased it to 40 seconds. Maybe 20 are enough. I kindly ask James to increase such value.

[eugenR]

Csantucci, on 03 November 2014 - 06:22 AM, said:

I had to increase the timeout time to have things loading regularly. I increased it to 40 seconds. Maybe 20 are enough. I kindly ask James to increase such value.

I has the same Problem with DVZO, this route has heavy KI-Trafic.
about 36 Trains scheduled in the 1/2 Hour before the Player Train start, about 300 KI-Trains programmed from 00:00 to 16:00.
If I start the activities without KI-Trafic, there is no error.

[disc]

commit 2623 did'n helped, just makes the game quit much faster. (5 seconds after loading started)

[Csantucci]

Neither was the problem solved for me. There can be more than one cause slowing down initial load of game. Many AI trains are only one of the causes.
Frankly speaking, to me the watchdog during initial load of game is more a problem than the solution of a problem, and I would remove it, also thinking at people with slow computers. After initial load I don't know yet.

[roeter]

The watchdog feature blocks the start of timetables for medium or large routes.
It seems that the various processes do not respond to the watchdog during the initial load process.
The major timetable I am using at the moment has about 1500 trains using about 400 different paths. The loading of the those paths takes quite a bit longer than 10 seconds - it actually takes several minutes. I set the time-out to 100 seconds but it still crashes.

This watchdog feature should be started only after the initial load. I can't tell if it works during the pre-run phase - it could well be that certain processes do not run frequently during the pre-run phase, for instance the display thread has no work during this phase. With the present set-up I can't even reach that phase.
With 10 sec. time-out I can't get through the signal initiation, with 100 sec. time-out the program crashes during path loading.

Regards,
Rob Roeterdink