OR v0.9, crashes when applying sand

[scamel]

Hi All,

I thought I'd post this here before I strolled over to the bug reporting page in case this is only a problem with me and not with my OR installation.

I'm attempting to beta test a new route. This route worked flawlessly before the upgrade to OR v0.9, and to be sure it wasn't anything in the route, I loaded the installation of the "finished" version before the route author began to add to it again. I got the same problems.

Using a consist I had created specifically for the beta test, I attempted to get the train moving. This is a purposely heavy train (an RS-18u and several loaded ballast cars) so I can test all sorts of train handling things. In this case, it worked because I likely wouldn't have found out that adding sand (the "X" key) would cause the program to grey screen!

I have attached my log file to this post. There is a rather large error at the end of it, I'm thinking this is probably it, but I do not quite understand what it is trying to tell me.

Thoughts?

OpenRailsLog.txt

[baldwin]

It is not the sanders because I use them and get no crash. However, looking at that error, it may well be a problem within one or both of the sms files. System.ArgumentException: Illegal characters in path.

[rdamurphy]

So, you can start and run the game, and the locomotive works fine until you apply sand?

And it worked correctly before?

There have been a number of sound improvements, can you tell me specifically where you got the locomotive from?

Also, it would be best to file a bug report to track the error.

Thanks,

Robert

[scamel]

Thank you for your insight, Baldwin. It wasn't OR after all, it was the specific engine I was using. I'll have to look around in the guts of that one somewhere to see what the issue is. Other engines work fine in there.

rdamurphy, to answer your questions:

I was able to get the game to open (though without the flashy menu, I seem to only have the alternate menu) and only two of the four tested locomotives caused this problem.

If the problem had turned out to be with OR, and not with something I have happening here, I would have certainly filed a bug report! I've found most of my problems with MSTS over the last 10+ years were always between the chair and keyboard!

**UPDATE**

The MLT Delaware & Hudson route causes the same problems. The sounds from this route were aliased to the two locomotives I had problems with in the other route - specifically the ALCO sounds, EMD sounds work fine. Bug report will be filed.

[scamel]

Fixed

I do not know why I did not see it sooner. It seems the files RS_eng.sms and Alcoeng.sms were missing a crucial quotation mark in the stream for sand.

If anyone else is having problems with the MLT D&H Route, please let me know. If you're having the same problem I had, where OR would crash on the application of sand, check that stream.

To me, this is proof that the OR code is tight! My inner nerd loves this! Well done!

Unchanged:

Stream (
Skip ( **** This stream allows the sander to be played at the same time **** )
Priority ( 4 )
Triggers ( 2
Discrete_Trigger ( 4 StartLoopRelease ( 1 File ( x_sand.wav" -1 ) SelectionMethod ( SequentialSelection ) ) )
Discrete_Trigger ( 5 ReleaseLoopRelease () )
)
)

Changed:

Stream (
Skip ( **** This stream allows the sander to be played at the same time **** )
Priority ( 4 )
Triggers ( 2
Discrete_Trigger ( 4 StartLoopRelease ( 1 File ( "x_sand.wav" -1 ) SelectionMethod ( SequentialSelection ) ) )
Discrete_Trigger ( 5 ReleaseLoopRelease () )
)
)