For some reason I seem to get very slight frame skips every 5 to 10 minutes in my stream due to GPU overload, yet I'm running an rtx2080 super and it's showing no sign of overloading, it only rarely happens randomly. It's the only problem I have left with my stream, everything else seems to be running smoothly, it shows where the frame skips happen in the log "Warning: EOI missing, emulating". So if someone could take a look at the log for what might be causing that problem and find a potential fix, that would be amazing! Thanks in advance! I've also attached the file in case the link doesn't work.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Small rendering Lag during stream (Log attached)
- Thread starter Laifu
- Start date
D
Deleted member 121471
Under NVENC encoder settings, use "Quality" preset and disable "Psycho Visual Tuning".
Thanks so much, I have changed the settings, I shall try that for next stream and see if that fixes the problem :DUnder NVENC encoder settings, use "Quality" preset and disable "Psycho Visual Tuning".
I tried streaming with the new settings today and the lag problem still happened, I can't see a reason why that would be happening, so I've attached today's log if you could maybe find something in it?Under NVENC encoder settings, use "Quality" preset and disable "Psycho Visual Tuning".
D
Deleted member 121471
You could check if "Game Mode" is turned on in your Windows 10 settings and if power management is set to "Max Performance", in yout NVIDIA control panel.
Other than that, the only things left to try are to cap your ingame FPS to a multiple of your capture FPS, so 60 or 120FPS and, last case scenario, create a fresh scene collection with only your game capture source added, test for issues, add cam source, test again and so on until the log starts registering the issue described.
Other than that, the only things left to try are to cap your ingame FPS to a multiple of your capture FPS, so 60 or 120FPS and, last case scenario, create a fresh scene collection with only your game capture source added, test for issues, add cam source, test again and so on until the log starts registering the issue described.
Nothing worked, so I ended up taking your last approach and it just seems like my gpu can't keep up with having 6 scenes at once, does this sound correct to you? Is there a way to have the scenes not run in the background as much? And if not would upgrading from my rtx2080 super graphics card fix this issue?You could check if "Game Mode" is turned on in your Windows 10 settings and if power management is set to "Max Performance", in yout NVIDIA control panel.
Other than that, the only things left to try are to cap your ingame FPS to a multiple of your capture FPS, so 60 or 120FPS and, last case scenario, create a fresh scene collection with only your game capture source added, test for issues, add cam source, test again and so on until the log starts registering the issue described.
D
Deleted member 121471
Scene sources are generally an issue when you have multiple capture sources in the same scene, which is not your case. Your current hardware should be more than capable (in theory), which leads me to believe the issue is something the OBS isn't engineered to collect as data in its session log. However, I could be missing something I'm not familiar with in said logs.
The last things that come to mind is disabling hardware acceleration in your internet browser of choice, disabling any and all overlays that are active, such as GeForce Experience, discord, steam, etc and/or reducing the number of browser sources (Alerts, overlay, etc...) and testing again.
For example, when I used to have stream overlays, popups and so on, I switched to Streamelements because I could have them all as a single source, which helped smooth things out on a system much slower than yours.
The last things that come to mind is disabling hardware acceleration in your internet browser of choice, disabling any and all overlays that are active, such as GeForce Experience, discord, steam, etc and/or reducing the number of browser sources (Alerts, overlay, etc...) and testing again.
For example, when I used to have stream overlays, popups and so on, I switched to Streamelements because I could have them all as a single source, which helped smooth things out on a system much slower than yours.
I really appreciate the help! I disabled hardware acceleration and if that isn't enough I'll consider switching to Streamelements, because that sounds like that might help a lot as well!Scene sources are generally an issue when you have multiple capture sources in the same scene, which is not your case. Your current hardware should be more than capable (in theory), which leads me to believe the issue is something the OBS isn't engineered to collect as data in its session log. However, I could be missing something I'm not familiar with in said logs.
The last things that come to mind is disabling hardware acceleration in your internet browser of choice, disabling any and all overlays that are active, such as GeForce Experience, discord, steam, etc and/or reducing the number of browser sources (Alerts, overlay, etc...) and testing again.
For example, when I used to have stream overlays, popups and so on, I switched to Streamelements because I could have them all as a single source, which helped smooth things out on a system much slower than yours.