This page is kept up-to-date with all the stuff that I'm aware of is not working correctly in the app.
If it's not mentioned here, please let me know via the Discord what's bugging you!
Mouse disappears in Main Menu
If you use RAW input in-game, the following can occur:
In rare instances at the end of a match, when returning to the Main Menu, your mouse cursor is hidden.
A quick Alt-Tab out (and back into) the game will fix it.
Unfortunately, this is an issue on Overwolf’s side of the fence, not my own. I have made them aware of this issue, and they are working on a fix.
A temporary workaround is to disable Raw Input.
No Recent Operator History
The Operator History stopped working a few weeks ago.
Ubisoft did this on their end in preparation for the new data API which launched with their new "My Siege Stats" website portal on the 20th of October.
Unfortunately, I don't have access to their new API (yet), so in the meantime Operator History is no longer tracking more recent data. I'm in talks to regain access to the Ubisoft data.
This also affects the Operator Mains info (what Operators a player favours). It also slows down the recuperation from the IQ/Caveira/Melusi/Ace bug that is still present for a few accounts (see below).
Operator Mains IQ/Ace/Melusi/Caveira
The Ubisoft Operator Use API was on the fritz a little over two months ago. It was saying everyone was playing IQ/Ace/Melusi/Caveira a lot. Basically, it took the total number of rounds you’ve ever played Caveira, and said that that’s the number of rounds you played Caveira that week.
This completely messed up the R6 Analyst calculation for everyone’s Operator Mains, as well as the Smart Ban suggestions, as they are based on the same information.
Now, the Operator Mains and Smart Bans are based on the last 320 rounds played for each player. So if at least 320 rounds have been played for an account in the past month-and-a-half (since the Ubi API was fixed) then the issue is no longer present for that account.
Unfortunately, the API freeze as mentioned above slows down this recovery until the API starts providing new info again.
Sixth-Pick tracking doesn't work in the first round
In the first round, sixth-pick tracking can be erroneously assigned to the wrong player/Operator.
This is caused by a mismatch in "timing". Basically, if the Operator Banning phase goes quicker than expected (all 5 teammates vote on same Operator in quick succession) the app is unsure exactly when the Sixth-Pick phase begins.
Unfortunately, until Overwolf allows for more granular phase detection (e.g. "Operator Ban Phase", "Operator Selection Phase", "Opeator Reveal Phase", "Operator Sixth Pick Phase"), this is impossible to solve reliably.
Wrong Plant Detection
In very rare instances, the app tracks a defuser plant when this is not the case.
From testing, this occurs when an attacking player "locates" both bombs within 25ms of eachother (either by walking into site, or by droning into site) during the Action Phase.
I'm looking into ways to counteract this rare issue.