Using MSTS editor with ORTS code in .trk file for a route

Bug #1714568 reported by Keith Wendt on 2017-09-01
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Open Rails
Carlo Santucci

Bug Description

OR development team,
I inserted the line of ORTS code in the .trk file for a route that removes trees from track sections. The line of code removed the trees from track sections in the route (the route had many trees in track sections when running in OR). However, when I tried to use the MSTS editor for the route with the ORTS line of code in the .trk file, the editor displayed an error message and closed. I tried moving the line of ORTS code to a different location in the .trk file three times but that didn't matter; MSTS displayed the error message and closed. I expect this issue has already been reported. If others have reported this issue, the OR manual should warn about it and should encourage setting up the ORTS folder for ORTS statements. Thanks for reviewing this message.

Keith Wendt
Wisconsin, USA

Carlo Santucci (carlosanit1) wrote :

If you put the OR additional lines at the end of the .trk file (just above the isolated parenthesis of the last line) the MSTS route editor loads regularly here.
I will add this info to the manual.

Carlo Santucci (carlosanit1) wrote :

Manual modified in x.3938.

Changed in or:
assignee: nobody → Carlo Santucci (carlosanit1)
status: New → In Progress
status: In Progress → Fix Committed

Thanks for responding to my concern about an issue with ORTS. I placed the line of ORTS code where you suggested in the .trk file for a specific route and it removed tress in/too near tracks and I was able to use the MSTS editor with the route. Thanks for the information about the fix for the issue. In the manual, someone should just add the specification for where the line of ORTS code should be placed in the .trk file. Thanks again.

Keith Wendt
Wisconsin, USA

James Ross (twpol) on 2017-09-10
Changed in or:
milestone: none → 1.3
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers