Question / Help "Encoding Overload"

[Byr0]

Hello there. So I've been experimenting with recording Minecraft in a high frame rate. I have an RTX 2080 and an Intel core i7 8700 with 16GB of DDR4 RAM (8GB of which being dedicated to my Minecraft). Whenever I hit record with a frame rate higher than about 140, no matter what my bitrate is my CPU or GPU usage (depending on the encoder) shoots up to 100% with OBS using 90% of it making it impossible to run any game at the same time. Baring in mind I have only one version of minecraft open and all the other programs open are none CPU and GPU intensive. I've tried changing my priority of OBS and this does not help. I've tried using Streamlabs and I've changed versions of OBS. I also tried changing my Minecraft settings but even if my minecraft is above 1000 fps OBS still refuses to record at a high frame rate. Not really sure what the issue is, I've seen countless other people record Minecraft with a frame rate of up to 560 or 480 with worse Graphics Cards and pretty much identical CPUs. Perhaps it's just my specific components or I need to go to a much older version of OBS but if anyone has any suggestions then please let me know.

 

[Tarumes]

Hello

please read pinned posts they say provide a logfile
https://obsproject.com/forum/threads/please-post-a-log-with-your-issue-heres-how.23074/

Please try to include a recording/streaming session when you experience problems while streaming or recording,
as OBS only writes important performance data during recording or streaming sessions.

If you have solved your problem yourself, please let the others know how you did it If someone else has the same problem,
he will find your post, read it through, is no step closer to solving it, and has wasted some time.

 

[Byr0]

Ok thanks for that. Solved the issue by myself anyway - was a very easy issue to solve (simply going back a few versionsof OBS) so my logs would not have made that discovery any easier lol. I'll make a bug report at some point and include my logs there.

Edit: The issue is back so I'm making a new support thread.