-
-
Notifications
You must be signed in to change notification settings - Fork 312
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
Ratings changes do not always trigger a new overlay #2357
Comments
It seems like the issue is that the actual rating is not in the compare string:
Neither 9.2 nor 9.5 are encoded in there, so that change, which should trigger a reapply of the overlay, doesn't. |
OK, no, the actual problem seems to be that the rating change from 9.2 to 9.5 is not recognized as a special text variable change, and it seems the wrong value is being used for the compare. If I force the rating on everything to 2.2:
Where'd that 9.2 come from? The previous rating on BB was 9.5. If I then force all ratings to 1.1:
Where did that 9.5 come from? The special text should have changed from 2.2 to 1.1. Another oddball comparison value. It's not from some other item, since they all got updated from 2.2 to 1.1. |
Version Number
2.1.0--build22
What branch are you on?
nightly
Describe the Bug
Rating is updated, then overlay is not:
These two lines:
Are log lines I added to
operations.py
to track what's going on.Relevant Collection/Overlay/Playlist Definition
Logs
https://gist.github.com/chazlarson/196adbca1213640963d1e8b18fd63695
The text was updated successfully, but these errors were encountered: