grocal
New Member
I guess it's a kind of bug or at least major inconvenience.
Let's assume we have 2 scenes. Scene 1 - anything (for example just plain image). Scene 2 - game capture source with hotkey set for choosing game source to capture (F12 is default, right?). Whenever you switch scenes you always have to press hotkey again to choose game source to capture. Can OBS remember what was chosen last time and not disable game capture source every time scenes are being switched (unless last source is gone of course)? This might be a problem for anyone who switches scenes frequently without having OBS preview around (or stream preview on secondary pc/monitor). You have to remember to switch game source hotkey every time you go back to scene with "game capture" source configured to use hotkey. I've kinda lost a bunch of gameplay that way when I chose source with hotkey, switched to scene with "intermission screen" and then back to scene with game not knowing that game source reset itself to nothing.
Tested OBS versions: latest beta and 0.57.05 - all prone to that bug.
Thanks in advance for any reaction.
Let's assume we have 2 scenes. Scene 1 - anything (for example just plain image). Scene 2 - game capture source with hotkey set for choosing game source to capture (F12 is default, right?). Whenever you switch scenes you always have to press hotkey again to choose game source to capture. Can OBS remember what was chosen last time and not disable game capture source every time scenes are being switched (unless last source is gone of course)? This might be a problem for anyone who switches scenes frequently without having OBS preview around (or stream preview on secondary pc/monitor). You have to remember to switch game source hotkey every time you go back to scene with "game capture" source configured to use hotkey. I've kinda lost a bunch of gameplay that way when I chose source with hotkey, switched to scene with "intermission screen" and then back to scene with game not knowing that game source reset itself to nothing.
Tested OBS versions: latest beta and 0.57.05 - all prone to that bug.
Thanks in advance for any reaction.