ORTS.Processes.ThreadHangException at ORTS.Signals.BuildSignalList (1.0.1.3095, Trat 321)

[jm252485]

Selected route is very complex - cca 2000 km. In original MSTS runs without any problems.
Installation OR was done on "clean" computer - system disc "C" was formatted (NTFS) and installed fresh copy of Win7 64 (with automatic uptades incl. SP1) In next step there were installed ATI HD4870 latest drivers downloaded directly from AMD.
There are no other complex program files (eg. Qffice etc.), only WinRar, VLC player (both for Win 64) and system files

.NET Framework is used from Windows installation (not patched)
XNA framework was installed from OR installer and not patched.

[Carlo Santucci (carlosanit1)]

The computer is too slow loading the route, therefore the watchdog is triggered and returns the program to the menu.

[jm252485 (mayer-jindrich)]

I am not sure - this route is built for 10 years and has 26 updates. The problem started from update 18, which add to route only cca 30 km (from cca 1700 to 1730). From this update till the last one (26) was added cca 300 km.
I can also run the othe very long route (also cca 1800km) called Breclav-Praha and this one runs OK wiht 40-50 FPS. Object density is comparable.

But - I tested my "probematic" route also on notebook (Lenovo with quad-core Intel, 4GB RAM nVidia separate graphic card, Win 7 Enterprise 64 bit) and runs OK up to 70 FPS.

Is there any posiibility how to make the critical time for "watchdog" longer ? (some command-line parameter ?)

[jm252485 (mayer-jindrich)]

Carlos wrote:
The computer is too slow loading the route, therefore the watchdog is triggered and returns the program to the menu.

So - I did PC upgrade: AMD X4 860 K processor, 8 GB RAM, new ASUS A88 board, GPU is the same (HD 4870). New Win7 64 bit installation. Result: the same error.

Additional testing on Dell - Intel i5 with integrated GPU. Runs "OK" (with 30-40FPS).

Maybe the problem is in AMD x Intel incompatibilty?