So last night I was streaming League of Legends and noticed after I updated OBS, when ever I was done with a match and headed into a new one the game capture would freeze and not work. I would have to re close the game capture and then re add it to make it work again. Is anyone aware of this issue? I will post a link to the stream showing this problem if needing to see it. Just want to make sure I can get this corrected.
Bug Report Game Capture in New Update
- Thread starter Darsay
- Start date
http://www.twitch.tv/darsay28/c/4461484 <---- example 1 I played the entire match not knowing game capture wasn't working properly.
http://www.twitch.tv/darsay28/c/4461492 <----- example 2. This time I noticed I was in match and it wasn't popping up. Had to delete and re add game capture.
http://www.twitch.tv/darsay28/c/4461508 <----- example 3. Realized I was 19 minutes into the match and was not working properly.
This continued all night so was trying to get some fixes
http://www.twitch.tv/darsay28/c/4461492 <----- example 2. This time I noticed I was in match and it wasn't popping up. Had to delete and re add game capture.
http://www.twitch.tv/darsay28/c/4461508 <----- example 3. Realized I was 19 minutes into the match and was not working properly.
This continued all night so was trying to get some fixes
Makkusu
New Member
I am going to put my spoon in this soup and say I am having the same issue. Win 8.1 Pro 64bit. I have to delete the game capture and add a new one and that will re capture the game client. I tried adding it as a global source and deleting/adding that same global source but it doesn't work, I have to manually ad the game capture from 'scratch' every time.
Since people keep posting here, I'll tell you what's going on. Riot changed something a month or so ago, so everyone who was using a single scene for LoL no longer works. It's best to have your window capture of the client on one scene and the game capture on another scene. That way, the game capture re-initializes every time you go into game. Use the scene switcher to switch between scenes automatically.
This might get fixed in the next OBS release, but I'm not sure.
This might get fixed in the next OBS release, but I'm not sure.
Finally found someone with the same problem as me. Running OBS on W7.
And as I had previously set up my Scenes and Sources. I didn't know. Until someone told me in the chat.
That they couldn't see the game. I have Window Capture on the client, which they can see "The Lobby" in League of Legends and such. And then above the Window Capture, I use Game Capture for the In-Game view.
So whenever I go from The Lobby to In-Game. It would show automatically and immediately.
Now I have to Manually change it, by ticking Off the box and ticking On the box again.
It's quite annoying for me, cause I'm still used to it doing auto, so most of my games on my stream are nothing but a freezing champ select with my Playlist in the background. LOL!
I read the previous mod post, about using 2 scenes instead of 1. But like I said.
As I minimize OBS (to lag less in-game), I tend to forget and it has to be done Manually.
Hope that y'all fix this asap!
Sorry for bumping, just wanted to let ya know that it's still there.
And as I had previously set up my Scenes and Sources. I didn't know. Until someone told me in the chat.
That they couldn't see the game. I have Window Capture on the client, which they can see "The Lobby" in League of Legends and such. And then above the Window Capture, I use Game Capture for the In-Game view.
So whenever I go from The Lobby to In-Game. It would show automatically and immediately.
Now I have to Manually change it, by ticking Off the box and ticking On the box again.
It's quite annoying for me, cause I'm still used to it doing auto, so most of my games on my stream are nothing but a freezing champ select with my Playlist in the background. LOL!
I read the previous mod post, about using 2 scenes instead of 1. But like I said.
As I minimize OBS (to lag less in-game), I tend to forget and it has to be done Manually.
Hope that y'all fix this asap!
Sorry for bumping, just wanted to let ya know that it's still there.
This should be fixed in the latest test build: https://obsproject.com/forum/threads/obs-0-63b-test-1.17349/