sms_Checker

[slipperman]

Hi All,
I thank Ashraf Ahmed Khan for the accolade - it's much appreciated - but the thread title wasn't very helpful towards indicating its content. Sorry, mate, but I thought it better to start a new thread.

sms_Checker v2.5 will be available from the library, as soon as it's been approved.

Reasons for this release
1. Fixed a bug in the common* folder checking routine which caused the message : .sms file ignored due to its location even though everything was legitimate.
2. Some routes (mainly North American) use a folder named 'alias' to contain .sms files. Some of those 'alias' folders are only used for 'holding' the .sms files for subsequent copying into .eng/.wag files, while for others the .sms files are used directly from that folder. Previous versions of sms_Checker ignored these folders. giving the above message. Running v2.5 in its default condition results in these folders being reported as .sms file in 'alias' folder ignored. A check box is provided to enable 'alias' folders to be included in all validations. Full instructions are included in the revised readme.

As always, please report any bugs, difficulties or suggestions here, or by PM.

Cheers,
Ged

[slipperman]

Hi All,
sms_Checker v3.0 has been uploaded to the library and should be available for download within a couple of days.

The basic program remains unchanged but with the additional option of being able to check for (or correct, where appropriate) specific types of error only.
Minor cosmetic changes have been made to accommodate the new facility.

Also, a minor bug concerning the validity of 'common.*' folders has (hopefully!) been fixed.

As usual, please let me know of any problems and/or suggestions for improvements/enhancements.

Cheers,
Ged

[slipperman]

Hi All,
sms_Checker v4.0 is now available from the library,
The procedures for fixing errors and for creating reports have been modified and a couple of new checks have been added.
Full details are in the main readme.

As usual, please let me know if you have any issues with this version.

May I, respectfully, suggest that the uploader of "MSTS/OR EMD 16-265H Engine Sounds" considers a re-upload to include a readme. This is so that any dependencies can be known - there are a number of missing .wav files. There are also several other anomalies which, although not affecting MSTS, will result in messages in the Open Rails log. Thanks

Cheers,
Ged

[serranolucas475]

hola ged! soy el autor del conjunto de emd 265h, en estos momentos estoy haciendo los arreglos del conjunto! en unos minutos lo subo!

[derekmorton]

Translated:-

hello ged! I am the author of the set of emd 265h, at the moment I am making the arrangements of the set! in a few minutes I upload it!

[serranolucas475]

Screenshot.jpgI just tried my own EMD 265H sound set, it didn't warn me about missing .wav files, which I do when installing a sound set or a cabview. It's that I don't make an alias for it to work, I just paste it in the same folder of the engine that I'm going to use, without the need for aliases as seen in the screenshot.

[serranolucas475]

Thanks derek for the translation!

[slipperman]

Hi serranolucas475,
Many thanks for your reply
If you're using MSTS, it won't report any missing .wav files - you just won't hear them!
I believe Open Rails will report the missing files in its log file.

There are 21 occurrences of missing .wav files (including the horn!) of which 7 are for incorrectly addressed GP38 files.

Cheers,
Ged

[serranolucas475]

good afternoon from argentina ged! I'm going to modify the .sms! when I read your answer, I thought you used Open Rails, on my PC when using MSTS it crashes because you can't use it on a PC with more than 4GB of RAM, and my computer has 8GB of RAM, I open msts and it stops working lol that's not why I can test in MSTS the Sounds!

[slipperman]

Hi serranolucas475,
I tested your sound set using MSTS by adding it to the default Dash9 (I know it's probably not right, but it was only for testing!). My PC has 12GB of memory and I had no problem.
I have since found that the K3L.wav does play in Open Rails, but not in MSTS. ScalabiltyGroup 1 and 3 use horn.wav instead, but that file isn't present in the folder.

Open Rails also reports an error in 265Hcab.sms in the section between lines 607 and 611. The complete entry is :

CurvePoints ( 5 -150.0 44100
0.000 44100
150.0 44100
)

I think you can see what the problem is!

Cheers,
Ged