The TSO Situation

Well, Auran game back to me with that fix for the TSO issue, but it's a two step process that required modifying the config.txt of the scenario and renaming the tso file.

That's a two step process.

I think I am going to go with Bloodnok's suggestion of making a copy of the TSO file - it's easier, is a one step process and ensures future compatibility for when the issue is eventually fixed.

So, here's what I'm doing in future scenarios ...

Make a copy of the TSO file.
Rename the copy to KUID userid number.tso
Package up in CDP

Works great, and costs about an extra 20-50k depending on the original TSO file.

I found out some time if you export data from trainz it will not work all the time and if you get a error is some tyime due to the map. the config file is not up to date. so just copy the file to a backup folder and reExport it and look in the config.tx file to see what the map kuid number is. then copy that map kuid number to you backup config file and the copy the file back to the scenario folder and it will work ok.

Go into the code, and where it tries to load the map (right near the top) change the space in the name to be an underscore.

Peter5 was kind enough to assist me here.
I send the file to him and the scenario refused to load for him until he did this:

1. Re-export the scenario with a different name
2. Copy the train kuids in the config folder into the new export.
3.Did the same for the create consist

Re-launch the new export and now it runs.

I exported a scenario overwriting an existing one.
When I tryed to load the scenario I got the message "Can not load scrip file for.....".
So I have noticed that if you try to overwrite an existing scenario exporting the layout directly from surveyor, Trainz does not overwrite all existing files (it overwrites only the tso file) and thus the error. So I learned that first it is better delete all scenario folder and then recreate it by exporting the desired map and then copying inside your script files.

The brew crew have thought this over I guess.
I find out that the first export creates all the nescesarry files. All other exports only regenerate the tso and name file. Look at the file details (date and time) and you can verify this for yourself.

Suppose everything should be exported again, its should overwrite the script you created proberly late at night and ruin your config with the list of kuid's for the trains.

what I have found out is that the Config.txt and *_name.tx and .GSL file need to be delete as the Trainz make a new KUID number for scenario when Exporting new object and if the KUID is not the same as the Trainz one it will give you a error when loading up the scenario.


				*TRAINZ ASSISTANCE COMMUNITY* *The TSO Situation*



	Home The TSO Situation \| GS Programmers \| Scenario Tutorial \| Time Chart \| Scenario Screenshots \| Signals & Junctions \| troubleshooting \| links


		I decided to do a page only on the TSO file, which can easily become puzzled to a newcomer and advance programmers alike. The TSO Situation is a problem that scenario creators have been dealing with for some time now. Basically, the TSO file refuses to load your scenario even after the compile detected your scenario wwithout errors. the compile detected no errors. Below are collections of solutions:



		SHUTTER Well, Auran game back to me with that fix for the TSO issue, but it's a two step process that required modifying the config.txt of the scenario and renaming the tso file. That's a two step process. I think I am going to go with Bloodnok's suggestion of making a copy of the TSO file - it's easier, is a one step process and ensures future compatibility for when the issue is eventually fixed. So, here's what I'm doing in future scenarios ... Make a copy of the TSO file. Rename the copy to KUID userid number.tso Package up in CDP Works great, and costs about an extra 20-50k depending on the original TSO file. SPEIC I found out some time if you export data from trainz it will not work all the time and if you get a error is some tyime due to the map. the config file is not up to date. so just copy the file to a backup folder and reExport it and look in the config.tx file to see what the map kuid number is. then copy that map kuid number to you backup config file and the copy the file back to the scenario folder and it will work ok. BLOODNOK Go into the code, and where it tries to load the map (right near the top) change the space in the name to be an underscore. ISH5 Peter5 was kind enough to assist me here. I send the file to him and the scenario refused to load for him until he did this: 1. Re-export the scenario with a different name 2. Copy the train kuids in the config folder into the new export. 3.Did the same for the create consist Re-launch the new export and now it runs. FROM AUDACE I exported a scenario overwriting an existing one. When I tryed to load the scenario I got the message "Can not load scrip file for.....". So I have noticed that if you try to overwrite an existing scenario exporting the layout directly from surveyor, Trainz does not overwrite all existing files (it overwrites only the tso file) and thus the error. So I learned that first it is better delete all scenario folder and then recreate it by exporting the desired map and then copying inside your script files. HUNTER58 The brew crew have thought this over I guess. I find out that the first export creates all the nescesarry files. All other exports only regenerate the tso and name file. Look at the file details (date and time) and you can verify this for yourself. Suppose everything should be exported again, its should overwrite the script you created proberly late at night and ruin your config with the list of kuid's for the trains. SPEIC what I have found out is that the Config.txt and *_name.tx and .GSL file need to be delete as the Trainz make a new KUID number for scenario when Exporting new object and if the KUID is not the same as the Trainz one it will give you a error when loading up the scenario.



		Nov 6, 2002