Am 21.04.2026 um 07:34 schrieb meow via Wine-Devel <wine-devel@list.winehq.org>:
And so there is one game on steam that creates a cursor of 384x384 in 1440p and that ends up blowing up and turning into a visual mess. Of course, that cursor is not 384x384, it just creates a buffer of 384x384 because the game for some reason does like 4x internal scaling or something (96dpi x 4 I assume).
Did you check what Windows does in this case? As you say, cropping the cursor gives identical results to what you see on Windows, so maybe it is actually the right thing to do. It is also possible that Windows returns an error and the application responds to that by creating a smaller image. The third option is that some information returned to the application is incorrect, causing the application to behave in an unintended way. If it is an old program, it is likely that it queries the DPI, but doesn't treat the result correctly and breaks if dpi != 96. In this case you might be able to reproduce a similar issue on Windows when you disable OS-Side scaling (i.e. set compatibility option scaling performed by application)