New NAVS EMD645 package question

[qballbandit]

I hate being this guy. I have looked this over a dozen times since yesterday morning and thought I had it installed correctly.
I can get the sounds working fine, but when I add the physics/include statement into the .eng file, MG barfs.
Is this the correct path for these entries?: C:\AAA MSTS Main Directory New\TRAINS\TRAINSET\NAVS_AUDIO\EMD_8_16-645E\physics
If so, is there something with MG that might be an issue vs. OR?
If not, than I am an idiot, because I thought I knew how to read

Thanks!!

[yellowdog]

I had the same issue with the 16-645E3 set, so I haven't even tried to do the new set uploaded a few days ago. Doing this part of the instructions causes MG to crash:

1. Open the locomotive's ENG file and navigate to the end.
2. Locate the "Name" entry. This is typically after a "sound" entry and just before the "description" entry.
3. Create a space under the "Name" entry. Now paste ONE of these TWELVE available include statements into the ENG file at this location

[CSRX]

I don't run MG, but I know the sound set and include files work well in ORTS v1.5.1, I guess as a beta tester of this set, I should have tested in the other versions of ORTS as well.. Leason learned.

[qballbandit]

That's a shame if not MG compatible. I use NAVS 16-645e3_ta_rev1 set for SD40s/GP40s and really like them a lot. There are include files, but the folder path logic is a bit different than this new set.

[Erick_Cantu]

Your path is incorrect. It is a relative path, just like a cab view alias path. The include statements are meant to be copied verbatim and left unmodified. You should not specify a drive letter, trainset folder directory, or anything else, just copy the include statement as-is. MG does not handle include statements differently then the other branches of OR to the best of my understanding. Here is an example:

Include physics.jpg

With that said, if your locomotive's ENG file already has an OR diesel engine block, you will probably need to overwrite its data with the data from one of the include files. The reason the directions state to add the include statement near the end of the file is because OR will always read the final block of data when there are duplicates, and typically there is nothing after the name but operating procedures.

The folder path logic is the exact same as the 16-645E3 set, the only difference is the include files point to a different folder.

[qballbandit]

Understood Erick, I just copied the path from the top of Explorer - my path, I believe is fine.
I do copy/paste from your read-me right to under the "name" line in the .eng file.

[Erick_Cantu]

I gotcha. In that case, yes, you have installed the files correctly.

I wonder if it might be a MG bug, although it seems strange that you don't have issues with the turbocharged 645 sounds since they use the same format in the include files (again, the only difference is the file path). I wonder if you might want to see if Carlo can investigate? Also, are you retrofitting a locomotive with OR physics or MSTS physics? I don't know if the sim might throw a fit if you try to overwrite an ORTSDieselEngines block with another ORTSDieselEngines block. I modified several of Tyler's locomotives, but I copied and pasted the whole block into his OR physics files for this.

Posting the log would go a long way towards diagnosis. I just tested the retrofit I posted above in the latest MG version and had no issues.

[dcarleton]

If you're 'repowering' one of the recent Trainsimulations units which use include files, the OR diesel engine block in the TS include file will likely conflict with EMD_645E.inc file. (That's what happened when I tried it.) However, the TS inc file which contains the OR Diesel Engine Block data also includes 62/15 tractive force data. So, if you try to replace the TS include file with the EMD_645E include file, you likely still would not have a complete engine.

[uli2]

In the ReadMe of the new sound set it says: "[...] For your locomotive, you will need to find the appropriate include statement from this list, then paste it near the end of the locomotive's ENG file (a good location is right above the "Name ( )" field). [...]"

In my case (an older SLI GP38-2 ENG file) "right above the "Name" field" means between the cab sound line and the name line. I copied the include statemennt to that place and it works fine in different OR versions, including MG 136.

I tried moving the include statement to right under the name line and that also worked.

[Erick_Cantu]

if you try to replace the TS include file with the EMD_645E include file, you likely still would not have a complete engine.

Correct; my include files only include an ORTSDieselEngines block to implement the corrected max and min RPM values and throttle tables to control the output RPM at each power setting. In that specific case, you'd be better off copying the data from one of the new include files and overwriting whatever is in the TS include file.

[yellowdog]

I tried it with Tyler Bundy's SD40s, as I have a lot of those on my system. They do have OR eng files, so maybe that's the issue? I have used the 567_1.2 set successfully, but they don't have the same inc setup. Anyway, attached is a log file after a crash from trying to use the 16-645E3_TA_REV1 set. Adding the include statement causes the crash. Removing it results in no crash. MG 150.3

OpenRailsLog.txt

[Erick_Cantu]

That's probably the issue. You would need to overwrite the ORTSDieselEngines block in his OR include files with the data from my include files. Bear in mind that the main reason I develop sounds is for current and future projects of mine, and the directions for the retrofit physics files are largely intended for retrofitting MSTS physics since the vast majority of existing content does not use OR physics. The few models with OR physics are generally edge cases because there aren't too many, and I didn't have the time or energy to write an exhaustive guide for every edge case.

[qballbandit]

Ok, good info folks, I'll see this in my .eng file, so I can try removing it, and re-inserting your, yes?:

include ( "Std_Eng_GP38-2.inc" )

[yellowdog]

I did a 1:1 replacement of the ORTSDieselEngines block sections. Still crashes when adding the Include line.

OpenRailsLog.txt

[yellowdog]

I figured it out, I think. I tried completely deleting the ORTSDieselEngines block section of Tyler's OR eng file without replacing it with any other text and that seems to have done it. MG doesn't crash, at least, and there are no errors in the log