Let's compare the logs from Classic and Studio and hopefully you understand better where we're coming from.
From your Classic log:
Code:
16:52:08: Number of frames skipped due to encoder lag: 3074 (33.25%)
16:52:08: Total frames rendered: 5351, number of late frames: 528 (9.87%) (it's okay for some frames to be late)
Classic was NOT functioning properly. You're skipping frames due to your system being overloaded. Classic, however, is a completely different program (Studio was a complete rewrite) so the issues that come up due to system overload are going to present themselves differently. The logs are reporting the issue all the same, though.
From your Studio log:
Code:
15:06:24.689: Output 'adv_file_output': Number of skipped frames due to encoding lag: 274 (3.8%)
15:06:24.689: Output 'adv_file_output': Number of lagged frames due to rendering lag/stalls: 100 (1.4%)
This again indicates that your computer is simply overloaded for the settings you're trying to use. Skipped frames means your CPU is overloaded, lagged frames means the GPU is overloaded.
Your CPU is an older generation i5, and your GPU is fairly dated as well. Please understand that video encoding is an extremely resource intensive process, and if you're not taking reasonable steps to ensure that your system is not already at capacity
before OBS is brought into the mix, you're gonna have a bad time. Grab a tool like HWMonitor or GPUz and start watching CPU/GPU load before and after you start OBS, your game, and then both.
As mentioned in the other thread, try turning FPS down to 30 and see if that helps the overload. You'll basically be cutting the required resources needed in half.
