Problems with Smokebox Consolidation "Resolved"

[Geep20]

Just recently I tried using the Consolidation and it keeps either dumping out of the game before a scenario will load. Or if I place it into a route through the scenario editor it will run for a bit then it will dump out. Also the whistle seems to have disappeared completely but it looks like all of the proper dav files are still present in the folder for the whistle. Wondering if anyone else has run into this problem and what might the fix be? Thanks for any help!

[mrennie]

Just recently I tried using the Consolidation and it keeps either dumping out of the game before a scenario will load. Or if I place it into a route through the scenario editor it will run for a bit then it will dump out. Also the whistle seems to have disappeared completely but it looks like all of the proper dav files are still present in the folder for the whistle. Wondering if anyone else has run into this problem and what might the fix be? Thanks for any help!

I haven't had that "dumping" happen, but I'll look into it to make sure.

The problem with the whistle is caused by sound instance groups in the blueprint - it's a core code bug that was discovered recently (in time for me to remove all the instance groups from the FEF-3). It crops up when you edit a scenario and then play it immediately without going back to the main menu.

[Chacal]

What is that bug precisely?

[Geep20]

This is what it gives me when it dumps the game.

Saved dump file to 'C:\TempDump\TS2015 - v48.0a.dmp'

I just found that the NKP Berk does the same thing when trying to load a scenario also.

[mrennie]

What is that bug precisely?

The instance groups in the sound blueprints aren't handled properly by the core code, so when you go from the editor straight into play a scenario, any sounds that are referenced from an instance group are likely to be suppressed.

[mrennie]

This is what it gives me when it dumps the game.

Saved dump file to 'C:\TempDump\TS2015 - v48.0a.dmp'

I just found that the NKP Berk does the same thing when trying to load a scenario also.

I wonder if it's a problem with the particular route you're using - which one is it?

[Geep20]

It doesn't seem to matter, I have tried it both on Horseshoe Curve and Majestic Falls and the same results occur.

[mrennie]

It's a mystery.

The Connie loads fine on my computer, so I really have no idea what's wrong.

Do you know how to use LogMate.exe? If you run TS2015 with that, it could give a clue as to what is wrong.

[buzz456]

Have you run a cache verification?

[Geep20]

No I have never used LogMate.exe. Is that provided with TS?

Buzz, how do you do a cache verification? That is something else I have never done myself, just assumed that steam did that when doing updates.

[buzz456]

Open your Steam folder. Right click on on TS2015. Click local properties. Click on local files tab. One of your choices is "verify integrity of game cache." It takes quite a while. There is a progress bar down at the bottom of your screen if I remember correctly.

[Geep20]

That seems to have worked, the steamer is back up and running correctly! Of course this means I have to re-apply all of my mods which sucks.

Thanks for the help guys!

[mrennie]

That seems to have worked, the steamer is back up and running correctly! Of course this means I have to re-apply all of my mods which sucks.

Thanks for the help guys!

That's good news.

I recommend applying your mods one at a time and then testing. You never know, maybe there's something odd going on with one of them.

[buzz456]

That seems to have worked, the steamer is back up and running correctly! Of course this means I have to re-apply all of my mods which sucks.

Thanks for the help guys!

Go investigate the "Two Click" solution to getting your mods back the easy way.

[Ericmopar]

If someone already mentioned this sorry, I kinda skimmed through all this.
Did you try simply clearing the blueprint cache?
The Connie is a bit touchy when using the Editors on a route or scenario that has it. I've figured out to clear the cache first, that usually brings back the whistle.
Something has change in the editors this time around. I used to be able to restart just the game, but when editing things I now have to restart my PC, or log off then back onto my accout to get a true view of what is going on with locos, signals etc.
Restarting the game and/or Steam aren't enough.