Lapppy
Member
Sometimes when a Game Capture source is set to 'Capture any full screen application', the game capture will for whatever reason successfully hook into Windows Explorer (Explorer.EXE).
It will keep this hook until the game capture source is removed, OBS is closed/reopened, or if 'capture any full screen application' is toggled. If another full screen app is started, the game capture does not switch to the current full screen app and instead is hooked on Explorer.EXE. This has lead to some accidental recordings of just black video...
I'm pretty sure that there is absolutely no good reason to game capture Windows Explorer.
---
The log shows a game capture source hooking into Explorer.EXE after failing to hook into VLC while I watch back a recording I did earlier. I then attempt to play League of Legends, but the hook stays on Explorer.EXE.
After the game, I check the log to see that game capture had not hooked into the game. I toggled the 'capture any fullscreen app' setting and play another game, and this time game capture properly hooks into the game.
---
EDIT: This will be fixed in the next version (0.16.0). Thanks!
It will keep this hook until the game capture source is removed, OBS is closed/reopened, or if 'capture any full screen application' is toggled. If another full screen app is started, the game capture does not switch to the current full screen app and instead is hooked on Explorer.EXE. This has lead to some accidental recordings of just black video...
I'm pretty sure that there is absolutely no good reason to game capture Windows Explorer.
---
The log shows a game capture source hooking into Explorer.EXE after failing to hook into VLC while I watch back a recording I did earlier. I then attempt to play League of Legends, but the hook stays on Explorer.EXE.
After the game, I check the log to see that game capture had not hooked into the game. I toggled the 'capture any fullscreen app' setting and play another game, and this time game capture properly hooks into the game.
---
EDIT: This will be fixed in the next version (0.16.0). Thanks!
Last edited: