Anyone else getting this - unable to load file - Tracks.bin - I have refreshed all of the DLC. Interesting is that Locoswap thinks the following: It is advertised as a EMD Norfolk Southern SD40-2 (from the Norfolk Southern SD40-2 High Nose Long Hood Forward Loco DLC) Respectfully
Is this a workshop item? If it is the issue lies within the scenario itself and not the route or included folders.
This is a purchased DLC from DTG. It was released back in July 2014. After some research it seems like this has always been an issue. A lot of the comments point to it in the Steam reviews. I was curious if there was a way to fix this. I know hat I can just hit F2 and just move on, the scenario will work. Not sure it will complete correctly and was wondering what the missing data was. https://store.steampowered.com/app/277737/?snr=1_5_9__205 Respectfully
Sorry I do not own this. At least you have a workaround and it is playable. Better than some other scenarios.
F2 opens the "Save" requester. It allows you to bypass the error box, as the simulation advances one gametic. Just press Cancel. It's also helpful when editing scenarios with scripted locos that output message boxes on the right hand side of the screen, making the flyouts inaccessible. In that case, pressing F2 will advance the simulation and the boxes will close. As to the scenario, I have wondered about that one ages ago. It seems it was changed, loco being swapped, but the ScenarioProperties.xml wasn't updated. The scenario works though. There's also a scenario in the Horseshoe Curve DLC that is from the Baldwin Centipede pack.
Yes the scenario does work, however, it will not show complete in the menu. Quite a nice scenario, also lets you dump the coal at the hopper close to the end. Wondering if the tracks.bin file and the inability to score in the menu are associated. I have noticed that multiple routes do have a tracks.bin file. Not this one though. Would like to see if one could be added correctly and would solve this? Very interesting. Something is wrong with the 'plumbing' of this scenario. I completed Take Me To The River and received a completion in the Emerald Coal Run. This so happens to be where the Locoswap thought the folder was. I am thinking that the index of the files are mixed up. I know that each scenario has its own unique reference ID (GUID) and folder. Where are these referenced? I modified my local career.xml and have fixed what is shown in Locoswap. I needed to delete my SDBCache.bin to take the effect. The DTG menu however is still pointing to the wrong file completed. Guessing this is in the Steam Cloud and is 1 step removed from accessability. Looks like some mis-management in compiling the files when the DLC was integrated into the Southern Coal route back i 2014. At least I now know how to clean up my end. Guess if I complete all of the scenarios everything will populate correctly!
"tracks.bin" errors show up when Career scenarios have been manipulated after release. Maybe this one got updated ages ago.
Oh. I don't know very specifics, but there is something curious about it I just remembered. Maybe worth investigating. For curiosity and science. I ran NSCD 2017 EOY and didn't annotate my photos. I tried to do it recently, deducing the scenario using weather, etc. I stumbled upon this scenario title either in the manual or the Steam page, but it's not consistent with the five available scenarios. There have been two LHF scenarios, either it was messed up, or it possibly required the original LHF (which is supplied by two apps now, the one for Castle Rock et al, the other for NSCD, otherwise supposedly identical, except it has the elderly SD40 sounds) and it was decided to ditch. In any event, the game hides some scenarios by default but when using certain search features, they show up. In my case, those are the ones missing the route, so starting them results in a very quick failure.
I have validated that Take Me to The River and Emerald Coal Run are mixed up. Completing one checks of the other and vise versa! One is a GE ES44 AC the other a EMD SD40. They both initiate the correct scenario however the outputs are plumbed incorrectly!
