I'm running the Northeast Corridor 4 route in Explore mode with the default Acela Express trainset. I'm in full-screen mode. Starting at Philadelphia 30th Street Station, I can run for a minute or two until the mainline opens up near Darby, and Open Rails freezes totally. I'm not operating any controls at the moment. No errors pop up; the sounds continue normally. If I Alt-Tab out and back, I can get the mouse cursor and click, which causes the Windows message to pop up that the Open Rails Activity Runner has stopped running and I can exit. (Fast Alt-Tab switching option must be turned on, or Alt-Tab won't even work; the whole interface locks up -- no mouse, no keyboard at all.) Nothing significant appears in the log that I can see. I tried different trains and get the same result at the same location.
Then I tried something else -- I switched to windowed mode. Same route, still in Explore Mode, back in the default Acela, starting from the same location. This time, I can go far past where the freeze happened. I got all the way to Wilmington and a little beyond, and then the freeze kicked in same as before. This time, there was a bit more in the log, but I can't make much out from it if it's relevant to the freeze or not.
I'm attaching two sample logs, one from when the freeze hits early in fullscreen modeand the other from when it hits much further down the line when I'm in windowed mode. Not sure if this is more of an issue with the route or if it's something in Open Rails?
Attached File(s)
-
OpenRailsLog - Fullscreen mode.txt (8.68K)
Number of downloads: 197 -
OpenRailsLog - Windowed mode.txt (14.3K)
Number of downloads: 180