[jared2982]

I was wondering if there is a limit to the number of items that TSRE will read in a .ref file? I entered a new model into my .ref file earlier today only to find that it does not show up in the TSRE menu. I opened the .ref file again to check for errors and found none. However if I delete another entry from the file then the new entry shows in the list and is available to be placed. Anyone shed some light on this?

[steved]

How many items do you have in your ref file.
I have well over 3000 with no errors.
I know that with Route_Riter a formatting mistake will prevent following items from showing but I'm not sure about TSRE.

Steve

[ebnertra000]

A formatting error will blind TSRE to everything below it, as well. To my knowledge there is no limit to the size of the .ref file

[xavivilla]

In the path that I contribute, the .ref file has 6329 entries and growing without problems in TSRE.

[Genma Saotome]

TSRE is perfectly comfortable with .ref file entries recorded on a single line. IMO that is much easier to read so long as your editor will display more than 80 characters per line. I have 4700 lines in my largest /ref file which includes a hundred or so blank lines. No problems... until I goof a closing parenthesis.

FWIW it is also ok to have world file entries on one line and OR is ok with the tsection file having entries on one line. TSRE will return everything to multiple lines when it writes that file again. The advantage to occasionally doing these adjustments comes if you want/need to do sorting and/or putting a copy into excel.

[roeter]

There's a tool called 'refclean' which might help sorting out the ref file. It checks the entries, sorts them per class and alphabetacally on filename within a class. It's still available on trainsim.com.
I always use it after making additions to my ref file so as to keep that file in at least some sort of decent order.

Regards,
Rob Roeterdink

[Genma Saotome]

An example of the ref file when things are on one line -- some shapes telling me what street I'm on:

Static ( Class ( Cal-P_Streets ) Filename ( R_Roosevelt.s )		Description ( "R - Roosevelt" ))
Static ( Class ( Cal-P_Streets ) Filename ( R_Sanford.s )		Description ( "R - Sanford" ))
Static ( Class ( Cal-P_Streets ) Filename ( R_San_Carlos.s )	Description ( "R - San Carlos" ))
Static ( Class ( Cal-P_Streets ) Filename ( R_Seaver.s )		Description ( "R - Seaver" ))
Static ( Class ( Cal-P_Streets ) Filename ( R_State.s )		Description ( "R - State" ))
Static ( Class ( Cal-P_Streets ) Filename ( R_Stockton.s )		Description ( "R - Stockton" ))
Static ( Class ( Cal-P_Streets ) Filename ( R_Wright.s )		Description ( "R - Wright" ))

a list of buildings:

Static ( Class ( Cal-P_B_Richmond ) Filename ( Cal-P_Michael-Pelton.s )	Shadow ( DYNAMIC )	Description ( "R- Pelton Insecticide" ))
Static ( Class ( Cal-P_B_Richmond ) Filename ( Not_Built.s )		Shadow ( NONE )		Description ( "R- Pole Yard" ))
Static ( Class ( Cal-P_B_Richmond ) Filename ( Cal-P_Pullman_Shops.s )	Shadow ( DYNAMIC )	Description ( "R- Pullman" ))
Static ( Class ( Cal-P_B_Richmond ) Filename ( Cal-P_REA_Depot.s )	Shadow ( DYNAMIC )	Description ( "R- REA Depot" ))
Static ( Class ( Cal-P_B_Richmond ) Filename ( richmond_station.s )	Shadow ( DYNAMIC )	Description ( "R- Richmond Station" ))
Static ( Class ( Cal-P_B_Richmond ) Filename ( Cal-P_Rheem.s )		Shadow ( DYNAMIC )	Description ( "R- Rheem" ))
Static ( Class ( Cal-P_B_Richmond ) Filename ( Cal-P_RSD_Whse.s )	Shadow ( DYNAMIC )	Description ( "R- RSD Warehouse" ))
Static ( Class ( Cal-P_B_Richmond ) Filename ( Not_Built.s )		Shadow ( DYNAMIC )	Description ( "R- Safeway" ))
Static ( Class ( Cal-P_B_Richmond ) Filename ( Not_Built.s )		Shadow ( DYNAMIC )	Description ( "R- Union Ice" ))
Static ( Class ( Cal-P_B_Richmond ) Filename ( Cal-P_W-R-S.s )		Shadow ( DYNAMIC )	Description ( "R- Wheeler, Reynolds & Stauffer" ))

and Berms:

Static ( Class ( SP_RBa_1t_Berms_STR ) Filename ( SP_RBa_1t_0005m_LH.s )		Description ( "SP_RBa_1t_0005m_LH" ) )
Static ( Class ( SP_RBa_1t_Berms_STR ) Filename ( SP_RBa_1t_0005m_LR.s )		Description ( "SP_RBa_1t_0005m_LR" ) )
Static ( Class ( SP_RBa_1t_Berms_STR ) Filename ( SP_RBa_1t_0005m_LX.s )		Description ( "SP_RBa_1t_0005m_LX" ) )
Static ( Class ( SP_RBa_1t_Berms_STR ) Filename ( SP_RBa_1t_0005m_NM.s )		Description ( "SP_RBa_1t_0005m_NM" ) )
Static ( Class ( SP_RBa_1t_Berms_STR ) Filename ( SP_RBa_1t_0005m_RH.s )		Description ( "SP_RBa_1t_0005m_RH" ) )
Static ( Class ( SP_RBa_1t_Berms_STR ) Filename ( SP_RBa_1t_0005m_RX.s )		Description ( "SP_RBa_1t_0005m_RX" ) )
Static ( Class ( SP_RBa_1t_Berms_STR ) Filename ( SP_RBa_1t_0005_2m_NM.s )	Description ( "SP_RBa_1t_0005_2m_NM" ) )
Static ( Class ( SP_RBa_1t_Berms_STR ) Filename ( SP_RBa_1t_0005_2m_RH.s )	Description ( "SP_RBa_1t_0005_2m_RH" ) )
Static ( Class ( SP_RBa_1t_Berms_STR ) Filename ( SP_RBa_1t_0005_5m_LH.s )		Description ( "SP_RBa_1t_0005_5m_LH" ) )
Static ( Class ( SP_RBa_1t_Berms_STR ) Filename ( SP_RBa_1t_0005_5m_LX.s )		Description ( "SP_RBa_1t_0005_5m_LX" ) )
Static ( Class ( SP_RBa_1t_Berms_STR ) Filename ( SP_RBa_1t_0005_5m_NM.s )	Description ( "SP_RBa_1t_0005_5m_NM" ) )
Static ( Class ( SP_RBa_1t_Berms_STR ) Filename ( SP_RBa_1t_0005_5m_RH.s )	Description ( "SP_RBa_1t_0005_5m_RH" ) )
Static ( Class ( SP_RBa_1t_Berms_STR ) Filename ( SP_RBa_1t_0005_5m_RX.s )	Description ( "SP_RBa_1t_0005_5m_RX" ) )

My editor will sort on selected lines so keeping things in alphabetical order is easy when everything is on one line. Alternatively a copy/paste to excel, sort, copy/paste to ref file is pretty easy too.

[jared2982]

I’m not sure how many items I have but it is only like 3000 lines total. So the number of its is way less than that. I can copy and paste the exact entry anywhere else in the ref and it works fine. I checked the entry above it 3 times for errors in formatting but it looks perfect to me. I usually just copy and paste from one of the other entries and change the fields to what I need so formatting doesn’t become a problem. I guess I’ll go back and check it again since I now know it’s not a TSRE issue. Has to be operator error.

[Weter]

I have a question:
Wether one model (s-file) might be needed in more, than one class, can it be mentioned twice in *.ref-file, or, what would be even better, can be multiple class entryes defined for that object - will it be correct? Or otherwise, have i to design some universal class names for all applications?
For example, the border poles with crossing sign may be need to pick from trackside objects for non-interactive crossing decoration, or as a part of interactive <crossing> class

[xavivilla]

There is no problem in having the same shape in two or more Classes and having the same or different Description.

The only drawback I see is that it has a larger .ref file than necessary.