ORTS Automatic Switch, Curve sounds

[advut]

Hi,
I am having a hard time to use the ORTS exclusive automatic switch\points and curve squeal sounds. I create Openrails folder in my route, then create .trk file and add the necessary entries but it's not working. I know I have to modify ttype.dat file in the route folder to reflect this changes so I have also done that. I use the demo auto sound by Carlo Santucci.

So, is there a route (any country, length, era) which successfully uses this ORTS feature? Helpful if those sounds are loud and prominent. I need to download that to see a working example and learn the process. Please help.

[R. Steele]

When I tried it, you had to download special RunActivity and RunActivityLAA exe files plus a copy of the Orts.Formats.Msts.dll, because Carlo only had it setup for one testing version of OR. The download was in the thread at ET about this.

Here's the thread >>> http://www.elvastower.com/forums/ind..._1#entry215319

I tried it in a route and found them too annoying and loud. It's experimental, needs work, Carlo appears to have lessened his involvement in OR for the present.

Sorry I can't be more helpful. Recheck your files against the examples in the thread, you probably made a simple error somewhere.

[advut]

What?? ORTS manual somewhat describes it so it can't be experimental! I use the latest monogame build by Carlo. Can you tell me the if the space matters? Can I just write the lines or do I have to arrange the lines like the thread? Will ORTS ignore the entries just because I didn't enter the space gaps? Please see the attached pictures.

Strange that you found the sounds loud. In my case there is no sound even though the wav files are loud enough. Point sounds are quite prominent over other sounds in real life, so it's better IMO if they are loud in game too.

[R. Steele]

What?? ORTS manual somewhat describes it so it can't be experimental! .

Options found on the experimental tab are explained in the manual and are considered experimental! Even Carlo describes the sounds as beta, and to my ear they could use refining. Also it has been noted that not all cars squeal, some types are more prone than others.
As I said...experimental.

Just reinstalled everything on my Surfliner 2-2 route OR profile, and sounds are there. Using 4142 monogame.
See screen shots, files should be setup as shown. I always use the double back slash with quotes.
If you care to know why it is the safest method, please see this thread
http://www.elvastower.com/forums/ind...42#entry220542 post#6

Lastly, yes the blank line spaces are important. You can see that my indents are different from Carlo, I normally use a single tab indent, instead of the spacebar...I believe either will work. Hope you figure it out.
I think the sound sets will be refined in the future.

bandicam 2018-08-07 13-20-39-821.jpg bandicam 2018-08-07 13-23-26-019.jpg bandicam 2018-08-07 13-24-46-702.jpg

[R. Steele]

I tried them out in an activity on the mainline with the Surfliner route and found them less annoying then I recall. Maybe at speed, they sound better to me than creeping around the yard. I think I"ll keep them in some routes and give them an honest try out.

[advut]

Thank you, I will try this. It looks like you entered another line gap after the "include" line in the trk file which I didn't. Maybe that's why ORTS doesn't read the automatic sound sms lines. Another problem is ORTS also doesn't show what sms files from the ttype.dat file it loaded in the sound debug window! So I don't even know whether it has actually loaded the auto sound sms files or not!!

[R. Steele]

...Another problem is ORTS also doesn't show what sms files from the ttype.dat file it loaded in the sound debug window! So I don't even know whether it has actually loaded the auto sound sms files or not!!

To overcome this problem:
1. Simply move one of the sms files in the "DemoAutoSound" folder that you placed in the global SOUND folder to a temp folder you created.
Run an activity or explore in the route, then check the OR log to see if there is a warning about not finding the sms file you removed to the temp folder. This should confirm that OR is looking for and using the files in the "DemoAutoSound" folder.
I did this using the BNSF Scenic route and the OR log did show a warning.

Information: Skipped unknown shader name Diffuse first seen in shape f:\2tsf\nwusa\trains\trainset\sli_amt_empire_build er\amt_p42dc_58.s

Information: Skipped unknown lighting model index 0 first seen in shape f:\2tsf\nwusa\trains\trainset\sli_amt_empire_build er\amt_p42dc_58.s

S

Warning: File SOUND\DemoAutoSound/curvesquealtrackex.sms missing from F:\2TSF\NWUSA\ROUTES\BNSF_Scenic

Warning: Skipped missing track sound DemoAutoSound/curvesquealtrackex.sms

CS

Warning: Skipped missing track sound DemoAutoSound/curvesquealtrackex.sms

CS

Warning: Skipped missing track sound DemoAutoSound/curvesquealtrackex.sms

CS

Warning: Skipped missing track sound DemoAutoSound/curvesquealtrackex.sms

and so forth.

Simple troubleshooting techniques to determine if everything is operating as expected...introduce an error and see if it appears in the log.
Remember to reset everything back to normal after you've determined OR will show a warning.

[advut]

So, I've had some time to experiment on this and was mostly successful in adding the auto sounds. I've performed this experiment on 3 different routes.. default Northeast Corridor (USA1), Nagpur -Bhuswal (Vidharbha) and RailIndia (Deoli). Now while the auto sounds work in both usa1 & vidharbha they don't work in deoli route. I've checked for possible errors of mine but none of 3 auto sms sounds work in that route. I think it has something to do with the number of track type entries in the ttype.dat. I suspect that the deoli route doesn't use as many track types as it says in it's ttype.dat file. Is there a way to check this? This route does have other problems like many level crossings not working correctly, station stops not being recognised etc. If you have this route can you please check it to see whether you can use the auto sounds with it and also if those other problems occur to you?

I've also found that the line gap after the "include" line and before the auto sms entries in the trk file that we create for ORTS use isn't necessary. Only 1 blank line at the beginning of that file is enough.

BTW, I agree that the auto sounds don't fit nicely. I will search for better sounds. Anyway thanks for your help so far.