-
Notifications
You must be signed in to change notification settings - Fork 13
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
Option for the menu to be in 240p #82
Comments
This could also close issue #59 where the deinterlacer destabilise the picture. |
Not quite the same, I'm using motion adaptive deinterlacing on a NTSC system (clock mod also enabled on the n64digital) so the stabilization is not an issue, it more that 240p seems to scale better at least to my eye. |
Yes, but I'm saying that changing to 240p could solve issue #59. Not that it is the same issue. |
Got it, yes that would solve it. |
While I appreciate more options myself, redoing whole menu to operate at 240p or giving user an option to choose between 240p/480i is not something that could be done easily with current components and the way element positioning is implemented now. If you're using any upscaler or HDMI mod I strongly recommend setting deinterlacing on those devices to I'm going to leave this issue open, it would be nice to have an option but it's not a priority now. |
A lot of us CRT users really don't like 480i either, it's very flickery looking at the edges especially on big sharp CRT's and the N64 not applying any vertical filtering to try hide this. Glad it's not dismissed completely, even if the 240p option becomes a basic looking menu, that'd still be great and preferable. |
+1, on OSSC interlacing looks really bad and causes image retention on IPS displays |
Description
To my eye using the the N64Digital scaling to 1080p, the 240p everdrive menu is a lot more clear than the 480i menu present here.
How to solve the problem
If there was an option to set the resolution to 240p in the config that would really help and allow others to keep the 480i if they want.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: