MY OBS GAME CAPTURE WILL NOT WORK JUST STAYS BLK IV DONE EVERYTHIN RAN IT AS ADMIN , TURNED UP HAWDWARE BOOST EVERYTHING STILL IS BLK HERE IS MY LOG https://obsproject.com/logs/IoXkpW0tqfTs0EMm
HELP PLEASE MAN !!!!!
- Thread starter words
- Start date
qhobbes
Active Member
1. The Hardware-accelerated GPU scheduling ("HAGS") feature in Windows is currently known to cause performance and capture issues with OBS, games and overlay tools. We recommend disabling it via this screen or these instructions as a troubleshooting step. Be sure to restart your PC after disabling it.
2. In Windows, we recommend that "Game Mode" be enabled for maximum gaming performance. Game Mode can be enabled via the Windows "Settings" app, under Gaming > Game Mode.
3. Be aware that having the Color Range set to "Full" will cause playback issues in certain browsers and on various video platforms. Shadows, highlights and color will look off. In OBS, go to "Settings -> Advanced" and set "Color Range" back to "Limited".
4. Also be aware that framerates other than 30fps or 60fps may lead to playback issues like stuttering or screen tearing. Stick to either of these for better compatibility with video players. You can change your OBS frame rate in Settings -> Video.
5. Browser hardware acceleration is currently disabled. Enabling acceleration is highly recommended due to the improvements to performance and significantly lower CPU usage for browser sources and docks. This can be enabled in Settings -> Advanced.
6. Multiple Game Capture sources are usually not needed, and can sometimes interfere with each other (Scene). You can use the same Game Capture for all your games. If you change games often, try out the hotkey mode, which lets you press a key to select your active game. If you play games in fullscreen, use 'Capture any fullscreen application' mode.
7. Window, Game and Display Capture all interfere with each other (Scene). Never put them in the same scene.
8. SLI/Crossfire Capture Mode (aka 'Shared memory capture') is very slow, and only to be used on SLI & Crossfire systems.
If you're using a laptop or a display with multiple graphics cards and your game is only running on one of them, consider switching OBS to run on the same GPU instead of enabling this setting. Guide available here.
If still having issues, provide new log.
2. In Windows, we recommend that "Game Mode" be enabled for maximum gaming performance. Game Mode can be enabled via the Windows "Settings" app, under Gaming > Game Mode.
3. Be aware that having the Color Range set to "Full" will cause playback issues in certain browsers and on various video platforms. Shadows, highlights and color will look off. In OBS, go to "Settings -> Advanced" and set "Color Range" back to "Limited".
4. Also be aware that framerates other than 30fps or 60fps may lead to playback issues like stuttering or screen tearing. Stick to either of these for better compatibility with video players. You can change your OBS frame rate in Settings -> Video.
5. Browser hardware acceleration is currently disabled. Enabling acceleration is highly recommended due to the improvements to performance and significantly lower CPU usage for browser sources and docks. This can be enabled in Settings -> Advanced.
6. Multiple Game Capture sources are usually not needed, and can sometimes interfere with each other (Scene). You can use the same Game Capture for all your games. If you change games often, try out the hotkey mode, which lets you press a key to select your active game. If you play games in fullscreen, use 'Capture any fullscreen application' mode.
7. Window, Game and Display Capture all interfere with each other (Scene). Never put them in the same scene.
8. SLI/Crossfire Capture Mode (aka 'Shared memory capture') is very slow, and only to be used on SLI & Crossfire systems.
If you're using a laptop or a display with multiple graphics cards and your game is only running on one of them, consider switching OBS to run on the same GPU instead of enabling this setting. Guide available here.
If still having issues, provide new log.