[Black Night]

using Dorset Coast v6 noticed there are quite a few trees in the middle of the track this was using X2396 also bushes on the Thames Mersey route as well

[dennisat]

 Black Night, on 12 August 2014 - 12:47 AM, said:

using Dorset Coast v6 noticed there are quite a few trees in the middle of the track this was using X2396 also bushes on the Thames Mersey route as well

This is actually a problem with the route(s). I have DC V6 and in many, many places forests are placed over the tracks. In the MSTS Route Editor you can swivel the forest about and alter the tree density to avoid trees appearing on the tracks when run in MSTS. However, the developers of OR don't know what algorithm was used to generate the tree placement in Route Editor; they have no access to MSTS code. OR therefore uses a different (obviously) algorithm to produce approximately the same tree spread as in MSTS. Where forest have actually been drawn across tracks (or roads, or buildings) there is thus a high probability of trees appearing in the "wrong" place. The only way this can be cured is to use Route Editor to shift the forest boundaries away from tracks, etc, which I have been (slowly!) doing to cure the worst cases.

Dennis

[Black Night]

My Problem is MSTS won`t run on my computer because of the graphic card issue .

[eric from trainsim]

Not having the route editor available does make things a bit more challenging, but it's not a show-stopper...

There are several debugging views available for F5, which are cycled thru by using Shift-F5... on the 6th one, your camera coordinates are displayed at the bottom of the HUD list.

https://lh6.googleusercontent.com/-JTitYj4Jl3U/U-ofK1fo7gI/AAAAAAAAYLg/VGIjL0W2AM8/s800/capture__200056.jpg

1) Use the F8 to navigate to what you think is the center of the Forest Object, and write down the coordinates.

2) Open up the world file, and look for a Forest() object that has coordinates close to that camera location value. You could also find the forest objects, and move the camera to each one to see which is the offender.

https://lh4.googleusercontent.com/-8iSMfEHPMYc/U-ohmtOfGnI/AAAAAAAAYL4/s-FjvfnttGM/s800/capture__200058.jpg
This example isn't fair, as there was only one forest object on the tile, but.... :blush:

3) Once identified, adjust the Area() down by 2-3 meters to shrink the size of the forest accordingly

4) Re-open the route in ORTS, and see if that fixed the problem. You may have to go hunting a few times to find the right forest object or to get the reduction value worked out, but it can be done with a little patience.



Note to the ORTS guys..... If it was possible to keyboard toggle (or provide as a checkbox option) a wireframe bounding box around an object's perimeter, it would make doing things like this a lot easier absent a route editor, and it's probably a function that you'd want in a route editor anyway...

[Black Night]

Thank you for that will give it a go

[dennisat]

 eolesen, on 12 August 2014 - 06:10 AM, said:

3) Adjust the Area() down by 2-3 meters to shrink the size of the forest accordingly

The problem with that solution in DC V6 is that the forest boundaries can be across the tracks for 50m or more; in places the tracks effectively traverse the forest area.

Edit:
In a lot of instances, though, this solution will work.

Dennis