Issue Type: Severe Bug (Terrain deformation affecting multiple routes) Summary: When building a custom route in Train Simulator Classic, using the same coordinates as another installed route, terrain deformation from my custom route is also altering the terrain of the other route. This happens despite me not opening or editing the other route in any way. Steps to Reproduce: 1. Create a custom route from scratch using the route editor. 2. Build the custom route in the same geographical coordinates as an existing installed route. 3. Edit terrain (e.g., sculpting or smoothing) in the custom route. 4. Observe changes to the terrain in the other installed route with overlapping coordinates. Expected Behavior: Terrain modifications made to one route should be isolated to that route and should not impact any other installed route, regardless of coordinate overlap. Actual Behavior: Terrain changes made in the custom route are mirrored onto the other installed route occupying the same coordinates. This occurs even though the other route has not been opened or edited, leading to unintended and significant deformation in a completely separate route. Impact: The other route, which I had not edited or accessed in editor mode, has been significantly deformed, making it unusable. I am now hesitant to reinstall the original route, fearing it could overwrite or corrupt the weeks of progress I have invested in my custom route. Additional Context: The purpose of building in the same area was to reconstruct the original railway as it appeared in the 1930s. Both routes now have conflicting terrain data due to this bug. The issue has caused significant disruption, as I enjoyed the original route and now cannot use it without further damaging my work. If anyone else has had this problem feel free to add to this post.
It also seems to only be doing this on routes you are importing hight maps into so that the terrain is of that location
Just make the original route (the one that you don't want altered) read only whilst you're route building, or if you want to go one step further remove the route from RailWorks/Content/Routes altogether and return it when you wish to drive it again.
