Open delventhalz opened 9 years ago
The logs indicate that the problem is that HearthStats Companion didn't detect that you were playing in Ranked mode — it should have logged a message saying "Ranked Mode detected" before your first match, but it did not. That's why you get the "Game Mode Not Detected" popup at the end.
I haven't been able to reproduce this myself (running full-screen on OS X Yosemite) but I suspect that Blizzard may have slightly adjusted the colours on that 'play' screen in the latest release and that's making the detection of the Ranked vs Casual selection a bit unreliable. I will recalculate all the detection parameters for that which hopefully will fix it for you.
Sounds good. Happens in Arena mode too btw.
On Dec 20, 2014, at 11:12 PM, Charles Gutjahr notifications@github.com wrote:
The logs indicate that the problem is that HearthStats Companion didn't detect that you were playing in Ranked mode — it should have logged a message saying "Ranked Mode detected" before your first match, but it did not. That's why you get the "Game Mode Not Detected" popup at the end.
I haven't been able to reproduce this myself (running full-screen on OS X Yosemite) but I suspect that Blizzard may have slightly adjusted the colours on that 'play' screen in the latest release and that's making the detection of the Ranked vs Casual selection a bit unreliable. I will recalculate all the detection parameters for that which hopefully will fix it for you.
— Reply to this email directly or view it on GitHub https://github.com/HearthStats/HearthStats.net-Uploader/issues/603#issuecomment-67760483.
Hi again
While testing a fix for this, I managed to reproduce the problem once. It looks like could be a slightly different problem. If you encounter this problem again, can you please follow these steps and tell me if you have the same error that I do:
21/12/2014 11:50:11.000 pm kernel[0]: process JavaAppLauncher[46475] caught causing excessive wakeups. Observed wakeups rate (per sec): 448; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 45036
I will. I’m about to leave town for the Holidays though. I will be playing Hearthstone on a laptop during the trip, but it’s not the computer I usually play on, so it may or may not have the same issue. If it is tied to the desktop, you won’t see anything from me until January.
On Dec 21, 2014, at 6:58 AM, Charles Gutjahr notifications@github.com wrote:
Hi again
While testing a fix for this, I managed to reproduce the problem once. It looks like could be a slightly different problem. If you encounter this problem again, can you please follow these steps and tell me if you have the same error that I do:
Open the OS X Console app (it's in /Applications/Utilities) If the 'All Messages' window doesn't appear, choose 'New Log Window' from the File menu Look through the logs for the last few minutes and tell me if you see a message similar to this: 21/12/2014 11:50:11.000 pm kernel[0]: process JavaAppLauncher[46475] caught causing excessive wakeups. Observed wakeups rate (per sec): 448; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 45036 — Reply to this email directly or view it on GitHub https://github.com/HearthStats/HearthStats.net-Uploader/issues/603#issuecomment-67769662.
Been getting a glitch when playing in Fullscreen (I don't think it has happened while windowed) in version 0.21.0. A window will pop up with the error "Game Mode Not Detected", prompting me to fill in Game Mode, Rank, and which deck I was using. I won't notice this window of course until I quit Hearthstone. By then I've played a number of other games, which will all have this error in the log:
[14:02:20] Apellon's turn [14:02:20] Zenith's turn [14:02:20] Result Win detected in log file for Zenith [14:02:20] Ignoring match with duration 0 s, you should close Hearthstats Companion before Hearthstone to avoid this warning.
So I end up losing my tracking for my entire session if I don't babysit Hearthstats in windowed mode. Not ideal. It doesn't happen all of the time, but probably half of the time. I'd downgrade, but both 0.19 and 0.20 had their own issues that would result in lost matches.
Log file: