Hi there
I would like to try to offer a solution here, as the linked article does not answer all the questions.
I also don't understand why Bert Wise is not told how to select the switch under the terrain with the TSRE using SETTINGS and Stick Camera To Terrain.
So we start with an error message from a route that is available to me. I do not have a GitHub account.
Warning: {TileX:-5791 TileZ:14803} track node 54 could not be found in TDB
The following message from you should serve as a comparison.
Warning: {TileX:-6081 TileZ:14925} track node 2296 could not be found in TDB
Since the error is not in the TDB, we have to look in the world files. In my case, that would be w-005791+014803.w.
In your route, this is w-006081+014925.w.
We now open this file with a text editor. I use ConText with MSTS HighLightning activated.
In the opened file we now set a search pattern for the Track Node. In my case
UiD ( 54 ), in yours
UiD ( 2296 ).
https://dat-host.de/images/2023/04/06/Screen-Shot-04-06-23-at-10.38-AM.jpeg
Here we can now locate the exact position of our track (outlined in red).
Now we can start the TSRE track editor to see why there should be a track node error at this position. So we start the TSRE with the route in question. As soon as the route is loaded, we set the camera view exactly vertically downwards. This helps to find the track.
https://dat-host.de/images/2023/04/06/Screen-Shot-04-06-23-at-10.32-AM.jpeg
In the TSRE Navi Window we now search for the track we are looking for. To do this, we first enter the tile x and tile y coordinates (outlined in red) and then camera x (outlined in blue) and camera z (outlined in green).This information is taken from the first image, outlined in red.Please note that you cannot enter Camara values with decimal places. Otherwise the value will return to 0.After clicking on Jump we should then land over a track.
https://dat-host.de/images/2023/04/06/Screen-Shot-04-06-23-at-10.34-AM.jpeg
This track is now already selected in the last picture. The corresponding data from the error message are outlined in red.
https://dat-host.de/images/2023/04/06/Screen-Shot-04-06-23-at-10.35-AM.jpeg
Result: it is not a mistake in this example, but intentional. There is a siding next to the track that is not supposed to be used in the simulation and is therefore intentionally not entered in the tdb.
I wish you a lot of fun with the error hunt, Jan