Not a waste of time at all. Some of us also use the testing version of OR, and if something that should work suddenly stops working it's important that it gets reported to the OR development team before an error gets baked in to the code. Thus the questions about what exactly caused the malfunction.
Utah Belt SD40-2 #3099 engine not visible
Collapse
X
-
Two points: First OR does not require a error to create a log file. FYI the Log file comment he is referring to a TXT file OR creates and saves to your desktop. It is not the Windowed Error message that appears on the screen when OR crashes.What I am talking about did not result in an error in the OpenRails program (version 1.6.1), so there was no log file produced.
Because the first engine did not load properly, I found myself looking from the next engine in the consist back down the train.
I would be interested if anyone noticed the same thing. That was the point of my original post. I was not asking for a solution, because I had found one. I was wondering if anyone else had noticed that the engine was missing.
In the .eng file in the OpenRails folder for the engine in question, there is a line — include ( "..\\UB_SD40-2_3099.eng" ).
I changed this to — include ( "..\\UB_SD40-2_3093.eng" ) and then I could see out of the front of engine 3099.
Please try running the activity, and let us know what you see.
Thanks
David
Second it appears that you do not understand alias redirect instructions:
The line in the eng file UB_SD40-2_3099.eng in UB_SD40-2_3099\OpenRails folder which reads "Include ( "..\\UB_SD40-2_3099.eng" )" instructs OR to go to the Parent folder of the current folder and read the file UB_SD40-2_3099.eng
The current folder in this case is .....\Trains\Trainset\\UB_SD40-2_3099\OpenRails.
The Parent folder is .....\Trains\Trainset\\UB_SD40-2_3099
If one changes Include ( "..\\UB_SD40-2_3099.eng" ) to include ( "..\\UB_SD40-2_3093.eng" ) then OR will look in the folder .....\Trains\Trainset\\UB_SD40-2_3099 and will not find a file named UB_SD40-2_3093.eng because that file is in .....\Trains\Trainset\\UB_SD40-2_3093 not .....\Trains\Trainset\\UB_SD40-2_3099.
If the Creator of this loco had wanted to tell OR to read UB_SD40-2_3093.eng the line would have been written this way:
Include ( "..\\..\\UB_SD40-2_3093\\UB_SD40-2_3093.eng" )
But why would he want to do that because IF he DID he would end up with "3093" not " 3099" because the ENG file UB_SD40-2_3093.eng has a FreightAnim ( SD40-2_Parts.S 1 1 ) line and that Parts.s Shape file has an ACE graphic file that has the numbers 3093 not 3099.
The above tells OR to go back to the Grandparent folder, .....\Trains\Trainset then go forward to the UB_SD40-2_3093 folder and read the UB_SD40-2_3093.eng file.CharlesComment
-
Thank you for that lengthy explanation, Charles. I think I have a better understanding now of just what is involved with include files.
DavidComment
-
David,
I just saw what made you think you needed to change 3099 t0 3093. The 3090 loco has the ENG file for 3093 in its OpenRails folder. Looks like 3093 was the original loco and the others were cloned from it BUT the Darkhorse427 forgot to update the OR ENG file in 3090. He said in post #12 an update was forth coming.CharlesComment
-
Yes, it would have been something like that, but I should not have been so hasty in assuming it was an oversight. Too soon old, too late smart.
DavidComment





Comment