Changelog for v1.0.7b
- fixed a bug where the app ignores the disabled visualize scanned area.
- fixed a bug which caused losses to be ignored when the user maximized the Hearthstone window
- introduced a new feature to automatically detect Hearthstone resolution on Windows which allows non-standard resolution to be scanned regardless of the resolution being listed in HearthTracker or not.
Details of the update:
During the development of HearthTracker, I have noticed Hearthstone client doesn't even have fixed resolutions, whilst the client is able to handle it dynamically. This seems like really important because it seems like the client will scale the images/UI accordingly, by doing so HearthTracker will most probably miss a few things when it tries to scan on non-standard resolutions in windowed mode. With users feedback, this has confirmed my doubts about that.
Therefore, I dive into my code again, make the app detects the resolution and coordinates of the working area better (properly excluding the borders and title bar). The app will now prioritize the auto game resolution detection over the selected game resolution on preferences. It will also scale the target images & coordinates accordingly in order to "see" better.
It is highly recommended that you enable the auto game resolution detection while in the same time, unless you're using border-less window mode or experiencing issues with the new feature. In the same time, please select the nearest match for the resolution as well so that HearthTracker can fallback into default option when auto detection fails.
Finally, with auto game resolution detection, you should be able to run Hearthstone with any resolution regardless it is being listed in the app preferences or not.
P/S: auto game resolution detection can only work on Windows at this moment, this could change in the future.
No comments:
Post a Comment