-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Large rendering lag seemingly caused by script #10
Comments
Hmm. Missed frames are usually caused by GPU overload, but the script doesn't use GPU at all. It simply accesses the values thru OBS API. The only obvious reason that I see is if your Update Delay is too small. But there is also a bug which causes the update to happen twice in a time frame instead of twice. It was not happening before, but started after specific OBS. Possibly due to changes to scripting system? Possibly the same kinda bug may happen to you? Anyway, my knowledge of lua has increased over the past year so I was thinking of rewriting the script from scratch. For now I can only suggest you to try older OBS version. |
Try new version from Release Page and let me know if the issue persists. Actually, I can see |
Sorry about the ridiculously long wait and thank you for the quick update! I did have ljsocket.lua in my scripts but has now been removed. The error still seems to persist. Screenshot![image](https://user-images.githubusercontent.com/65280024/220314941-f7c17022-0df8-41a0-b7ad-54afdeba355b.png) |
Waiting doesn't cost me anything, so no problem! :3 In fact, OBS can sometimes mess up scene/source configuration. Here's what you can try:
|
I've been noticing huge rendering lag with an average of 13.5% frames missed compared to an average of 0.6% while disabled (through the plugin).
I'm currently using OBS 23.0.3 (x64) with OBS Stats on Stream 1.3. Bot is disabled.
Here is my configuration:
This issue is also present while OBS is run in administrator mode.
Is there any solution for this and/or is there anyone else also experiencing this issue?
The text was updated successfully, but these errors were encountered: