Lookupper 1.3.0 version has a issue?

marcio_ironsmith

this program isn’t working properly after the new update. Previously, when i pressed Ctrl + D in-game (Hitman WoA), it would translate without bringing the game to the menu. However, with the new update, it automatically goes to the menu and doesn’t recognize the subtitles. Is there a way for me to revert to the previous version manually, or will this issue be fixed?
There is the video:

marcio_ironsmith

marcio_ironsmith
video
https://youtu.be/P2IspzIbiAQ

creator

marcio_ironsmith Thanks for the video. I’m already downloading the game and will issue a fix ASAP once I identify the cause of the issue.

marcio_ironsmith

creator It was working in the previous version. Thank you for your attention.

creator

marcio_ironsmith

Could you please confirm if Lookupper works as intended with Hitman WoA when you perform a lookup by hovering over a word, instead of using the lookup without hovering?

It seems like the game goes to the menu when the game window becomes inactive. This happens if the Lookupper window gains focus.

In version 1.3.1, I’ll remove the Lookup window focusing in non-targeted mode to mitigate similar issues with other games.

marcio_ironsmith

creator
Since the game is an FPS, i can't move the mouse cursor to the subtitles even if I want to. However, if i manage to hover the cursor over any text in the game and click, it can still translate without pausing the game.
Here is the video: https://youtu.be/bSE6jbiuk9I

creator

marcio_ironsmith Thank you. The problem is that I can’t run Hitman 3 on my computer, so I can’t suggest a solution yet. But I will definitely find a way.

marcio_ironsmith

@creator
I updated to version 1.3.1, but unfortunately, it doesn't properly capture the words. 🙁
Here is the video: https://youtu.be/Kw9ik9a83gc

creator

marcio_ironsmith It captures words, but the OCR is making mistakes due to the inconsistent background and white text on it. OCR doesn’t handle this well. I have an idea to improve it, and I’ll do my best.

marcio_ironsmith

creator
Actually, when i purchased the Pro version, i was using version 1.2.9, and it was working smoothly. Could it be that something you added or removed in version 1.3.0 is causing the issue? The program is amazing. I hope it gains millions of users in the future.

creator

marcio_ironsmith I rechecked all the commits and I’m pretty sure there are no changes to the OCR engine between versions 1.2.9 and 1.3.1. So, it should detect (and misdetect sometimes) the same as before. I hope to make significant OCR improvements later.