-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OCR Doesn't grab complete grid when Game Resolution and Monitor Resolution don't match #256
Comments
Could you attach snapshot generated by autosolver? |
w11 It seems to work on smaller ones, but at 7x7 it just loses that left most column and fails |
I think that the default layout of the fragments is affected by the modded buffer. Could you verify if this is case? At the moment, the layout is not configurable, but I could add this to the settings. |
If you don't mind building autosolver form source, you can fix it yourself now by changing this line: https://github.com/marcincichocki/breach-protocol-autosolver/blob/v2.11.0/src/core/ocr/fragments/grid-fragment.ts#L25 The first argument determines distance in percentage from left border (without black bars) to the start of the grid fragment. If you decrease it, it should make grid fragment bigger, thus solving your issue. |
I currently run CP2077 @ 1920x1080, but it's upscaled to my monitor size of 3440x1440. When I use the current version of the breach protocol, it doesn't seem to capture the whole grid of options properly. I think it's looking at the game resolution when the game is in focus, instead of the monitor resolution.. Not sure how to fix this, since I don't think the older version (1.5) had this issue with the mismatched resolutions
NOTE: It seems that in the older version of CP2077, the monitor was handing the upscaling to full screen. But, now it appears it's being done by the driver. So, the issue might not be the software, but a change in the drivers. I'll have to investigate more on my end when I get a chance.
OS; WIndows 10
Platform: Native via GOG, version 1.5
BPA: 2.3.0
The text was updated successfully, but these errors were encountered: