I updated to the next update before service began and LOST ALL our settings!
Now you know why you don't EVER update, or change anything for that matter, right before something critical! Do it AFTER the last service, so you have all of that time to troubleshoot, and document what you have before you do it.
But DO UPDATE! Not updating is an invitation for things to break because the stuff it relies on was updated outside of your control and is not incompatible anymore, or to get hacked because people study the updates looking for problems that were fixed and thus how to get into one that hasn't been updated.
As for this particular problem, did you update from v27 or before to v28 or later? That boundary has been known for months now, to break almost every plugin, simply because it (finally!) updated the Qt graphics framework to one that is still in active support. Plugins that are built for the old Qt, as required for v27 and before, fail to load in v28 and later, so OBS doesn't include their settings when it closes and overwrites the file. At that point, they're gone forever, even if you revert to what you had before. Hence the need for documentation before updating.
To update correctly across that boundary, you need to backup everything that you have, using each plugin's tool to do that, or screenshot if necessary. Then update *both* OBS *and* all of the plugins, THEN start OBS for the first time after the update, and put all the settings back that didn't survive, using each plugin's tool or manually with the screenshots.
By the way, v28 is not the latest. We're on v29.1.2 at the time of this writing. No such problem from v28 to v29, because the Qt version hasn't changed. But still understand that updating anything is a significant risk, and you do have to update. So do it when you have loads of time to troubleshoot immediately afterwards, and backup beforehand. At the very least, keep your (independent) documentation up to date so you can rebuild from scratch quickly and completely.
(if it's not backed up or documented in a way that is easily recoverable, then it must not have been important)
This is not a solution, but it might still help if the devs would add the option:
It would be great if instead of telling us about an update when we launch the program, it would tell us right after we end the stream. When I launch obs, I'm about to use it and don't want to be held up for an unknown period of time while it updates. But generally when I end a stream I'm done...
obsproject.com
After LIVE streaming, the streams unexpectedly stops after 30 to 50 minutes!
That probably needs a log file that includes the unexpected stop.
