-
Notifications
You must be signed in to change notification settings - Fork 795
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
[Feature Request]: Selectable Resolution at original XBox Port #7185
Comments
We don't have a way to detect if the system is able to run 1280x720, is there a way you know to check this? 0 should of cause be filtered out, are you able to see where it is coming from? |
Since every xbox is capable of 480 i/p , 720p and 1080i, is it needed to be filtered? 480p and 720p should be a safe option. (since 480p is the default) i assume the option 0 is a return message of avaible resolutions? maybe an SDL-Test fails. |
Not every connection or TV is able to display more then 480p, or is there some scaling magic that will then down scale the upscaled image? |
The original XBox knows two states: PAL or NTSC. At NTSC and combined with component-cables (YPbPr) you can get 480p, 720p or 1080i .. at every other standard-connection (Composite, S-Video, RGB over SCART/JP-21) you only reach 480i .. so if you can use 480p you should also can use 720p. Since it is only an entry in the config every xbox is theoretical capable. Only a few crt can work with 480p, so it is a safe bet. I didn't tried if DevilutionX can run at 480i, since my beamer can't use this at component/hdmi. |
maybe an check if 720p is valid like lithiumX can be implemented, since it depends also on nxdk: |
Feature Type
Quality of Life
Describe
At the actual release (1.5.2) the ini modification to 1280x720 works flawless, just kinda slow. Gives the feeling nearly 30 years ago on an old PC. (9ish FPS)
The ingame menu gives as resolution option 480 and 0. so it is not directly selectable, also 0 just gives an empty image if restarted with this selection.
The text was updated successfully, but these errors were encountered: