[Laci1959]

Quote

As an additional question to David's, what is the purpose in MSTS of the .rit and .tit files? They seem to me just to repeat information contained in the .rdb and .tdb files.

It served as a kind of backup. In addition, it was used by MSTS AE for the distorted construction of the track during the construction of the activity.

[dforrest]

Laci, can you please explain what you mean by "distorted construction of the track during the construction of the activity".

[Genma Saotome]

 dforrest, on 10 November 2021 - 03:32 AM, said:

The thread has been hijacked by *_y.raw!!! Are there any more comments on .rit and .tit?

Yeah, I'll split it.

All additional comments about useless raw files should be made here.

[steved]

Just as an experiment, I went and changed the names of the .rit and .tit to .rit1 and .tit1.
Fired up ORMG and ran the route for a little while. Everything is good.
Fired up TSRE and placed a couple of items and saved. TSRE recreated both the .rit and .tit files on the save.
While OR doesn't seem to require them TSRE thinks they need to be there. For whatever reason.

Randy

[vince]

 steved, on 10 November 2021 - 01:33 PM, said:

Just as an experiment, I went and changed the names of the .rit and .tit to .rit1 and .tit1.
Fired up ORMG and ran the route for a little while. Everything is good.
Fired up TSRE and placed a couple of items and saved. TSRE recreated both the .rit and .tit files on the save.
While OR doesn't seem to require them TSRE thinks they need to be there. For whatever reason. Randy

Goku did that to keep compatibility with MSTS.

vince

[jonas]

While looking through my notes, a description from the year 2009 fell into my hands. I put the translation here:

--------------------------------------------------------

SignalItems differ in tdb and tit:
=================================

tdb->
		SignalItem (
			TrItemId ( 936 )
			TrItemSData ( 115.043 00000002 )
			TrItemRData ( -332.248 1.34109 -809.292 -5536 15046 )
			TrSignalType ( 00000001 1 3.77853 Sig25EHp_F2_Vmax_Jm )
			TrSignalDirs ( 1
				TrSignalDir ( 102 1 1 0 )
			)
		)

tit->
	SignalItem (
		TrItemId ( 936 )
		TrItemSData ( 115.043 00000002 )
		TrItemRData ( -332.248 1.34109 -809.292 -5536 15046 )
		TrSignalType ( 00000001 1 3.77853 Sig25EHp_F2_Vmax_Jm )
		TrSignalDirs ( 1
			TrSignalRDir ( -228.063 1.34109 -668.631 -5536 15046 0.646922 )
		)
	)

SignalItem entries differ in the tdb file from those in the tit file.
More precisely: In the tdb the entry in the "TrSignalDirs" token the entry is called "TrSignalDir", in the tit the entry is called "TrSignalRDir"!

In the tdb file, the 1st value in the "TrSignalDir" line denotes a TrPin from the vector part of the tdb file.
In the tit file, the "TrSignalRDir" line contains xzy values followed by tile coordinates and a (to me) unclear decimal number.

--------------------------------------------------------

I don't want to say that the tit and rit are important after all, but at least the tit doesn't seem to just contain a cloned list of the tdb. Small differences seem to exist after all. For OR, however, this should not matter.

[Laci1959]

 dforrest, on 10 November 2021 - 07:52 AM, said:

Laci, can you please explain what you mean by "distorted construction of the track during the construction of the activity".

https://kephost.net/p/2021/45/305_f036c3212f0a.png

The distance between 52.00 and 53.00 in the picture is 1000 meters, ie 1 kilometer. The distance between the two track msts is 5 m. If it were proportional, the distance between the two tracks would not be visible. By that I mean a distorted site plan. There is nothing wrong with that because it is used in many places.

[dforrest]

Sorry Laci, but I still do not understand how "it was used by MSTS AE for the distorted construction of the track during the construction of the activity" (full quote from your first post).

[Weter]

David, Laci uses online translator to express himself in English.
The "Distorted" word is usually have some negative sence, but translation software doesn't catch Laci's idea.
Hungarian language is most difficult of European languages, so no wonder, it's hard to process. (26 cases it has)
As I understand his idea, rit/tit are maybe used to build MODIFIED-proportions map for being more well-seen at AE, rather, than, e.g. Trackviewer's representation of the same small scale.

[jonas]

I'm with David here. It is still also not clear to me to what extent the distortion in the map display of the MSTS AE is caused or intended by the tit and/or rit?
I would like to understand it.