.eng file closing bracket problem.

[apco25]

Doing a little editing this morning on the MILW GP20 rebuilds and once again I've found a malformed .eng file. Everything loads up fine (I use Open Rails) except the outside sound alias doesn't play. I've experienced this problem before in OR and MSTS. It is not an alias or .sms problem as the .sms file works fine in other engines. With the previous problems it was traced down to a section of the .eng file not having the correct brackets causing the file to not parse and fail to load.

I've been staring at it for the 30 minutes and can't find where that break exists!. Any fresh eyes want to look it over?

[inflammable]

I have ConText with the TrainSim highlighter.

After some paging through it, you are missing the closing parenthesis to the Lights section. Each light is closed, but the total 38 Lights is left open. Which will make the immediately following Sound not work.

The Engine section works out fine.

James

[tbundy1982]

I built this light file before downloading OR, therefore it probably does cause problems in OR. The solution that I have found with other models is to replace the the "#" with "comment (" or something like that. OR does not, and according to the development team will not ever, read a # as a comment. The #'s pretty much botch the engine file in OR. Most of Dick Cowen's models use the "#" instead of " Comment (" and will probably give you the identical problem.

If that doesn't work for you, we'll try to dig a bit deeper.

James may be right about the closing parenthesis. I don't see how the locomotive would run in MSTS without error, though, if this was the case. I never beta tested these so that one might be on me. :/

I hope you find a solution!

Tyler

[DCRR1]

The error is located on line #1188. This is right below the "end of lighting" comment and above the sound line for the engine sms. The bracket on that line is an opening bracket, not a closing bracket.

(++++++++++++++++++++++++++++++++++ End of Lighting Section ++++++++++++++++++++++++++++)
( should be )
Sound ( "..\\..\\COMMON.SND\\MLW_645\\645T44_(SOO)_eng.sms " )
)

John

[apco25]

Tyler,

I had already changed that closing bracket above the sound line, but that didn't correct the problem. I also replaced the #( with Comment( also with no results.

The cab .sms file is loading correctly, but not the external. Yes, Dick Cowen's do the same thing in OR. I have fixed those in the past.

Btw, Conbuilder reports that these are non driveable AI engines.

[hiball 3985]

I took the .eng file, only changed the closing bracket and the sound lines to what I'm using and it worked fine. Maybe your problem is with the engine sounds you are alliasing to?

[apco25]

I'm using the MLW 645 sound set and as I stated in the original post they work just fine in other .eng files.

[hiball 3985]

Can you post the eng file you fixed?

[lineman]

The original files worked fine after I fixed the closing bracket problem and Replaced all the '#' signs in the light section with 'Comment' including the ones before the light colors entry, after the light hex codes.

[crstagg]

................
Btw, Conbuilder reports that these are non driveable AI engines.

Just tested the file in ConBuilder 5.5.0 and it does NOT report that it is non-drivable.

And testing the ENG file after correcting the "(" to ")" no errors were found except the missing S and SD files which of course were not in the ZIP file provided in post #1

[apco25]

Charles,

When I created a consist and added the engines to it I got the non driveable message....

I've correct that bracket already and yet OR is still barfing on parsing the sound entry. Same goes for changing # to comment. Is anyone testing this in OR or just MSTS?

[lineman]

I tested it in both to see the difference. As stated before it only worked after every # in the lights section was replaced not just the section headers. Hope you get it working soon. I don't know what else it could be?

[crstagg]

Charles,

When I created a consist and added the engines to it I got the non driveable message....

I've correct that bracket already and yet OR is still barfing on parsing the sound entry. Same goes for changing # to comment. Is anyone testing this in OR or just MSTS?

What ver of ConBuilder?

What is the ZIP? I cannot test in OR w/o the other files besides the ENG.

[tbundy1982]

The zip is milwgp202.zip here in the file library. I have some time today so I'll try to help you guys sleuth this out. Standby....
Tyler

[baldwin]

I am using an unchanged version of this eng file and it runs in both MSTS and OR, and the # instead of comment does not stop OR from displaying and running the engine. Conbuilder does not report an undrivable engine either. So I took the file from the OP and changed the cab and sound calls, changed the error at the end of the light section, and once again, it loads and runs in MSTS and OR and Conbuilder does not report an undrivable engine.