-
Notifications
You must be signed in to change notification settings - Fork 99
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
On Windows, buffers larger than the window cause weird artifacts and look horrible #221
Comments
Exactly how do you send this larger than window buffer to minifb? |
@emoon by using It's exactly the same as sending a buffer that's the same size as the window, or smaller than the window. |
ok, I will have to investigate it. You can workaround the issue by scaling it manual (which you may or may not want to do anyway if you want super-sampled downscaling) minifb on will only scale with nearest filtering. |
And you can also make it better by adding a function for me to query DPI scaling (since I only multiply the resolution by 2 to support high DPI on macOS, but then it causes bug on windows -_-) |
temporary you can always check if you are running on macOS or Windows. |
🤮 🤮 🤮 🤮 🤮 🤮 🤮 🤮 🤮 🤮 🤮 🤮 🤮 🤮 🤮 🤮 🤮 🤮 🤮 🤮 |
Hey, I wrote temporary above. |
I'd rather wait for a fix is what I mean lol |
Also, if you are in such hurry you can add it yourself. |
Sorry, I did not mean to imply that I was in any sort of hurry, but you're not being very helpful by telling me to go do it myself. Like I said, I'm more than happy to wait for a fix, apologies if anything I said came off the wrong way |
I said if you want super-sampled down scaling (i.e anti-aliasing) you would have to do yourself (as minifb doesn't support it) regular scaling should work, but I don't think I have tested with buffer larger than the window. |
I can try to get |
Oh, you're misunderstanding me then. I'm taking advantage of the extra pixels on macOS, not trying to do antialiasing (I already have that). However somehow that causes minifb on Windows to flip out when the display doesn't have those extra pixels. Apparently an entire Discord chat just agreed that the vomiting faces were exactly equivalent to "FUCK YOU WTF I NEED THIS FIXED RIGHT THIS MINUTE", so I'm sorry if it came off that way (that's really, really not what I meant). I was replying to the "check if the OS is macOS" hack specifically |
Fair enough, yeah that is how I pretty much interpret it as well. Understood. I will get the scaling value return added soonish. |
won't get around to implement it this weekend |
Any progress on that |
Sorry, not yet |
Just FYI I have started to work on this but it's quite a lot of work. |
Being tracked in #236 |
At least on Windows, displaying a buffer larger than the size of the window causes weird artifacts.
My ray tracer is a good example of this, and is how the bug was discovered.
At 1x resolution:
At 2x resolution:
My friends with real Windows machines originally reported this bug to me, then I confirmed that it also happens in Wine, so I think the problem is minifb.
The text was updated successfully, but these errors were encountered: