NewHome › Forums › OSSC, OSSC Pro and DExx-vd isl › OSSC – Discussion and support › OSSC for PCBs
384×240 optim mode could be added which would use 4x horizontal multiplier (1536 width) for line4x and line5x.
Fantastic!
Will post data from a Psikyo board next…
Gunbird 2 has a samplerate of 456 which puts it in the difficult 423-532 range so will have to wait for 384×240 optim mode to get it dialed in but OSSC reports 261 lines and 60.14Hz. The dotclk is 57.2727Mhz / 8 = 7.1590875Mhz.
Truxton has samplerate 450 so not possible to use optim mode there either.
270 lines
57.6Hz
7Mhz dotclk (according to https://pineight.com/mw/index.php?title=Dot_clock_rates)
7000000 / ( 270 * 57.6 ) = 450.10288
Is it normal for OSSC to report the number of lines and refresh rate inconsistently? For example trying this again I get 269 lines and 57.78Hz.
Doesn’t Garegga look vertically compressed on my screen?
That is in 384×240 optim mode (thanks @marqs!). It looks normal in Generic mode.
Yes that’s not surprising when using 384×240 mode on a 320×240 game. Remember that optimized mode can only scale by pixel repetition, i.e. integer scaling.
Since it then multiplies by 4x on the horizontal (i.e. vertical for a TATE game), but vertical by 5x, it will look squished compared to both original or square pixel 4:3.
Original: 320*10/11 / 240 = 1.21 (this is what you see in generic mode)
384×240 opt: 320*4 / 240*5 = 1.067, however your screen probably also stretches the 1536 width (height in this case) to 1600 so
1.067* 1600/1536 = 1.11
If your screen would accept 320×240 in 5x mode, aspect would of course be full 4:3
320*5 / 240*5 = 1.33
Exactly these disturbances to aspect ratio is why I don’t personally like optimized modes too much. 🙂
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 |