-
Notifications
You must be signed in to change notification settings - Fork 4
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
[ Bug ] Observer tool seems to send information too slowly to the prod toolkit under specific conditions #75
Comments
From your screenshot, I can see you do not have any theme applied to the LPT yet. I know it's most probably not related, but that's sometimes where the timeouts come from. Another question is when you compare the machine where the issue is occurring and the LPT server, are the clocks in sync, or are they off? And how is it on your Windows 10 machine? |
I also tried with a theme, didn't help. I did more testing, and it seems to be related to Farsight.
and And it seems that every time I enable farsight on my windows 11 machine, it starts lagging. Here's a video: windows-11-pc-lagged_h264_preview.mp4On my windows 10 machine, it works flawlessly windows-10-pc-ok_h264_preview.mp4In both cases, I'm using the same replay, so it's not a replay issue. |
Your system clocks might be in sync but the time in the observer tool and the Windows clock is at least 2 to 3 seconds off on the windows 11 video. Could you please provide us with the version and the build of windows you are using? |
Ok, could you please change the log you added? Instead of returning just the ingame time from Farsight, please return all the data, there is a benchmark to measure how long the memory reading took. |
That's a good idea! I forgot it had a benchmark. So, i changed the log to console.log(`Farsight benchmark: ${JSON.stringify(farsightData.benchmark)}`); But it seems pretty okay, around 2.5ms for full updates
Problem still persists. I'm not sure what else i could do to try to reproduce this bug on other machines, or figure out why this is happening in this case |
From what I can tell it is not 2.5 ms instead, it means 2.5 ticks, and depending on the system that could mean several things. I will try to adjust the code so it will return ms instead of ticks in a small patch. And then we can try again. |
could you please download this version and try again on both systems? https://github.com/RCVolus/league-observer-tool/releases/tag/v6.9.2-alpha.0 |
So, with this version, windows 10 PC still works fine Now, with both systems I started getting errors with the Live Events API, it seems to be a League thing, not a LPT thing.
But that's a separate issue. Now, there's something else I noticed while testing, that might give some clues as to what's happening. Here's a video of it: 2024-01-14.12-16-28_remux_h264_crf21.-.Copy.mp4 |
Another question on that Note do you have both observer Tools running at the Same time ? |
Describe the bug
The prod toolkit updates the info on screen too slowly (such as in-game timers, etc)
The reason I think this is a
league-observer-tool
issue and not related to theleague-prod-toolkit
is that I have 2 PCs at home (connecting to the same LPT instance), and this issue only happens on one of them (my league-prod-toolkit is running on a separate ubuntu instance).This means that the in-game overlay on LPT is always delayed compared to the actual game.
Other relevant info is that when this issue happens, if I close the observer tool, but keep the LPT scoreboard still open, you can see it still updates (while delayed compared to the gameplay). So I don't know if the observer tool is sending too much data and LPT can't keep up with it or if it's something else.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
LPT scoreboard should keep up with the actual game data
Screenshots
System:
Additional context
The issue happens on my Windows 11 machine. The other PC where it runs smoothly is running Windows 10, I don't know if Windows 11 has to do somthing with it.
I tried running the observer tool with compatibility mode set to windows 8 and it didn't help. Running as admin also didn't help.
Logs didn't show any relevant info:
logs
Is there anything I can do to help reproduce this bug?
The text was updated successfully, but these errors were encountered: