Hello again,
When i open some images in full screen using any high quality zoom settings other than "none" or "bilinear", the image looks pixelated, as if i was looking at the up-scaled thumbnail of the image, until I scroll to another image and back to it, it is then when i view it correctly.
It doesn't happen with all images, i attached one example in which it occurs consistently. I am currently using windows 10 ver 1.6.4, though in a previous version (1.5.1) it always happened to all firsts images.
I took an screenshot of the full screen view of the image, so you could see what it looks like:
I'm experiencing this as well and wanted to add some observations in hopes it helps debugging this:
Seeing two variants of this. I feel like they're related, but not quite like what the opening poster is seeing?
With Fullscreen Auto Zoom setting on "Fit image to window" (cannot reproduce with other "Fit image to window, X only" variants), it seems like a dice roll (race condition perhaps?) if the image is displayed as it should or pixelated. Not like OP but screen filling with a seemingly lower res version scaled nearest neighbor.
This one only seems to happen when the image resolution results in 100% zoom in fullscreen. I believe that would mean height to match display height in pixels.
I can confirm this behavior only happening with high quality zoom enabled. Specifically, the Zoom Out one with anything but "Nearest" or "Bilinear".
It seems like the chance for this one goes up if the image takes longer to load. BMP or sizable PNG from a spinning disk can trigger this fairly often, but it's more of guesswork and might be unrelated.
Showing info text in fullscreen reveals that the zoom level stays at 100%. Changing zoom level without exiting can fix the view (but need to change from 100% since it's already at that).
During startup and when switching out of fullscreen or quitting, I can see the a smaller window for a split second. Perhaps the image is rendered according to that size and not refreshed when fullscreen is initialized?
With Fullscreen Auto Zoom setting on "No fit", I get something similar to OP, except the image is tiny (42x32 with provided example). In that case the example image does work for me to reproduce the issue. Actually, from what I can tell it happens on all images here.
In this case it appears to not matter if high quality zoom is enabled, at least on my machine. Odd.
Setting the View (not Fullscreen) Auto Zoom setting to "No fit" seems to resolve that variant of the issue.
Showing info text in fullscreen reveals that the zoom level is very low. For the example image it's 5% in my case. For other images it may go down to 1%. Changing zoom level without exiting can fix the view (can just press shortcut to get 100% zoom in this case).
I'm on Windows 10, with a primary display resolution of 1920x1080 (so I see the first variant with 1080 height images). Startup setting is set to "Viewer - Fullsceen". 100% DPI, no font scaling. XNView MP 1.7.0, though I also saw this in previous versions.
Not sure when exactly it started happening, however. Admittedly I skipped updating for a while before it cropped up.
Also not sure if I should even mention it since it makes me sound insane, but while writing this up, going back and forth with settings, I accidentally tried opening an unsupported file and it made the issue go away temporarily. Switching settings around can make it trigger again. No clue how these are connected if at all, but I can repeat this a few times and it works for some reason...
I hope this helps in some way. Maybe there's more to this but these are the combinations of settings I could observe on my end.
It is still happening in version 1.8.0 and with a completely different PC. Only the CPU brand is the same.
And @blubbeh made the perfect description of the bug.
faltonico wrote: Wed Sep 25, 2024 11:11 pm
It is still happening in version 1.8.0 and with a completely different PC. Only the CPU brand is the same.
And @blubbeh made the perfect description of the bug.
Do you use 'View>Misc>Two pass rendering'? Please send your xnview.ini, and the way to reproduce?
faltonico wrote: Wed Sep 25, 2024 11:11 pm
It is still happening in version 1.8.0 and with a completely different PC. Only the CPU brand is the same.
And @blubbeh made the perfect description of the bug.
Do you use 'View>Misc>Two pass rendering'? Please send your xnview.ini, and the way to reproduce?
Now that i tried to reproduce the issue with and without the thing you asked me to, I could not, either way... even with the images that consistently showed that way. NOW It is working correctly with any type of resampling.
And Two pass rendering was ON by default.
The only thing i did "new" that i remember from the last post to today was to update windows 10 and my AMD RX 7900 XTX GPU driver.
