Hmm, After a busy few months, I'm just getting a chance to try my hand at TS2022 again and see that it has morphed Anyway, I was looking for one of my favourite scenarios, the AP one with scripted thunderstorm, but it seems to have disappeared from my scenario list - is not visible when slecting for either the train or the route. All files are updated, so have no idea where it's gone to. Anyone experiencing similar issues? APWSEP: 2O46 12:07 Sutton - Luton Route = MML - London St. Pancras to Bedford Track covered = St. Pancras - Luton Traction = Ex-First Capital Connect 319370 Year = 2015 Duration = 50 minutes
It's here: RailWorks\Content\Routes\00000034-d000-0000-0000-000000002014\Scenarios\3b3bcc71-557b-4ee3-b66b-fe6cc8d15286 Appears under MML London-Bedford Standard tab If it's on disk but not in menu, delete SDBCache.bin (make sure Steam cloud save is active) else reinstall WeatherEP.
Cheers, Torf, the folder is on by computer, but I can't find that bin file - where would it be located?
Sorry, typo. RailWorks\Content\SDBCache.bin - this is the scenario database, delete it, will be rebuilt when restarting TS. (Using the career.xml file which is saved in the Steam Cloud so you don't lose your progress / completion marks) - all missing scenarios will reappear.
I've reinstalled both 319s, the weather back, and deleted that bin file, but sadly still no luck.....
Huh? Does it appear under Build>Scenario>MML London St Pancras to Bedford>Timetabled>APSWEP:2O46... ? It has to - if there's a ScenarioProperties.xml file and a RouteProperties.xml file - the scenario WILL appear. Question: Have you manually copied scenarios once instead of cloning? This can lead to double scenario GUIDs, in that case one is disappearing, because the GUID is the only thing TS cares for when creating the database, there cannot be two of the same GUID (no matter which route folder they're in) You can do a Windows search for folders, search for Code: 3b3bcc71-557b-4ee3-b66b-fe6cc8d15286 within Content\Routes. This will not find scenarios in an .ap file, but chances are very low there is one to be found. If there is two hits then that's the reason. You then need to remove one (by cloning it and then deleting the original.) It could also be a rare case of another scenario having the same GUID by default, although chances to win the lottery are way higher than that. (GUID = 128 bit number: 340,282,366,920,938,463,463,374,607,431,768,211,456 possible GUIDs in total. Ought to be enough for everyone. More scenarios than stars in the Universe.)
Torf From the old gurus on UKTS we always deleted 2 files to clear and rebuild the scenario database cache As you say RailWorks\Content\SDBCache.bin plus the RailWorks\Content\SDBCache.bin.MD5 (ie the checksum file). Is that still relevant?
Slightly off topic, but there's a great AP forked lightning scenario for the AP class68 on Wherry Lines version 2.0 On topic.... it has nothing to do with updates to either core game or any AP product. I'm fully up to date with everything, and all is well here.
Definitely no. The MD5 file will be updated anyway when SDBCache.bin has been rebuilt. Note that I've pointed out the importance of the Steam Cloud here. It happened to others and me that the "career.xml" in Steam\userdata gets lost or corrupted. This file is responsible for the SDBCache rebuilding process taking so long, because it needs to check each ScenarioProperties.xml file for how many points scored gives which medal for inserting that information back into the scenario database. If that career.xml is lost there's no way for TS to know your progress after deleting SDBCache.bin, hence all checkmarks and medals will be gone. Btw I noticed TMCache.dat has something to do with purchasing content. It gets updated after a Steam purchase only. "T" probably means Train Simulator or Transaction, the "M" is probably standing for manifest, probably part of speeding up the DRM (manifest (=Proof of Purchase) <--> _.sbn (public decryption key) <--> GeoPcDx BLOB decryption process). If that is true I finally know the function of every single file in TS.
Thanks to everyone trying to help. It occurred to me to open TS Tools - the scenario is listed there, but I didn't see any option to clone a scenario in Tools. I copied the scenario folder and added a digit at the end, but still no joy in TS. Then of course it occurred to be to look to see if the scenario appears via the Build option in TS - thankfully the original scenario did, so I cloned a copy and lo and behold the clone appears ok in my standard scenarios. I am trying to remember if this might have been precipitated by me favouriting the scenario when I was last on - I recall I had similar issues with a Class 73 scenario that disappeared when I favourited it. Must be some sort of glitch in the handling of them. As long as I don't favourite anything, they still are listed. No idea why the scenario appeared in the list via Build but not in the Standard list though.....
Do not add a digit, you're making things even worse : The GUID must be 128 bit. You made it 132 bit. The GUID must then also be changed in the ScenarioProperties.xml (and in two different notations, a hex GUID and the same split into two 64-bit IDs), not only the folder. Clone it using TS>Build>Scenario menu.
As I say, the scenario is still in the folder, and appeared in TS Tools, and in the Build option in TS, buy just not displayed in the actual standard scenarios.
So has the folder search yielded a result (should only take seconds)? I have only this explanation that there is already a scenario using the original AP's GUID by manually copying scenarios.
Yes, it was in the folder ok. I rebuilt the XML in TS Tools, but it didn't appear still in standard scenarios. Only the Build>cloning option solved it as the cloned scenario only appears.
No I mean does the windows search give you two of those 3b3bcc71-557b-4ee3-b66b-fe6cc8d15286 folders as a result? Forgive my curiosity, but we still don't have the reason why the scenario is not in the SDBCache and thus not displays in the Standard tab. It might still be necessary to remove the standard AP scenario to avoid trouble later with one other scenario.
Yes, searched again, there is only one instance of 3b3bcc71-557b-4ee3-b66b-fe6cc8d15286 and that's in MML.
