track.bin

[railduffer]

I have a route I am designing, and at the same time building scenarios. I have a scenario I have built that worked fine. I changed some lighting at a mine site, some other things. Now when I start the scenario there is a message that the scenario won't load -- it can't find "track.bin". OK what do I do? I do have RW Tools, but I don't know how to fix this problem.

Thanks for any help

[Chacal]

Look in your route folder and subfolders. Is the tracks.bin file present?

[JerryC]

The most common way to prevent this issue is to create your scenario as a standard scenario, then convert it to a career scenario AFTER you are completely finish building, tinkering, and testing it. Career scenarios do not like to be changed and will throw up a hairball if you change the scenery or rolling stock assets.

In my experience, the best way to fix a missing tracks .bin is to go into the Scenario Editor for the route that is bonked, place a rolling stock asset of some kind on the tracks, then save the Scenario. Then if you don't need the Asset, delete it and save the Scenario again. You should be good to go afterwards.

[GreatNortherner]

Hi all,

This issue is, as far as I know, caused when the checksum files of the Career scenario no longer match the change dates or filesizes (or whatever) of the scenario files and probably also those of the used rolling stock (installing physics mods tends to break Career scenarios too).

There is, I think, an easier way to fix this issue that commonly comes up after editing anything in/around career scenarios: Open the scenario in the editor, go to Timetable view. Find the Script button in the upper right corner of the screen (second or third from the right), click it. It brings up a pop-up window, on it is a button "rebuild checkums" which you should click. And you're done, you don't even need to save the scenario (no changes to the scenario itself will have been made by pressing this button anyway, only the checksums will have been updated).

Cheers
Michael

[railduffer]

Thanks guys. This did occur building my first career scenario. I then re-wrote it as a standard scenario, and poof it worked fine.

Again thanks