-
Notifications
You must be signed in to change notification settings - Fork 19
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
% Desync #177
Comments
Are you using v15.9.0? |
Maybe having other non-drop livestreams open affects it? |
New Error code 22:32:17: ERROR: Exception in task |
That looks like you have problems with your ISP. I'll leave it open if more people report this. |
I have a % desync too, but i didn't have the error code of T4bletopG4mes. This problem is since today. I haven't had this problem in the last few days. Edit: Jumped actually from 80/120 to 71/120 |
Okay today I got this error, that posted T4bletopG4mes.
|
The error could be unrelated but desync seems to happen, although its probably more Twitch's than TDM's fault. |
Description
There seems to be a sync problem where TDM thinks it has mined a larger % than what the drops inventory shows.
To Reproduce
Mine any drop I guess.
Expected behavior
Show a similar percentage to twitch drops inventory page (browser).
Observed behavior
I have noticed the percentage deviating for up to 4% from what the inventory page shows (having seen what TDM shows, reloading the twitch inventory page on my browser and seeing what it shows there). It eventually catches up, however this causes problems when a stage is close to 100% since TDM says there are 0 seconds left but of course it cant claim the drop since on twitch's end there is 1% or more left. This is quite annoying when it happens to very time limited drops like the Warframe ones.
Screenshots
No response
Logs
No response
OS
Windows 10 (64-bit)
Build
.exe
Version/Commit
Both latest dev build and stable release
Additional context
Could be related with the "Cannot connect to Twitch, retrying" error
The text was updated successfully, but these errors were encountered: