Bug Report OBS Looms in Background Processes, Never Opens

Angelwork

New Member
Whenever I attempt to open the program, it resides in the background processes and fails to actually open.

Upon trying to open the program a second time, my computer will become unusable - the process can't be hard killed, alt F4'd, usually have to restart - even killing and reopening explorer doesn't work.

It was ultra buggy and temperamental on my computer before this "non opening" behavior began (which seems to have started after the most recent Windows 10 update). I'm not sure if it's because of SLI or Surround or MSI Afterburner, but it has historically necessitated hard reboots among other issues.

Hope we can figure out what's causing the problems. I appreciate any help you may be able to offer.

Attached are a log from before this started happening, and one from after.
 

Attachments

  • 2016-12-16 11-50-49.txt
    4.1 KB · Views: 6
  • 2016-12-11 01-02-06.txt
    14.5 KB · Views: 4

Suslik V

Active Member
Same Scene Collection?

01:02:07.320: Switched to scene 'Normal'

under the 2016-12-11-01-02-06-txt good log
Is this scene still present and has Browser Source?
There was a thread: OBS won't open the first time read it please, maybe you have similar problem.
 

C-Dude

Member
make sure minimize to system tray while strated is not checked. Also switch the render to direct3d11 instead of openGL it is much faster and better.

Also since you are getting this message in the log:

11:50:50.201: Warning: The OpenGL renderer is currently in use. On windows, the OpenGL renderer can decrease capture performance due to the lack of specific features used to maximize capture performance. The Direct3D 11 renderer is recommended instead.
 

Angelwork

New Member
Also switch the render to direct3d11 instead of openGL it is much faster and better.

Unfortunately the D3D11 renderer is completely incapable of desktop capture even with "multi-gpu fix" enabled on my machine. It's OpenGL or black screen.

Doesn't seem like that other thread actually has a solution at this time, but good to know it's being worked on.
 
Top