Not heard of any case. In fact, the guy that created Konstanz-Villingen, Prelli, which serves as a prime example of realistic track laying (and started out as an experiment only), highly recommends creating a lot of trackrules for all situations needed in your route. Less ribbons, more rules. I'm quoting Prelli here (translated with DeepL): "Good track construction is simply not possible with just one track rule and I now have enough experience to claim that TS can handle a whole battery of track rules very well. This experiment* should therefore also serve to finally clear up this prejudice, which can only have arisen out of ignorance or profit motives, and to demonstrate once and for all what is feasible if you just want to. It is undisputed that it is more work to build with several TrackRules and the consistent use of easements and also to superelevate them. I understand payware and freeware track builders who shy away from this effort and not everyone attaches such great importance to it. I have no problem with that. But I do criticize the misinformation that has often been spread here. I am against that and I am fighting against it. Good track construction with the necessary track rules neither harms performance nor stability, and anyone who claims otherwise should either provide evidence or please put an end to these annoying and obstructive prejudices that can be used to justify even the worst track construction. I think this must finally come to an end so that the bar for good tracks (here in the sense of “good track”) can finally be raised." * This "experiment" became Konstanz-Villingen Source: https://rail-sim.de/forum/thread/8389-rlb-team-badische-schwarzwaldbahn-kbs-720/
The question should be "Does a route need multiple track rules?" But no, multiple rules will not cause crashes--though a badly written track tile .bin file can crash the game, just like a badly written .bin file for any other asset will. That may be where the misconception of multiple rules being troublesome comes from, but it can certainly be easier to work with just a single rule.
Probably the most prominent bad asset was a crippled version (400-ish bytes) of the Port Ogden & Northern "PONtrack.bin".
I think some of those statements are a bit extreme. I personally prefer to use a single, or few, track rules. I'm not sure why that would be considered to be a performance hit. I find a big advantage of using a single track rule comes when you want to change a line's speed limit or status - it is an absolute nightmare trying to change speeds for lots of small sections with different track rules. I'm sure there are advantages and disadvantages to both methods - I don't think any "annoying and obstructive prejudices" that need "fighting against" come into it. John
Well, the guy has proven his skills with that route which is still seen as the best german route ever made in TSC. The initial question is anwered, of course it's up to everyone how to make their routes. The statement by Prelli came from the german forums, and there were indeed a lot of routes at that time which suffered from bad track laying, and many did use the wrong assumption you couldn't use many trackrules as an excuse.
.... the important word being "excuse".... Far too may times an *excuse* has made it's way into general belief. You only have to look at what a track rules contains to see that there's very little to support needing more than one. Give a route it's own track rule and the world is your Oyster.
I can't think of any reasons off hand why you would need multiple track rules in a single route. A single track rule can be modified as and when required to cater for the needs of the section you are setting up without it interfering with any track already laid. On the other hand, the only real drawback to using multiple rules is that it becomes very fiddly to adjust track properties close to/across the point where they join. I'm fully in favour of keeping the number of track ribbons down to the necessary minimum too, even if this means relaying individual track segments several times to achieve it.
I use multiple track rules for my route, and it is the only way to get correct entry- and exit curves (length) to match real world track data (and google map overlay) One track rule for each speed limit, with different angles for super elevation (and if I'm not wrong the speed tolerance is also important) More on this on the Rail-Sim.de forum Just don't use multiple track rules in a junction or in a curve.
Multiple track rule. On the left SE Wire Track rule and on the right SE Nowire Track rule. Can they interfere with signals?
