Remove Tree From Track doesn't work...

[Komachi]

I'm running the GN Hi-line and I'm seeing plenty of tree on track, both with it enabled and disabled... Shame it doesn't work at this moment.

[OTTODAD]

So I tested doing it the hard way in the Route Editor, like I do when checking routes like my 450 miles Gold-Spike and the Surfliner-2 routes after having converted them to use DB-Tracks.

Driving a fast loco with the 0-Zero Compass turned on I eyeball the tracks and scenery and when I see something that needs attention hit the PRINT SCREEN key to grab a snapshot.

Having finished the run, which takes some time in long routes, I then open the Route Editor and having made a note of the compass co-ordinates shown by the screenshots and what their problems are then take care of them.

Below is me doing the same in the ORTS DB-Tracks Gold-Spike-X route and having taken a screenshot of this tree on the tracks went into the Route Editor but it's co-ordinates did not show the tree's correct location and had to move the camera to where it was.

Being there you can see the difference between the placing of forest trees in MSTS and ORTS !

At this rate it would take a long time to locate trees on tracks and fix them and other scenery glitches.

O t t o

[eric]

Maybe it's just the angle, but is that red line over the ballast?...

[jjtang]

So it seems MSTS actually places trees further inside the boundary, then what OR is currently doing.

[eric]

It depends in part on the density... MSTS caps it well below where OR does, so the possibility of having more trees overhanging the red line increases with the population() line....

I don't care if it goes all the way up to the boundary. To me, the red lines are a "do not cross" boundary. The buffer logic should take into account the maximum possible scaling width of the ACE file.

[drelyea]

Hi,

MSTS will set trees at the edges of the forest box. It doesn't happen as often for the reason Eric gave (lower density).

It won't happen as obviously with the "scrawny" pines and firs as it does with the "majestic" oaks and maples, but it does happen. (There is trouble in the forest....)

While the red line of the box to the right of the track is much closer than I would set it, the problem in Ottodad's case is that corner of a forest box at the top of the screen sticking over the track, at the compass info in the MSTS RE screen.

Short of "cracking" the MSTS pattern, many older routes will have this problem. If placing the forest didn't put a tree on the track, the route builder moved on. It will be impossible to set an inner boundary, if the forest straddles the track partially or completely.

Doug Relyea

[OTTODAD]

The red line of the forest to the right of the track there being over the ballast is not the problem, it is the forest to the left of it !

Moved it a bit and no more tree on the track !

It's listing in the World file which uses it is shown below.

Tried to do the same in the more detailed DB-Tracks MINI and ORTS crashed here:



Log attached.

I seem to remember that there has been a fix for this problem but can not find it in my ORTS X.1525 Options / Simulation settings other than having ticked: "Use Advanced Adhesion Model".

O t t o

[twpol]

Below is me doing the same in the ORTS DB-Tracks Gold-Spike-X route and having taken a screenshot of this tree on the tracks went into the Route Editor but it's co-ordinates did not show the tree's correct location and had to move the camera to where it was.

It is a known issue that the coordinates in Open Rails are not in alignment with those in MSTS - it will be fixed eventually.

[OTTODAD]

Thanks, James !

No problem, as making scenery modifications requiring the Route Editor must wait until ORTS is at a more advanced state.

O t t o