If anyone is interested in testing some changes to the route merge functions, let me know.
Last month, I merged a route with overlapping tiles, and it was a bit of a mess for two reasons:
1) The second route's Terrtex replaced what was already there
2) The terrain from the second route replaced what was already there
3) I really didn't want any the track added to the TDB
I've since fenced off some of the processing that takes place in a merge, and would like to offer it up to others to test.
There are a few new keywords in the settings file that right now need to be set:
Right now, these default to false. If people think protecting the terrain, terrtex and TDB should be the exception, I can flip this around to use the keywords to only disable those actions if you want to disable them.
Feedback welcome.
Last month, I merged a route with overlapping tiles, and it was a bit of a mess for two reasons:
1) The second route's Terrtex replaced what was already there
2) The terrain from the second route replaced what was already there
3) I really didn't want any the track added to the TDB
I've since fenced off some of the processing that takes place in a merge, and would like to offer it up to others to test.
There are a few new keywords in the settings file that right now need to be set:
Code:
routeMergeString = "IRM:0:0:0" // For merging a second route with offsets X Y Z applied if // world geometry is not identical routeMergeTerrain = true // Allows the merged route terrain to overwrite the original route routeMergeTDB = false // Adds track and road objects but does not add them to the merged TDB routeMergeTerrtex = true // Allows the merged route's terrtex to overwrite the original route
Right now, these default to false. If people think protecting the terrain, terrtex and TDB should be the exception, I can flip this around to use the keywords to only disable those actions if you want to disable them.
Feedback welcome.