There are plenty of tutorial videos out there for how to build a bundle with Unity. We may be creating a tutorial video on how to specifically do that with this mod in the future.
Question about disabling the mod. I also noticed that with the recent update, the bell would occasionally be silent. I figured I'd just disable the mod until there was an update so I switched back to the default bell on every one of my engines. Then I saved the game and returned to the main menu before disabling the mod through the UMM console. After restarting the game I was unable to load into my save without the game crashing. Re-enabling the mod allowed me to load the save.
Edit- Went through all the same process again and was able to get my save working properly with the mod disabled. Not sure what was different this time around, it's entirely possible that I screwed something up before and that was what caused it. Either way, I don't seem to be having the issue now so it's potentially resolved.
bug has been found. With the newest update to the experimental branch the bell sounds don't play. The only fix I've found is reinstalling the mod but it breaks again not long after
A bug has arisen due to the newest patch of the game wherein engines still fitted with the default bell will not make any bell sounds until the bell is changed and the engine unloaded and then reloaded
I just want to voice my appreciation and thanks for the inclusion of ACL 250's bell. The Wilmington Railroad Museum and that engine have been important to me for a long time. I just rang the bell last month while visiting, and the recording is spot-on. I do feel like some of the other recordings could be cleaner, but for the game's first bell mod this is great.
14 comments
We may be creating a tutorial video on how to specifically do that with this mod in the future.
Edit- Went through all the same process again and was able to get my save working properly with the mod disabled. Not sure what was different this time around, it's entirely possible that I screwed something up before and that was what caused it. Either way, I don't seem to be having the issue now so it's potentially resolved.