You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using ProMods 2.70 (with ETS2 1.50), and ProMods TCP 1.50, ts-map built on Visual Studio 2022 using develop branch.
If the max tile depth is set to >= 4, ts-map will not generate any tiles at greater depth than 4, and reports having completed successfully.
During tile generation, it (correctly, I believe based on the high value) shows the total number of tiles to generate, but stops at roughly 160 (a depth max of 4).
The problem can be circumvented I believe by generating twice, 0 -> 4 depth, and 5 -> 8 depth. I've been using the tiles (combined, with the json info file correctly edited) with JAGFx.
Possible issue with some of the tiles at a zoomed out level (3 or 4, maybe) not displaying on the map widget of the tool above - but haven't yet conclusively proven what the reason for this is.
I'll update the issue if I discover anything else - if there's any testing I can help with to identify the source of the issue, feel free to ask! Thanks in advance if you get a chance to look this over.
The text was updated successfully, but these errors were encountered:
Using ProMods 2.70 (with ETS2 1.50), and ProMods TCP 1.50, ts-map built on Visual Studio 2022 using develop branch.
If the max tile depth is set to >= 4, ts-map will not generate any tiles at greater depth than 4, and reports having completed successfully.
During tile generation, it (correctly, I believe based on the high value) shows the total number of tiles to generate, but stops at roughly 160 (a depth max of 4).
The problem can be circumvented I believe by generating twice, 0 -> 4 depth, and 5 -> 8 depth. I've been using the tiles (combined, with the json info file correctly edited) with JAGFx.
Possible issue with some of the tiles at a zoomed out level (3 or 4, maybe) not displaying on the map widget of the tool above - but haven't yet conclusively proven what the reason for this is.
I'll update the issue if I discover anything else - if there's any testing I can help with to identify the source of the issue, feel free to ask! Thanks in advance if you get a chance to look this over.
The text was updated successfully, but these errors were encountered: