Error in the TBD of Dynamic tracks

Use this forum if you need help using TSRE.
eolesen
Posts: 57
Joined: 28 Feb 2021, 02:39
65535 is a magic number... it's the largest 16 bit unsigned integer possible.

DT should be used sparingly. On my routes that average 200+ miles in length, I might use 10 pieces of DT. A few have zero.

User avatar
Goku
Site Admin
Posts: 363
Joined: 15 Jan 2019, 18:10
Location: Poland
Contact:
In TSRE and OR there is no longer such a limit. We use Int values instead of Short Int.

ADITYA3191
Posts: 35
Joined: 19 May 2020, 13:46
Even after deleting DT, Problem continues. This is very demotivating. Please guide me if there is any other solution on it. You can go through the route using link in previous discussions.

Kapitaen13
Posts: 46
Joined: 16 Jan 2019, 15:21
I have downloaded and installed the route, thanks to ADITYA3191.
For one thing, contrary to previous statements, there are errors in the route after all.
Screen Shot 01-10-23 at 10.23 AM.JPG
Screen Shot 01-10-23 at 10.23 AM.JPG (126.47 KiB) Viewed 26735 times
Screen Shot 01-10-23 at 11.02 AM.JPG
Screen Shot 01-10-23 at 11.02 AM.JPG (48.33 KiB) Viewed 26735 times
Screen Shot 01-10-23 at 10.20 AM.JPG
Screen Shot 01-10-23 at 10.20 AM.JPG (42.6 KiB) Viewed 26735 times
But these errors have no effect on the DynTrack.
The big problem in the route is the internal tsection.dat. This was also mentioned by the previous speakers. There are serious errors in the file structure here.

Kapitaen13
Posts: 46
Joined: 16 Jan 2019, 15:21
Screen Shot 01-10-23 at 01.17 PM.JPG
Screen Shot 01-10-23 at 01.17 PM.JPG (127.73 KiB) Viewed 26734 times
From line 60904 the big mess begins. After the trackpath number follows the number of sections. This is followed by the section. This must not be smaller than 40002, but see for yourself!

If you delete the unused sections and path from the tsection, you can put DynTracks back into the route, but they will never match the track again.
Even just re-integrating via the z key results in different track layouts.
Screen Shot 01-10-23 at 04.08 PM.JPG
Screen Shot 01-10-23 at 04.08 PM.JPG (100.66 KiB) Viewed 26734 times
Screen Shot 01-10-23 at 04.07 PM.JPG
Screen Shot 01-10-23 at 04.07 PM.JPG (101.07 KiB) Viewed 26734 times

Kapitaen13
Posts: 46
Joined: 16 Jan 2019, 15:21
Screen Shot 01-10-23 at 04.06 PM.JPG
Screen Shot 01-10-23 at 04.06 PM.JPG (99.87 KiB) Viewed 26734 times
I then tried to rebuild the rail database via ROUTERITER TSUTIL. Unfortunately this was developed for the MSTS and I get hundreds of errors because in the MSTS the radius of the DynTrack must be negative.
Screen Shot 01-10-23 at 01.15 PM.JPG
Screen Shot 01-10-23 at 01.15 PM.JPG (134.36 KiB) Viewed 26734 times
Sorry, but if you don't have an older backup, I don't see any chance for a further build....

Jan
Attachments
LogOR.zip
(1 KiB) Downloaded 431 times

eolesen
Posts: 57
Joined: 28 Feb 2021, 02:39
It looks like the numbering for the DT got written as { n-65535 } instead of continuing to { 65535+n }

I wonder if hand editing the Trackpath numbering to be +65535 might get things in synch with the local tsection again?

Or... deleting out the >65535 numbers from both the TDB and local tsection.

I requested access to give it a shot. If Jeff Kraus is still around, he might be someone who could solve this type of conundrum.

Kapitaen13
Posts: 46
Joined: 16 Jan 2019, 15:21
The best handmade result obtained is this:

Code: Select all

.trk

	RouteStart ( -2783 13177 240 940 )


__________________________________________

tsection.dat

	TrackSection (
		SectionCurve ( 0 ) 65536 14.8 0
	)
	TrackSection (
		SectionCurve ( 1 ) 65538 -0.206 269
	)
	TrackSection (
		SectionCurve ( 1 ) 65539 0.206 269

	)

	TrackPath ( 45381 2 65536 65538 )

_______________________________________________

.tdb

		TrackNode ( 151
			TrVectorNode (
				TrVectorSections ( 3 0 39877 -2783 13177 10815 0 2 00 -2783 13177 240.71799 0.97300601 840.56403 0 0.061940242 0 65536 45381 -2783 13177 10830 0 1 00 -2783 13177 241.33701 0.97300601 850.54498 0 0.061940271 0 65538 45381 -2783 13177 10830 0 1 00 -2783 13177 241.95601 0.97300601 860.52582 0 0.061940271 0 )
			)
			TrPins ( 1 1
				TrPin ( 164 0 )
				TrPin ( 112 1 )
			)
		)

_________________________________________________

w-002783+013177.w

	Dyntrack (
		UiD ( 10830 )
		TrackSections (
			TrackSection (
				SectionCurve ( 0 ) 65536 14.8 0
			)
			TrackSection (
				SectionCurve ( 1 ) 65538 -0.206 269
			)
			TrackSection (
				SectionCurve ( 0 ) 4294967295 0 0
			)
			TrackSection (
				SectionCurve ( 1 ) 4294967295 0 0
			)
			TrackSection (
				SectionCurve ( 0 ) 4294967295 0 0
			)
		)
		SectionIdx ( 45381 )
		Elevation ( 0 )
		CollideFlags ( 39 )
		StaticFlags ( 00100000 )
		Position ( 241.337 0.973006 850.545 )
		QDirection ( 0 -0.0309652 0 0.99952 )
		VDbId ( 4294967295 )
	)
Jan
Attachments
Screen Shot 01-13-23 at 01.25 PM.JPG
Screen Shot 01-13-23 at 01.25 PM.JPG (244.68 KiB) Viewed 26693 times

ADITYA3191
Posts: 35
Joined: 19 May 2020, 13:46
Hello Kapitaen, Thank you so much for briefly explaining the issue. As you said there is no option to solve this, we will build the route again from last backup. Can you please tell me the name of software you are using to view tsection.dat ?

Kapitaen13
Posts: 46
Joined: 16 Jan 2019, 15:21
Hallo ADITYA3191,

the free text editor used is called ConTEXT. https://www.contexteditor.org/

A syntax highlighting for MSTS files is available in my forum. https://the-train.de/downloads/entry/9244-msts-context/ :)

Image

Post Reply