![]() ![]() ![]() The printing of the available area, which I think you removed from the debug output window, would help a lot: what if the algorithm does not "see" sufficient elbowroom? That said - I do see the lack of aspect correction in the windowed modes - so this is something I can atleast work backward and bisect (and I suspect the issue is on our side).īeware that pixel-perfect may not always be able to correct the aspect ratio. Why? Neither of them looks like a standard display unfortunately not able to reproduce it. The size of the full-screen screenshot is 1546x927 and of the windowed one-1289x879. Can you please look into that while I re-test switching between windowed and full-screen modes at my friend's? Shall I provide magnified fragments of your screenshots that you may see the problem clearer? On the second-it should consist of 2x2 pixel blocks, but it does not. On the first one, the image should consist of 4x3 pixel blocks, but it does not. Notice, Doom does not look pixel-perfect on neither of you screen-shots. Did you intentionally remove it? Just the other day it helped me find a problem with the handling of high-DPI awareness on high-DPI decies: it saw virtual pixels rather than physcial ones. I do not see the a report of the available area in the log-an important indicator of what area pixel-perfect mode thinks is available for magnfication. I will try again at my friend's and, if the error occurs, will give you all the details: version and config. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |