[roeter]

Under very specific circumstances, TSRE creates a tdb entry with 'nan' as value for vector data.

What happened is that very occasionaly I had the problem that a track section could not be added to the tdb - after pressing 'Z', the 'yellow line' would still not be shown.
I decided to save my route with a section stuck in that situation, and found that after that, TSRE would no longer load my route but would immediately crash when the route was opened.
I then opened the route in OR itself - the OR logic is more robust in handling invalid data. Thus it showed that the vector data for this section of track contained 'nan'.
The problem occurs when the X and Y direction vectors of the track have almost the same value (that is, the angle of the section is 45, 135, 225 or 315 degrees), and the section has an elevation > 0.5 degrees.

Below is the world-file entry of the offending section as well as an extract of the .tdb showing the 'nan' value.

		TrackNode ( 12718
			TrEndNode ( 0 )
			UiD ( -10421 14919 252 1 -10421 14919 nan 25.792046 nan 0.007000003 nan 0 )
			TrPins ( 1 0
				TrPin ( 13280 0 )
			)
		)
...
		TrackNode ( 13280
			TrVectorNode (
				TrVectorSections ( 1 29618 24034 -10421 14919 252 0 1 00 -10421 14919 nan 25.974375 nan 0.007000003 nan 0 )
			)
			TrPins ( 1 1
				TrPin ( 13490 1 )
				TrPin ( 12718 1 )
			)
		)

	TrackObj (
		UiD ( 252 )
		SectionIdx ( 24034 )
		Elevation ( 0 )
		CollideFlags ( 39 )
		FileName ( VM1t150r10d.s )
		StaticFlags ( 00200180 )
		Position ( 751.464 25.9744 -39.4462 )
		QDirection ( 0.00247382 0.707401 -0.00247591 -0.706804 )
		VDbId ( 4294967295 )
	)

Regards,
Rob Roeterdink

[Goku]

I know about this issue, but I saw it only when experimental flex dynamic track was used.
I will look at your case.