qhobbes
Active Member
1. The Hardware-accelerated GPU scheduling ("HAGS") feature in Windows is currently known to cause performance and capture issues with OBS. It's an experimental feature and we recommend disabling it via these instructions.
2. In Windows, we recommend that "Game Mode" be enabled. Game Mode can be enabled via the Windows 10 "Settings" app, under Gaming > Game Mode.
3. Audio buffering hit the maximum value. This is an indicator of very high system load, will affect stream latency, and may even cause individual audio sources to stop working. Keep an eye on CPU usage especially, and close background programs if needed.
Occasionally, this can be caused by incorrect device timestamps. Restart OBS to reset buffering.
Source affected (potential cause): Desktop Audio
4. Run OBS as Administrator. Right click on the OBS shortcut, properties, advanced, check box, ok, apply, ok.
5. The log contains an Auto-Config Wizard run. Results of this analysis are therefore inaccurate. Please post a link to a clean log file.
To make a clean log file, please follow these steps:
1) Restart OBS as Admin.
2) Start your recording for at least 30 seconds (if possible). Make sure you replicate any issues as best you can, which means having any games/apps open and captured, etc.
3) Stop your recording.
4) Select Help > Log Files > Upload Current Log File. Send that link here. If OBS crashes, re-open it and Select Help > Log Files > Upload Current Last File.
2. In Windows, we recommend that "Game Mode" be enabled. Game Mode can be enabled via the Windows 10 "Settings" app, under Gaming > Game Mode.
3. Audio buffering hit the maximum value. This is an indicator of very high system load, will affect stream latency, and may even cause individual audio sources to stop working. Keep an eye on CPU usage especially, and close background programs if needed.
Occasionally, this can be caused by incorrect device timestamps. Restart OBS to reset buffering.
Source affected (potential cause): Desktop Audio
4. Run OBS as Administrator. Right click on the OBS shortcut, properties, advanced, check box, ok, apply, ok.
5. The log contains an Auto-Config Wizard run. Results of this analysis are therefore inaccurate. Please post a link to a clean log file.
To make a clean log file, please follow these steps:
1) Restart OBS as Admin.
2) Start your recording for at least 30 seconds (if possible). Make sure you replicate any issues as best you can, which means having any games/apps open and captured, etc.
3) Stop your recording.
4) Select Help > Log Files > Upload Current Log File. Send that link here. If OBS crashes, re-open it and Select Help > Log Files > Upload Current Last File.