ShinMalphur
New Member
Hi. Basically, I'm resurrecting the following thread:
obsproject.com
I'm experiencing exactly the same issue. I've switched to OBS as an alternative to Nvidia Shadowplay. My goal is to rely on a replay buffer and keep the usability as automated as possible. Got the executable scheduled on the startup with launch options (--startreplaybuffer --minimize-to-tray), game capture on "capture any fullscreen application" to keep as little interaction with UI as possible and I highly prefer keeping things that way.
Everything works perfectly as expected; except for one specific case: OBS is constantly trying to hook into the Telegram messenger, which I have always running in the background. I'd have no problems with that if it was a foreground window since Telegram probably relies on some graphics API for media or UI acceleration, but it keeps hooking into a windowless process for media viewing, which also prevents it from hooking into the actual foreground 3D application at the same time.
My question is if there is any way to block OBS from hooking into unwanted processes since that behavior is ruining capture consistency and automation. As for now, I'm forced to use "capture application with a hotkey" as a workaround.
This behavior is inconsistent, I'll upload logs when it happens again.
Telegram Desktop causing endless loop in OBS
Hey, so I have this problem: Sometimes, when I use Telegram Desktop before starting a game, it tries to capture it (as game capture), fails and then gets stuck. 18:02:55.609: [game-capture: 'Game Capture'] attempting to hook fullscreen process: Telegram.exe 19:14:48.491: adding 21 milliseconds...
I'm experiencing exactly the same issue. I've switched to OBS as an alternative to Nvidia Shadowplay. My goal is to rely on a replay buffer and keep the usability as automated as possible. Got the executable scheduled on the startup with launch options (--startreplaybuffer --minimize-to-tray), game capture on "capture any fullscreen application" to keep as little interaction with UI as possible and I highly prefer keeping things that way.
Everything works perfectly as expected; except for one specific case: OBS is constantly trying to hook into the Telegram messenger, which I have always running in the background. I'd have no problems with that if it was a foreground window since Telegram probably relies on some graphics API for media or UI acceleration, but it keeps hooking into a windowless process for media viewing, which also prevents it from hooking into the actual foreground 3D application at the same time.
My question is if there is any way to block OBS from hooking into unwanted processes since that behavior is ruining capture consistency and automation. As for now, I'm forced to use "capture application with a hotkey" as a workaround.
This behavior is inconsistent, I'll upload logs when it happens again.