HearthSim/HSTracker

Opponent's board display is corrupted in Battlegrounds

alsospacebar opened this issue · 29 comments

Describe the bug
Opponent's board display is corrupted

To Reproduce
Steps to reproduce the behavior:

  1. Hover over an opponent who's board you've seen
  2. Look at their board display from the tracker
  3. See error

Game mode

  • Battlegrounds

Expected behavior
Show opponent's board as normal

Screenshots
See screenshot below.

Version (please complete the following information):
2.5.11

Additional context
N/A

Screenshot 2023-10-30 at 13 20 08

I have not seen this issue. Does it happen all the time or some special combination?

If all the time, what resolution are you running your monitor/display at?

Same issue here, Macbook pro 16

Yeah, i have the same issue, macbook air m2. Tried reinstalling, but that didn't help(

Must be a Mac thing... I have it too on my Mac Studio

I played last night without problems. So far nobody provided resolutions or how your display is setup.

I played last night without problems. So far nobody provided resolutions or how your display is setup.

Mac OS version : 14.0 (23A344)
Issue on both the integrated screen of macbook pro 16 (120hz) and external screen in TB4 over HDMI (1080x1200 60hz)
The whole rest of the UI is displaying OK
Screenshot 2023-11-02 at 20 27 49
Screenshot 2023-11-02 at 20 28 16
Screenshot 2023-11-02 at 20 28 20
Screenshot 2023-11-02 at 20 28 30

It looks like all the cards are stacked on top of eachother
Screenshot 2023-11-02 at 20 30 48

Does the problem happen if you run Hearthstone in windowed mode ?

Yes... I run in windowed mode, but I see it in full screen as well. Full screen is 1920 x 1080 and windowed is "custom." Medium quality and fast frame rate as well. I've had this issue since the latest update.

Just checked other resolutions in windowed mode, same results.

Did the problem only start with the latest 2 versions?

Also, please share your Mac model and Mac OS version. It is hard to fix this issue unless I can recreate it.

For me it was the latest version for sure... it's been happening for the last week or so (can't remember). I have a Mac Studio running Sonoma 14.0

I got this problem after upgrading to Version 2.5.11, before that everything was ok.

I got this problem after upgrading to Version 2.5.11, before that everything was ok.

What MacOS version are you running?

I got this problem after upgrading to Version 2.5.11, before that everything was ok.

What MacOS version are you running?

I'm currently running Sonoma 14.0. But when there was a previous version of HSTracker, it was also Sonoma 14.0

I played last night without problems. So far nobody provided resolutions or how your display is setup.

Dammit I typed that response but apparently didn't press send. My display is a Studio Display (2560x1440, retina). I'm on Sonoma 14.1, and this started with 2.5.11.

Download version 2.5.10 got same as in 2.5.11 problem, discussed in this issue. v 2.5.9 works fine (just tested it)
version OS Sonoma 14.0 (M1)

Have the same issue

HSTracker 2.5.11
Macbook Pro M2 running Sonoma 14.0

Please try this version and let me know if the problem is fixed.

https://drive.google.com/file/d/1shiu31rCIlKSg0vxMdkI3TSCoTDOm647/view?usp=sharing

Please try this version and let me know if the problem is fixed.

https://drive.google.com/file/d/1shiu31rCIlKSg0vxMdkI3TSCoTDOm647/view?usp=sharing

Unfortunately issue still persists.

Confirmed that HSTracker used is 2.5.12

Also have the same issue since 2-3 versions
on Macbook Pro M2 running Sonoma 14.0

One more version to try:

https://drive.google.com/file/d/1dQDUbI7Y4kaKy0CiT9FviTNAHUMYM6Iy/view?usp=sharing

I found that the new macOS SDK shipped with Xcode 15 changed some behavior, hopefully this will revert the behavior to what is was until I upgrade to Sonoma and can find an alternative. Fingers crossed this solves it.

This worked like a charm

This worked like a charm

Thanks for the quick confirmation. I will make an official version tomorrow.

Official version is now out, please update to it as I am deleting the old test versions.

The problem was solved after the update, thank you very much!