by asalmon on Tue Aug 24, 2004 8:18 am
Although I am not a conbuilder beta-tester, I have been on correspondance with one of the testers, Tony F. The below is mostly his work, which I have confirmed similar results on my PC. (As we had different windows versions it was good to compare results)
When a sound is referenced in an SMS file, MSTS first looks in the current directory for it, then looks in the main sound directory.
If a sound is referenced as follows
../../gp38/sound/x_gp_horn.wav
then when it looks in the current folder it goes up two levels, down through gp38 to sound and finds it.
If it doesn't find it, it looks in your msts folder. HOWEVER it looks for
{insert path here}/train simulator/sound/../../gp38/sound - which is looking for a gp38 folder at the same level as train simulator - which most likely doen't exist!
So, for all those sounds meant to be in main sound folder, if you try to alias them they don't work.
Try it - have a consist of two of your engines where "x_couple" has been incorrectly aliased. Explore a route - uncouple and recouple - what do you hear?
Now fix the sms removing the "aliasing" of the coupling sound. Repeat. How is it now?
Another bit of proof - run msts with the soundtest interface - train.exe -vm:w -soundtest - when you do anything with your incorectly aliased enging, you get "SMS error - failed to load WAV" - try it.
Therefore - all these errors do need fixing.