352×240 timing mode, timing auto switch
- This topic has 0 replies, 1 voice, and was last updated November 11, 2017 at 6:38 AM by .
Viewing 1 post (of 1 total)
Viewing 1 post (of 1 total)
- You must be logged in to reply to this topic.
NewHome › Forums › OSSC, OSSC Pro and DExx-vd isl › OSSC – Feature Requests › 352×240 timing mode, timing auto switch
Hi,
I use the OSSC mainly with my Saturn, and games often switch resolutions. For example, Thunder Force V uses 704×480 in the title screen and options, then 352×240 ingame, while the bootup sequence uses 320×240.
In 352×240 mode, when using Line2x in HDMI, I get a lot of aliasing visible mostly on mesh patterns (checkerboard effect). This seems to be because in generic 4:3 mode the resolution is not correctly sampled for this resolution. If I switch OSSC from Generic 4:3 to 320×240 mode, then play with the advanced timing, I can get a pixel perfect output for 352x and 704x modes (from memory, H samplerate was around 454 for 352x mode, 908 for 704x mode).
But of course then this mode will not work fine with 320×240, on the bootup of the console. There are only two such timing presets, 320×240 and 256×240. For the Saturn, a third is needed, 352×240. Playstation may need a fourth, 368px (I think Capcom 2d fighters may have used this).
To alleviate this, would it be possible for the OSSC to recognize these modes and switch to the appropriate modes automatically?
If this is possible, would it be also possible for the system to have automatic presets for any different recognized timing mode? Then I could set up pixel perfect output for all different resolutions the Saturn can output, of which there are plenty (around 24x 15KHz modes in total).
Cookie | Duration | Description |
---|---|---|
_gat | 1 minute | This cookie is installed by Google Universal Analytics to restrain request rate and thus limit the collection of data on high traffic sites. |
Cookie | Duration | Description |
---|---|---|
__gads | 1 year 24 days | The __gads cookie, set by Google, is stored under DoubleClick domain and tracks the number of times users see an advert, measures the success of the campaign and calculates its revenue. This cookie can only be read from the domain they are set on and will not track any data while browsing through other sites. |
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
Cookie | Duration | Description |
---|---|---|
IDE | 1 year 24 days | Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile. |
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
Cookie | Duration | Description |
---|---|---|
ct_checked_emails | session | No description |
ct_has_scrolled | session | No description |
ct_mouse_moved | session | No description |
ct_screen_info | session | No description |
wordpress_apbct_antibot | session | No description |
wp_woocommerce_session_9cc3598a6315be16da4f85bb374cf6a5 | 2 days | No description |