Page 1 of 1

Default scenarios

Unread postPosted: Thu Dec 30, 2021 1:20 pm
by miata54
This has been bugging me for years snice purchasing TS . I know what the problem is but have not been able to correct/solve it. Take a look at the attached pic, Menu 1, of the TS menu and in particular the two default routes, Cajon Pass and Castlerock. Look at the top two scenarios of Cajon Pass and the top three of Castlerock. Notice the missing text for Train Name and a missing pic of the loco in the upper left hand corner. Other scenarios are complete.

I have looked at other scenario bin files to see what is missing in the subject scenarios, copying/pasting missing entries of text into the subject scenarios to see if anything at all would show up under the Train Name header. Not paying attention yet to correct syntax. Just trying to get anything al all to show up. This is the text I have been copying/pasting in the correct position referenced by a correctly structured scenario.

d:type="cDeltaString">RS_TXT_CHALLENGER</Key>

I have done the same process for the pic of the loco, but again have been unsuccessful. There have been other incomplete scenarios from both routes that I have managed to correct, but not these five.

Would someone please confirm/deny that your default Cajon Pass and Castlerock routes display the same missing text and loco pics as I have shown here? Repeated file verification from Steam always yield the same results.

Would greatly appreciate any assistance.

Thanks

Re: Default scenarios

Unread postPosted: Thu Dec 30, 2021 7:05 pm
by jlms48
My findings :
Castle Rock
Big Boy Monument FR - same for me but note this is not a default scenario with the route. came with Big Boy addon.
BNSF 1 FR Monument - same as you
G Trax FR Berkshire - this is an addon scenario which I don't have

Cajon
BNSF FR San Bernadino - Loco pcture shows EMDf7 Warbonnet but the train name text box is blank.
These are all Freeroam scenarios which don't really interest me but I hope the comparison helps.

Re: Default scenarios

Unread postPosted: Fri Dec 31, 2021 12:40 am
by Chacal
I get that with the [BNSF 1] scenarios and a few others that came with DLC other than the route itself, such as [NS Highnose] and [SD40-2 SF]. I don't have the Big Boy pack, so I don't have any [Big Boy] scenario.

Re: Default scenarios

Unread postPosted: Fri Dec 31, 2021 8:06 pm
by trev123
I have some like that on Cajon Pass but third party scenarios. I did hear that by using TS Tools you can put the thumbnails in them. Personally, I don't worry about things like that.

Re: Default scenarios

Unread postPosted: Sat Jan 01, 2022 2:01 pm
by thor1969
Mhh I think the loco name displayed in the scenario view is based on a entry in the engine's bin file named "Displayname" or so. This might be not set for some addons, I'll have to check that. If I am correct, it should be not too complicated to fix it.

he picture for the engines is a file named image.png placed in the folder, where the loco information resides. If you place a picture with this name there, it should show up. Same is valid for preview thumbnails of routes.

I'll come back after I did find out more about the displayname.

Kind regards

Thorsten

Re: Default scenarios

Unread postPosted: Tue Jan 04, 2022 1:20 pm
by thor1969
I checked my Challenger scenarios, and they show a thumbnail and also the name of the engine. So it should not be faulty by default.
You might want to try to rebuild your scenario database by deleting the SDBCache.bin in the content folder. It will create a new on start of TS. Sometimes this gets corrupted, especially if you have large amount of scenarios. Altough it can get quite large, I managed to reach it's limits. This results ins defective entries in the bin
To be safe, rename the existing bin or copy it away, so you can restore it if something gets wrong.

Kind regards

Thorsten

Re: Default scenarios

Unread postPosted: Tue Jan 04, 2022 2:49 pm
by Chacal
Also, if you swapped the player loco in a scenario using the old RW-Tools (I have not tried with the new TS-Tools), it did not update the loco's name in the scenario database. Swapping with the game's scenario editor did.