[istvanek]

Goku, on 07 February 2017 - 07:41 AM, said:

OR doesn't support it.

Erm, IMHO OR does support it. Just add 'ORTSUserPreferenceForestClearDistance ( X )' command to route .trk file (where X is distance in meters).

OR Manual - 8.14.2 Modifications to .trk files

Artur

[Goku]

You are right. It works in new OpenRails.
So, TSRE will accept this value in TRK file too.

[Goku]

Next version will include tools for working with multiline sound regions and speedposts.

http://i.imgur.com/2gGuouO.png

[Goku]

New version: http://koniec.org/ts...SRE5_v0.684.zip

0.684

- create and edit multiline sound regions and speedposts
- support for ORTSUserPreferenceForestClearDistance in TRK file ( Forests are avoiding tracks when placing trees)
- tile water level fix
- set opacity (Alpha) for map layer (use it before loading or downloading maps; use opauge maps only for terrain texture edition, NOT for object placing etc)
- google maps replaced with universal URL in settings.txt. If you want to use google satellite, set:

imageMapsUrl = http://maps.googleapis.com/maps/api/staticmap?center={lat},{lon}&zoom={zoom}&size={res}x{res}&maptype=satellite&key=

[mgabesz]

Hi Goku! The google satellite image quality is very low in Route Editor. I saved some high resolution (8000x8000) images from "Google Map Customizer" website with "FireShot Pro". These images has better quality. Everybody can change the original saved satellite images in"terrain_maps" folder in MSTS directory. But the problem: Positions of images not the same and i think the angle of view also different. What do you think? Is this useable or no way?

[Goku]

You can't use maps downloaded from the browser in MSTS because it uses different map projection.

Increasing map quality in TSRE is possible, but I think it is too difficult.
1. Google maps texture now has 4096x4096 resolution, so it is only 0.5m per pixel. Maximum possible texture size in most GPU is 8192x8192 px, but it is still 0.25m per pixel and 200 MB per texture in GPU.
2. Google Static Maps allows for downloading max 640x640 px, so for 8192x8192 resolution you need at least 64 requests. And because of projection differences it may be over 100 or even 150.
3. Also applying MSTS projection lowers the quality because of bad interpolation algoritm. I think fixing interpolation algoritm can improve resolution to 0.5m per pixel (now TSRE has something like 0.7-1.0 m/px). But I think 1.5x better resolution it is not worth it.

If you want better quality:
- you can make new interpolation code for TSRE
- you can edit OSM maps in your area and use OSM layer instead:

http://i.imgur.com/z0VhCEK.jpg

[mgabesz]

OK. I understood. Thanks for fast answer and thank you very much for your great work! :cheers3:

[Goku]

I implemented interpolation for projection conversion. Looks it better or not?

http://i.imgur.com/yLS1HRL.png

[mgabesz]

I think it looks better.

[Goku]

And example with 4x more requests to google.
1. 4096x4096 texture.
2. 8192x8192 texture.

I think the 4x request (zoom = 18) might be possible to enable in settings.txt. If you have google maps key, it will work (it requires 170 - 230 requests per tile, depending on lat/lon).
I think 8192x8192 texture is not reasonable.

http://i.imgur.com/OitbJuo.png