Problems with Smokebox Consolidation "Resolved"

[mrennie]

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.

The only way to fix the whistle problem permanently (unless DTG fix the error in the core code) is for me to remove the instance groups from the sound blueprints. It would take me two minutes to do that, but it could take months for DTG to release the patch.

[Geep20]

Update on this problem. I ran the Consolidation on the Majestic Falls route before doing any of my mods and it worked fine. I started applying mods, first with Krellnuts 2015 sound pack and tried again on the same scenario. The problem came back and the scenario dumped me out of the game once again.. The scenario was a workshop one called Connie and Coal I believe if that helps at all. But in general this seems to be a problem with any Consolidation scenario and possibly the G-trax Berk as well.

[mrennie]

Update on this problem. I ran the Consolidation on the Majestic Falls route before doing any of my mods and it worked fine. I started applying mods, first with Krellnuts 2015 sound pack and tried again on the same scenario. The problem came back and the scenario dumped me out of the game once again.. The scenario was a workshop one called Connie and Coal I believe if that helps at all. But in general this seems to be a problem with any Consolidation scenario and possibly the G-trax Berk as well.

But you say the problem happened only after applying mods? So surely it must have something to do with applying the mods, no?

[Geep20]

Yes but just the Krellnuts sound pack nothing else was installed besides that.

I'm wondering if this has something more to do with the HSC problems that occurred for some when loading Krellnuts 2015 sounds? I remember reading that there was a problem with the coal hopper correct? I think the scenario I was attempting to run uses those hoppers in it.

[buzz456]

Krellnut sounds should have no effect on that if you have the latest version.

[Geep20]

Didn't realize there was a update to Krellnuts 2015 sounds. The H21A HSC hopper was indeed the problem and it has been resolved with the sound update install. All is good again in my little TS world, thanks all for the help and sorry to be a pain!

[mrennie]

Didn't realize there was a update to Krellnuts 2015 sounds. The H21A HSC hopper was indeed the problem and it has been resolved with the sound update install. All is good again in my little TS world, thanks all for the help and sorry to be a pain!

Maybe you could change the title of the thread by adding "- Resolved" at the end.

[Geep20]

Didn't realize there was a update to Krellnuts 2015 sounds. The H21A HSC hopper was indeed the problem and it has been resolved with the sound update install. All is good again in my little TS world, thanks all for the help and sorry to be a pain!

Maybe you could change the title of the thread by adding "- Resolved" at the end.

Done and done!

[mrennie]

Didn't realize there was a update to Krellnuts 2015 sounds. The H21A HSC hopper was indeed the problem and it has been resolved with the sound update install. All is good again in my little TS world, thanks all for the help and sorry to be a pain!

Maybe you could change the title of the thread by adding "- Resolved" at the end.

Done and done!

[Captainbob]

I am posting on this old thread because I ran into a similar issue yesterday creating a scenario on the Majestic Falls Route using the Connie. All went well for most of the day, until I added a second Connie at the end of the scenario run as a static locomotive and tender. At that point I started having a problem when I would edit and save the scenario, as soon as I hit the play button, TS2015 would lock up with the TS2015 V50.5A dmp message. I then would have to use Task Manager to close down TS2015 or sometimes reboot the computer each time. I had no mods for sound on the Connie, just the recently updated loco. After reading this thread, I decided to use RW tools and remove the 2nd Connie and Tender from the scenario, and the lock up problem instantly disappeared. I am not sure if this is a problem with more than one Connie, but I think it may have also something to do with the Majestic Falls Route, which of course users a combination of 3 different DLC routes. Maybe this combination of this particular route and multiple Connies causes instability in the scenario editor.

[mrennie]

I am posting on this old thread because I ran into a similar issue yesterday creating a scenario on the Majestic Falls Route using the Connie. All went well for most of the day, until I added a second Connie at the end of the scenario run as a static locomotive and tender. At that point I started having a problem when I would edit and save the scenario, as soon as I hit the play button, TS2015 would lock up with the TS2015 V50.5A dmp message. I then would have to use Task Manager to close down TS2015 or sometimes reboot the computer each time. I had no mods for sound on the Connie, just the recently updated loco. After reading this thread, I decided to use RW tools and remove the 2nd Connie and Tender from the scenario, and the lock up problem instantly disappeared. I am not sure if this is a problem with more than one Connie, but I think it may have also something to do with the Majestic Falls Route, which of course users a combination of 3 different DLC routes. Maybe this combination of this particular route and multiple Connies causes instability in the scenario editor.

Hmm, curious, I'll try it out myself later today. Exactly which two Connies did you use (so that I can try to reproduce it)?

[Captainbob]

I am posting on this old thread because I ran into a similar issue yesterday creating a scenario on the Majestic Falls Route using the Connie. All went well for most of the day, until I added a second Connie at the end of the scenario run as a static locomotive and tender. At that point I started having a problem when I would edit and save the scenario, as soon as I hit the play button, TS2015 would lock up with the TS2015 V50.5A dmp message. I then would have to use Task Manager to close down TS2015 or sometimes reboot the computer each time. I had no mods for sound on the Connie, just the recently updated loco. After reading this thread, I decided to use RW tools and remove the 2nd Connie and Tender from the scenario, and the lock up problem instantly disappeared. I am not sure if this is a problem with more than one Connie, but I think it may have also something to do with the Majestic Falls Route, which of course users a combination of 3 different DLC routes. Maybe this combination of this particular route and multiple Connies causes instability in the scenario editor.

Hmm, curious, I'll try it out myself later today. Exactly which two Connies did you use (so that I can try to reproduce it)?

I used the HUD version and the weathered Tender on both. The player train was located at the Y at the Wickery Hill Lumber Yard and the other Loco and tender was in the Morgan Yard at the other end of the route. I deleted the consist at the Morgan Yard end. All other rolling stock was standard freight cars that were with the route and 4 or 5 diesels which are all part of the route too.

Computer specs. Windows 7, i5 CPU, GTX 750 TI, 6 GB Ram. 64 bit.

[mrennie]

I am posting on this old thread because I ran into a similar issue yesterday creating a scenario on the Majestic Falls Route using the Connie. All went well for most of the day, until I added a second Connie at the end of the scenario run as a static locomotive and tender. At that point I started having a problem when I would edit and save the scenario, as soon as I hit the play button, TS2015 would lock up with the TS2015 V50.5A dmp message. I then would have to use Task Manager to close down TS2015 or sometimes reboot the computer each time. I had no mods for sound on the Connie, just the recently updated loco. After reading this thread, I decided to use RW tools and remove the 2nd Connie and Tender from the scenario, and the lock up problem instantly disappeared. I am not sure if this is a problem with more than one Connie, but I think it may have also something to do with the Majestic Falls Route, which of course users a combination of 3 different DLC routes. Maybe this combination of this particular route and multiple Connies causes instability in the scenario editor.

Hmm, curious, I'll try it out myself later today. Exactly which two Connies did you use (so that I can try to reproduce it)?

I used the HUD version and the weathered Tender on both. The player train was located at the Y at the Wickery Hill Lumber Yard and the other Loco and tender was in the Morgan Yard at the other end of the route. I deleted the consist at the Morgan Yard end. All other rolling stock was standard freight cars that were with the route and 4 or 5 diesels which are all part of the route too.

Computer specs. Windows 7, i5 CPU, GTX 750 TI, 6 GB Ram. 64 bit.

I'm not entirely sure if the weathered tender is compatible with the HUD version, because of it's (the tender's) scripting, but I'll try it.

EDIT: OK, I get it to crash too. I'll replace the weathered tenders with the HUD tenders and see what happens.

[Captainbob]

I am posting on this old thread because I ran into a similar issue yesterday creating a scenario on the Majestic Falls Route using the Connie. All went well for most of the day, until I added a second Connie at the end of the scenario run as a static locomotive and tender. At that point I started having a problem when I would edit and save the scenario, as soon as I hit the play button, TS2015 would lock up with the TS2015 V50.5A dmp message. I then would have to use Task Manager to close down TS2015 or sometimes reboot the computer each time. I had no mods for sound on the Connie, just the recently updated loco. After reading this thread, I decided to use RW tools and remove the 2nd Connie and Tender from the scenario, and the lock up problem instantly disappeared. I am not sure if this is a problem with more than one Connie, but I think it may have also something to do with the Majestic Falls Route, which of course users a combination of 3 different DLC routes. Maybe this combination of this particular route and multiple Connies causes instability in the scenario editor.

Hmm, curious, I'll try it out myself later today. Exactly which two Connies did you use (so that I can try to reproduce it)?

I used the HUD version and the weathered Tender on both. The player train was located at the Y at the Wickery Hill Lumber Yard and the other Loco and tender was in the Morgan Yard at the other end of the route. I deleted the consist at the Morgan Yard end. All other rolling stock was standard freight cars that were with the route and 4 or 5 diesels which are all part of the route too.

Computer specs. Windows 7, i5 CPU, GTX 750 TI, 6 GB Ram. 64 bit.

I'm not entirely sure if the weathered tender is compatible with the HUD version, because of it's (the tender's) scripting, but I'll try it.

Well this morning, I took a copy of the scenario and put two Connies where I had removed the one yesterday, in the yard, and no problem with the editor locking up. So maybe this was just a glitch in the editor yesterday, and removing the Connie fixed it.

[mrennie]

Seems to be a quirk of the editor. Before going ahead and replacing the tenders, I thought I'd just make sure the scenario still crashes after restarting TS. It didn't!

I think the editor has problems when you play a scenario directly after editing it, without first going back to the main menu, or better still, exiting and restarting. The muted whistle bug is a symptom of that quirkiness (the combination of the bug in the editor and a bug in the core coding of sound instance groups would cause sounds in instance groups to be muted).