![]() ![]() One of those features that allows it to head off the competition is the use of plug-ins. ![]() It allows you to bring your stream to life, and while it has a steep learning curve compared to competitor software Streamlabs OBS and Twitch Studio, it has a number of distinct advantages. Gsync isn't supposed to have any relationship with OBS, but I'm guessing there's something at the nvidia driver level that's not playing nice with certain games.Įdit: Oh yeah - if you have Geforce Experience, disable the in-game overlay.When it comes to streaming, the ultimate tool is Open Broadcast Software Studio, better known as OBS Studios. Like many of you, I'm in the boat of having no rendering lag for years, and then, suddenly, all the rendering lag. I'm still looking for a complete fix, but as of yet, there doesn't seem to be one. So, less than 1% is pretty good in my books. I can pull a 1080p 60fps stream with around. To be real, this likely won't fix all your issues - it certainly didn't fix all of mine - but it helped. For me, this would make my canvas 1440p, which is more taxing on my GPU. Conventional wisdom has you set your canvas the same resolution as your monitor, but this has always caused even more rendering lag. If you want to stream at 720p, set your canvas to 1280x720 and your output to match. If you want to stream at 1080p, set your canvas to 1920x1080, as well as the output. I don't know why the sudden change.Ĭhange your canvas size to match your output size. To be clear, I've never had an issue with Lanczos until now - even with weaker hardware. Either of the other two filters will be fine, but Lanczos seems to be a GPU destroyer when it comes to the FPS of the recording/stream. This setting has also tanked the FPS in some folks' games, so use at your own risk.ĭo not use the Lanczos downscale filter. It seems to make my streams/recordings a little smoother, but again, I could be completely wrong. ![]() ![]() Note: I'm not yet totally convinced this one helps at all it could just be placebo. If you're using Game Capture, go into the properties of Game Capture and check "limit capture framerate". If anyone is still having this issue, I can provide a few mitigating steps, but not a solid fix, should the aforementioned solutions not work for you. Tested with multiple games and both OBS Studio and Streamlabs OBS and the results are the same. And I really don't see downgrading my viewer experience as a viable solution (Not directed at you dude, just a point on workarounds vs solutions). I've capped my OBS frame rate to 30 but it doesn't help when your available range is 2 to 12 FPS. This gain is not stable though and I can't stream it. Again, leaning towards your GPU driver theory. When I switch OBS from GPU encoding to CPU on OBS settings I get a minor gain in FPS. So it isn't some internet / hardware / software issue. And I had 411 waiting for some time before installing it as a new driver usually screws something up.īefore whatever caused this to occur happened a I had a perfect streaming experience. I did update around the same time as 1809 dropped. The usual response to this is something like, "cap your FPS to reduce the overhead on your gpu." I haven't had much luck fixing it with adjusting game settings or capping FPS. I'm getting rendering lag.Īnother reason why I'm thinking this could be driver related is because this was never experienced before with the same settings, and there are posts popping up all over the place about it, even on the OBS forums - most of them recent and coinciding with these few updates. I'm willing to bet that you're experiencing the latter, but to be sure, you can check your OBS logs for it, or open the status window while you're streaming. Render delay means your GPU can't keep up. Encoder delay means that your CPU can't keep up. The lag you're experiencing is likely caused by either encoder delay or rendering delay. Updating the drivers changed which capture methods work better with certain games, hence why I'm leaning toward it being a driver issue. I'm having the same issue, but I'm not yet convinced it was the windows update that caused it, since it was happening to me before the update, as well - specifically on nvidia drivers 411.70 and 416.16. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |