Fenrir
Forum Admin
05/04/2017 - UPDATE4: We are actively engaged with Avast on trying to solve the webcam issue with the 18.0.2 update. This is not isolated to OBS, but several other programs (including ManyCam) are reporting the same issues. If you do not use Avast (or similar, such as AVG), you can safely manually update to 18.0.2 with the below link.
05/03/2017 - UPDATE3: The update has been pulled until AV vendors have a chance to respond to us. In the meantime, if you want to manually update the build is available here: https://github.com/jp9000/obs-studio/releases/tag/18.0.2
05/02/2017 - UPDATE2: A potential issue with some poorly coded antivirus programs has caused us to halt rolling out the update. Please stand by until we can find a solution to this issue.
05/02/2017 - UPDATE: A fix has been implemented and released in 18.0.2 that fixes the Game Capture for 32bit DirectX9 games, such as CS:GO and League of Legends. Please update as soon as you are able, the auto-updater should prompt you to update the next time OBS is launched.
If you are having performance issues after updating, it is not related to this bug, but rather something else. Please make a new thread with details, and as always, include a log.
What we know:
The Creator update for Windows 10 has been confirmed to cause an issues with the methods OBS uses to capture specific games (not all) with the Game Capture source. This is manifest by forcing the Game Capture source to fall back on memory capture, instead of shared texture capture. This is FAR less efficient, and can cause a significant performance loss in both OBS and your games.
The issue is being actively looked in to, and data is being collected. It appears that 32-bit DirectX 9 games are affected, including but not limited to:
What we do not know:
We do not currently have the full details on what causes this to happen. If you are experiencing this issue, and wish to help, see the below section and provide a log for us.
How can I fix it?
At this time there is not enough data to determine the cause, so there is no actual fix. However, there are a few things you can do to work around the issue.
If you play your game fullscreen, you can use Display Capture to capture your game instead. You can also play your game windowed or borderless windowed and use Window Capture.
We know this is not ideal, and will update this post as soon as a fix is made available.
What can I do to help?
Sit tight! We have all the logs and information we need at this point, but feel free to report any additional issues you may encounter.
I will do my best to keep this thread updated with any additional information or workarounds we are able to find. Please try to keep this thread on topic. I will be monitoring this thread and actively removing off-topic posts.
05/03/2017 - UPDATE3: The update has been pulled until AV vendors have a chance to respond to us. In the meantime, if you want to manually update the build is available here: https://github.com/jp9000/obs-studio/releases/tag/18.0.2
05/02/2017 - UPDATE2: A potential issue with some poorly coded antivirus programs has caused us to halt rolling out the update. Please stand by until we can find a solution to this issue.
05/02/2017 - UPDATE: A fix has been implemented and released in 18.0.2 that fixes the Game Capture for 32bit DirectX9 games, such as CS:GO and League of Legends. Please update as soon as you are able, the auto-updater should prompt you to update the next time OBS is launched.
If you are having performance issues after updating, it is not related to this bug, but rather something else. Please make a new thread with details, and as always, include a log.
What we know:
The Creator update for Windows 10 has been confirmed to cause an issues with the methods OBS uses to capture specific games (not all) with the Game Capture source. This is manifest by forcing the Game Capture source to fall back on memory capture, instead of shared texture capture. This is FAR less efficient, and can cause a significant performance loss in both OBS and your games.
The issue is being actively looked in to, and data is being collected. It appears that 32-bit DirectX 9 games are affected, including but not limited to:
- Counter-strike: Global Offensive
- League of Legends
- Rocket League
- The Witcher
- Bioshock 1 and 2
What we do not know:
We do not currently have the full details on what causes this to happen. If you are experiencing this issue, and wish to help, see the below section and provide a log for us.
How can I fix it?
At this time there is not enough data to determine the cause, so there is no actual fix. However, there are a few things you can do to work around the issue.
If you play your game fullscreen, you can use Display Capture to capture your game instead. You can also play your game windowed or borderless windowed and use Window Capture.
We know this is not ideal, and will update this post as soon as a fix is made available.
What can I do to help?
Sit tight! We have all the logs and information we need at this point, but feel free to report any additional issues you may encounter.
I will do my best to keep this thread updated with any additional information or workarounds we are able to find. Please try to keep this thread on topic. I will be monitoring this thread and actively removing off-topic posts.
Last edited: