GUI will not start when I remove monitors

[KDCarey]

I made a recent change to my config - I added all three of my screens as video sources. It worked well until I took my laptop on the road for a business trip and disconnected it from the hub that had the additional two monitors. OBS starts but no UI. When I reconnect the laptop (MAc) back to the hub then OBS works as expected. The obvious answer (I believe) is to reconnect to the hub, remove the external monitors as video sources and presumably all will be well. However, I am once again on an extended trip and will not be able to get back home to reconnect for a few weeks and I need to do presentations almost daily until then. Is there any way for me to modify these settings to remove the screen sources through the config files so I can get OBS working again before I return home? I could not find any documentation on this. Thank you.

 

[KDCarey]

I think I found the answer although It was lucky as I made some educated guesses on how to resolve the issue by modifying the config files.

In directory: ~/Library/Application Support/obs-studio/basic/scenes I found a .json file that I thought had my configuration information. I edited (removed) a few sections that referenced the screens as input sources:

In the "sources" section I removed all objects from the array that referenced the screen captures. I then also removed all references from "scene_order" for the scenes that used these sources. One edit and it all seemed to work!

My Question now is if this is a bug. It seems OBS will not function if your config references a screen that is no longer attached.

 

[KDCarey]

Should I report a bug for this?
Issue: When a screen is set as a source for the profile in use and then OBS is started without that screen attached it crashes and prevents the UI from starting.
Example steps to reproduce: While connected to a doc with an additional monitor set the additional monitor as a source. Then stop OBS, disconnect from the doc and restart OBS - it will not start.

 

[suds]

I just had the same issue. Thank you for the heads-up!
Please open a defect if you haven't yet.

[edit to add: luckily I had an old config file backup from April in the specified folder I could go back to]