[disc]

There is a room to make sounds more efficient by just modifing the sms. But it's pointless if the handling of setting going to changed. I mean now the 2082 commit by rdmurphy, that made volume curves match to MSTS, but then reverted because of some problems. I wonder what happened with that change.

[gpz]

From the change history I see the volume curve handling was modified to assume the speed values in it are in km/h, and when realized that the original handling with m/s was the correct one, changed it back. It was within 24 hours, and half year ago, so I really don't get why you took this one as an example for pointless sms changes...

[disc]

Maybe not that was that i remember, but some sounds in OR always had lower volume(when the camera was nearly in same distance like in msts), and some change made them to sound like in MSTS which was reverted after.

[disc]

So i see this stuttering problem isn't really connected to the GC graph. Sometimes the game stutters, sometimes not, on the same path on same route same season same time same settings. It might by a bug of .net framework. Isn't there a way to reset the .net without restarting the full system?

Or maybe connected to AI trains? However the difference isn't big 4 to 12 AI trains

How can i build an OR to .net 4.5.1? I tried setting the compile target in VS to 4.5.1, and it built the game, but when i tried to start it (openrails.exe), crashed instantly, referring to kernelbase.dll