I looked at all your comments and there were two that might be a problem: the first is right under SteamSpecialEffects and the second right before EngineVariables. I've not done multi-line comments like that... they might be ok... but to be on the safe side I'd make each line has "comment" rather than count on multiple lines being controlled by a single "comment". As far as I can tell there is nothing at all wrong with the others.
OR steam locomotive ENGs problems with comment statements
#12
Posted 08 June 2011 - 05:50 PM
Thanks, Dave.
Was it ever resolved that comment statements were allowed in ENG read by OR's code?
Cheers Bazza
Was it ever resolved that comment statements were allowed in ENG read by OR's code?
Cheers Bazza
#13
Posted 08 June 2011 - 07:14 PM
captain_bazza, on 08 June 2011 - 05:50 PM, said:
Thanks, Dave.
Was it ever resolved that comment statements were allowed in ENG read by OR's code?
Cheers Bazza
Was it ever resolved that comment statements were allowed in ENG read by OR's code?
Cheers Bazza
I don't recall.
About all I can say is I always use a # character when I create a comment and I never allow the text of the comment to go past one line -- if I need more than that I do it as a second comment line.
What puzzled me about your original comments was that something was wrong w/ the coupler and that you blamed the comments. That doesn't make sense... the .eng file looked ok. What exactly did you see and have you looked into whatever .wag was behind the loco?
#14
Posted 09 June 2011 - 12:12 AM
captain_bazza, on 08 June 2011 - 05:50 PM, said:
Was it ever resolved that comment statements were allowed in ENG read by OR's code?
Comments are allowed anywhere in STF files, but you've not used a valid comment construction for our STF parser. The valid options are:
- comment ( ... )
- skip ( ... )
- _WORD ( ... )
- #WORD ( ... )
- # ( ... )
- ( # ANYTHING EXCEPT CLOSE BRACKET )
WORD can be any normal token/word without whitespace or symbols in it.
#15
Posted 09 June 2011 - 02:38 AM
@ Dave
I tried two different wagons, including a default MSTS wagon in front and behind the loco.
I didn't see anything in the coupler statements that drew my attention, but I usually reply on what has worked okay in the past. It is also possible that I missed something obvious!!!
I had a problem with the two brake controllers, which required replacing that section in two ENGs. My fault, I may have done something wrong when editing it sometime.
@James, thank you; noted for future testing.
Cheers n goodnight
Bazza
Quote
whatever .wag was behind the loco?
I tried two different wagons, including a default MSTS wagon in front and behind the loco.
I didn't see anything in the coupler statements that drew my attention, but I usually reply on what has worked okay in the past. It is also possible that I missed something obvious!!!
I had a problem with the two brake controllers, which required replacing that section in two ENGs. My fault, I may have done something wrong when editing it sometime.
@James, thank you; noted for future testing.
Cheers n goodnight
Bazza
#16
Posted 18 June 2011 - 05:39 AM
A beta of M&U #5 and the slopeback tender have been uploaded to the beta section of the file library and are awaiting approval.
Please note, both are still WIP. Your feedback is welcome. I recommend the ERIE coal hopper cars (55 tons) available from ET standard gauge freight section.
All I ask is some helpful feedback.
Thank you.
Cheers Bazza
Please note, both are still WIP. Your feedback is welcome. I recommend the ERIE coal hopper cars (55 tons) available from ET standard gauge freight section.
All I ask is some helpful feedback.
Thank you.
Cheers Bazza