Missin terrain in New L&PS

[Don6218]

I have some missing terrain in the New London & Port Stanly route. The coordinates are given below. I though it may be a download issue but it only corrected in MSTS with a subsequent new download.
Could it be something that OR is reading incorrectly or cannot read? It is the only place there is a problem, and no prominent errors. When I run a "Test" it comes back clean with no problems, same with RR.

I have downloaded the route again and installed in one of my add-on drives, this time no missing terrain in MSTS. I haven't had a chance to check it in OR yet.

It looks like something missed the ticket on my initial download. I will post the coordinates as soon as I can.

Thank you for any information.

************************************************** ************************************************** *******

Edit: The terrain now works in MSTS but in OR it is still missing. Something OR cannot process maybe. There is nothing I can see in the OR error report. I will submit that over at ET and see if they can shed some light on this anomaly.

The coordinates are: 35' -- Lat 42.828200 by Lon -81.183250

[OTTODAD]

Can you please post a link to the web site you have downloaded it from ?

[crstagg]

There is one in the T-S library but it is 4 years old. Not sure what he means by New L&PS.

[OTTODAD]

Observe the Compass Co-ordinates which do not match !

[Don6218]

Here is the screenshot with the compass:

[Vince]

Transfer patches not displaying?
That doesn't look like tiles missing to me. I'd have to look at the location in the RE to be sure.

And yes, the MSTS compass coordinates are known to be incorrect. Thats why there are 5 miles missing between Philly and Wilmington on the NEC.

[wacampbell]

Its a problem with terrain transparency - the feature used to make tunnel portals etc. I am not sure if it is a file problem, or if OpenRails is interpreting the file wrong. Either way, I posted a fix yesterday that I believe works ...

https://www.trainsim.com/vbts/showthread.php?321098-Missing-Land-L-amp-PS&p=1862827#post1862827

[longiron]

Observe the Compass Co-ordinates which do not match !

Otto,
Its a well know and long standing minor discrepancy between MSTS and OpenRails coordinates. It's not an issue because OR doesn't have a RE, so exact coordinate location doesn't really matter as long as OpenRails is internally consistent.
chris

[OTTODAD]

Its a well know and long standing minor discrepancy between MSTS and OpenRails coordinates. It's not an issue because OR doesn't have a RE, so exact coordinate location doesn't really matter as long as OpenRails is internally consistent.

It matters when one tries to find the same compass coordinates where ORTS is having a problem in the MSTS Route Editor !

This patch showing missing terrain textures in ORTS is not a "transparency" and the MSTS tiles there are using standard Terrain textures !

[wacampbell]

Perhaps I will try one more time. I am the author of the L&PS route, and also a primary author of the Open Rails program. I have been able to replicate the OP's problem report. I can say with certainty this has to do with a little known feature of the route editor where terrain can be made invisible with the V key. This feature is used for creating transparent areas in the terrain for forming tunnel portals. The effect of the V key is to create special 'visibility' files in the route's TILES folder. These files have a name ending with _f.raw. They contain the data that describes what part of the terrain should be 'invisible' Through some error, some copies of Version 3 of the L&PS route have _f.raw files that are corrupt or incorrect. They can be fixed in the route editor as I described in the post that everyone is ignoring. Or possibly simpler, is to go into the TILES folder and delete the five files with names that end in _f.raw file. Since the L&PS doesn't use any tunnel portals, these files are not needed.

Its a problem with terrain transparency - the feature used to make tunnel portals etc. I am not sure if it is a file problem, or if OpenRails is interpreting the file wrong. Either way, I posted a fix yesterday that I believe works ...

https://www.trainsim.com/vbts/showth...27#post1862827

[OTTODAD]

Hi Wayne !

I took notice but could not figure out how to apply V with F7 nor F9 when in the Route Editor !

Removing the 5 *_f.raw files worked.

I have asked in the ET forum when you will release this update to the L&PS, being mentioned. So far no reply.

LPS-TERRAIN-FIXED.jpg
Click on the image to enlarge.

[wacampbell]

I have asked in the ET forum when you will release this update to the L&PS, being mentioned. So far no reply.

There is no 'when' in the route builder's vocabulary - you know that :-)

As to the V key, its time to reread section 3.11.2 of the Michael Vone bible.

Hopefully the OP will have some success with this fix.

[OTTODAD]

As to the V key, its time to reread section 3.11.2 of the Michael Vone bible.

Good grief, it has been a long time since I did some creative work using the Route Editor.

It is on page 192 of Michael's Guide to Route Building, but is rather limited as transparent terrain patches can not be rotated !

[Don6218]

That is what I appreciate about this forum, solutions to everyday problems.

I have followed Mr. Campbell's direction and will do a test as soon as I can. This is a great route and finely detailed, perfect for OR.

Thank you all for the submissions.