[Bert Wise]

Hi there

I get the following warning in my OR log when I run MLT's Rogers Pass route.

Warning: Track node 37 pin 0 has invalid link to track node 0 in G:\MSTS\MSTS Mini Routes\Canadian Rockies\ROUTES\RogersPass\RogersPass.rdb:line 283

I am assuming this is a road piece, not a track piece, as it references the .rdb, not the .tdb

I've looked at the RogersPass.rdb and it has the following for track node 37

		TrackNode ( 37
			TrEndNode ( 0 )
			UiD ( -12660 14916 726 0 -12660 14916 332.64001 790.06702 -344.61603 0 2.74016 0 )
			TrPins ( 1 0
				TrPin ( 0 0 )
			)
		)

I went into TSRE to find the node but I can't see a node number over road pieces.

Is there another way I can locate this node within TSRE?

Thanks

Bert

[Kapitaen13]

Hello Bert,
Actually, I don't understand your question. :pardon:
I already posted what you need to find the street node.
Track Nodes cannot be found

First I searched for the street in the Worldfile. To do this, open w-12660+14916.w and search for UID ( 37 ).

If there is a hit, you can also find the street; if there is no hit, there is only an error in the street database.

How to get to the road section in the TSRE with the NAVI WINDOW is shown in the linked post in picture 3. Alternatively, or if there is no street segment, you can use the start parameter in ROUTE.trk to start the TSRE directly above the node, so that you only have to turn the camera downwards.

RouteStart ( -12660 14916 332 -344 )

Either you will find a single piece of road or only a single Pole. In any case, the road is not connected to other parts of the road ( TrPin ( 0 0 ) ). If it is only a single street segment, you can try to delete it. If there is only the Node Pole, you can try to add a new street segment to it and then remove the rdb lines with the help of the Hacks function in the TSRE. The hack also works with the road database.

Good luck.

[Bert Wise]

Hi Kapitaen13

Using your instructions, I was able to select the road piece in question. My confusion was because no node numbers show for road pieces like it does for track pieces.

As you can see in the attached photo

 Capture.JPG (255.09K)
Number of downloads: 9

I seem to have a road section ( with blue poles ) that is attached to other road sections. When I select it, UiD shows 726, which also shows up in the warning message so I assume this is the offending road section.

I deleted the road section, then pressed "Z" and saved. The road section and blue lines disappeared but the .rdb file didn't update and I still get the warning in the OR log.

I then restored the original files and added a road segment to the end, pressed "Z" and saved. The blue lines extended over the new road but the .rdb file didn't update and I still get the warning in the OR log.

How does one update the .rdb file?

There are 4 warnings in total in the OR log, all referencing 726. The coordinates seem to match the 4 poles at the ends of the blue lines over this offending road piece.

Any suggestions would be welcome.

Thanks

Bert

[steved]

Do you have these two lines in your settings.txt for TSRE?
writeEnabled = true
writeTDB = true

Randy

[Bert Wise]

steved, on 14 April 2023 - 10:44 AM, said:

Do you have these two lines in your settings.txt for TSRE?
writeEnabled = true
writeTDB = true

Randy

Yes, both lines are in my settings.txt file, without a # at the beginning of the line.

Bert

[steved]

Where is the route installed?

Randy

[Bert Wise]

Outside of any protected folders

G:\MSTS\MSTS Mini Routes\Canadian Rockies\ROUTES\RogersPass

Bert

[Kapitaen13]

Looks like you found the right piece of road, good job.
Unfortunately, I cannot say what is going wrong.

You click on select, click on the street,....

https://dat-host.de/images/2023/04/15/Screen-Shot-04-15-23-at-11.30-AM.jpeg

... then you press Del on the keyboard, street and rdb lines disappear and then you save in the menu.


https://dat-host.de/images/2023/04/15/Screen-Shot-04-15-23-at-11.30-AM-001.jpeg

Quote

I deleted the road section, then pressed "Z" and saved.

What is pressing Z supposed to do here? I don't understand that now.

[Bert Wise]

Unfortunately, that doesn't work.

I can select the piece and delete it. The road piece and the blue lines above it disappear. I then save but when I run the route in OR i still get the same 4 warning messages.

I looked at the .w file and the UiD 726 is no longer there, but the nodes still exist in the .rdb file.

Is there some other way that the .rdb file gets updated?

Pressing Z, i understand, updates the .tdb file.

As further information, once I delete the road piece, if I attempt to place a new road piece in its place, TSRE crashes to the desktop. I've replicated this several times.

Bert

[Kapitaen13]

Judging from your information, the error is not caused by the deleted road section. As already mentioned, no connection to the road system is established with TrPin ( 0 0 ). According to this, there should only be one pole without verctor lines at the position in question, presumably in blue. But if TSRE crashes during placement, you won't get anywhere with the hack function.
How many hits come up in the rdb with the search pattern for "-12660 14916 726"?

Individual track or road nodes can be removed from the database with TSUTIL and the function 'clrdb'.

Quote

20) Reorganization of databases (track/road) and resources
Function ('clrdb') analyzes track- and road-database and deletes all definition-chains (TrEndNode -
TrVectorNode/TrJunctionNode - TrEndNode), which are no longer used. A definition-chain of nodes is
no more used, if there are NO valid references from world- or sound-objects to this chain. This
situation may exist, if world-objects or total world-files have been deleted.

Or you can delete them manually and use "rendb" to restore them by numbering.

Quote

13) Modify track-database "*.tdb"/"*.rdb" and delete gaps
After manual delete of (defective) Track-Nodes from track-/road-database *.tdb/*.rdb, this function
('rendb') can repair references and dependencies within the databases. All Nodes are
'shifted together' and references are updated. It is checked, if there are invalid references
which cannot be reestablished. These references are logged and replaced by '0'.
TrItem-Definitions are renumbered, too. All gaps are deleted. If specified, TrItem-Definitions,
which are no longer referenced from world-files or Track-Nodes, are also deleted. All references
are updated.

However, these are complicated processes. I would have to have the track itself to try this out.
Sorry that I can't help here...