Possible incompatability New night sky map.
#1
Posted 26 October 2017 - 06:44 AM
This suggests that there may be something in the new file which OR doesn't like.
Has anybody else had an equivalent problem, I wonder?
#3
Posted 27 October 2017 - 02:28 AM
Hopefully this will work.
The route is Bob Wirth's Emporia Sub, the rolling stock has Streamlines SD45-2 from the Santa Fe pack (modified to use the sound sourced from the UP Feather River pack) and RTTX cars and Caboose sourced from Trainsim.com (modified as 'Carriage' to permit the train to run at higher speeds). The train is my representation of the 'Super C' which was permitted to run at the higher speeds,
Rob.
Attached File(s)
-
OpenRailsLog.txt (15.26K)
Number of downloads: 186
#4
Posted 27 October 2017 - 03:59 AM
keystoneaholic, on 27 October 2017 - 02:28 AM, said:
Hopefully this will work.
The attached log doesn't have a crash noted in it.
The log file is created every time the Open Rails is run, so if you crash, change something, and then run it again, the crash log is lost. If you still suspect that starmap file, replace it and get it to crash again.
#5
Posted 27 October 2017 - 04:34 AM
Jovet, on 27 October 2017 - 03:59 AM, said:
The log file is created every time the Open Rails is run, so if you crash, change something, and then run it again, the crash log is lost. If you still suspect that starmap file, replace it and get it to crash again.
OK, I'll change the starmap again and see what happens.
#6
Posted 17 November 2017 - 09:39 AM
It does occur to me that this has only started to happen since I changed my video card. My old Radeon HD6670 gave up the ghost and I made the mistake of changing to an Nvidea GT730 (more expensive but lower performance and some OR issues seem to have ensued).
I have got a log file attached for you this time!
Attached File(s)
-
OR Crash Log 17 11 2017.txt (19.84K)
Number of downloads: 187
#7
Posted 17 November 2017 - 03:13 PM
Quote
I notice you have Performance Tuner on. Have you tried running with it off?
regards,
vince
#8
Posted 17 November 2017 - 10:06 PM
I suggest these two extra tests to help determine if the problem is some combination of the star map and where you were running in the route. If things blow up in both of these tests you know for sure it is the star map. If things work then it's a more complex problem.
I downloaded the Emporia Sub a month or so ago and found so many problems (many hundreds, almost all about dynamic track) I was ready to toss it. Fortunately I was refereed by Bob Wirth to a fellow who goes by ChiFan (actual name Chester) who had written some code to deal with the issues I was seeing. Chester sent me an entirely new .tdb, .rdb. local tsection.dat and many changed world files. Things look pretty good after that.
#9
Posted 18 November 2017 - 05:35 AM
The crash log is for the Seligman Sub (Bob Wirth's version) during daylight hours (about 1330 hrs). I suspect that the original problem was not actually related to the sky-dome or the route involved but is related to something else.
The train is the same:-
4 x SD45-2 (Streamlines, one in the Bi-centennial colours, modified to use the sound files from the Feather River UP set)
15 x RTTX flats (ex trainsim) modified to passenger carriages to allow the higher speeds to be made
1 x cabin car (ex trainsim) also modified to passenger carriage for the higher speed
We are talking 'Super C' here.
I'm going to try changing one or two things in a controlled way to see whether I can get to the bottom of it. As nobody else has weighed in with "I've had that happen too" I assume that it's a bit more obscure. It may be related to my specific set-up, though I have made few amendments to OR or the video set up as I tend to leave things I don't really understand well alone.
#10
Posted 18 November 2017 - 09:36 AM
So, as also Vince says, try unchecking the "automatically tune settings to keep performance level" experimental option checkbox. If that is not enough, try returning to 2000 m. viewing distance.