[HDL]

I see. I went and tried it anyway but as you figured, it didn’t work. So I suppose outputting the pure native resolution of old consoles is just not possible here? That’s rather disappointing. Seems like 696×480 is the next best thing (to maintain integers).

[HDL]

Switching that changes the output from 720×240 to 1440×240.

[HDL]

I’ve not tried it with a 480p source. I’m not able to test it at the moment, but if I get the chance and encounter different results I’ll post.

[HDL]

I tried this with both 0.76 and 0.77. The test pattern appears fine, but as soon as I turn the console on it’s just a black screen.

I’ve since bought a Magewell capture which displays the OSSC signal fine, but if someone has an answer to this problem please post it.

[HDL]

Yes I had figured out what to change. Posted details as well as my tweak values here: https://videogameperfection.com/forums/topic/tips-tweaks-lx3-lx4-lx5-modes/page/4/#post-11885

It’s not perfect, though. I can’t get a sample phase value the eliminates all of the blur (comes about 99% of the way) and I can’t get perfect alignment of the overscan area (it always overshoots or undershoots by a small amount). Perhaps in the future there can be a mode that presets the ideal values for this so others don’t have to go through all the same tweaking.

[HDL]

Yeah it’s for optimized mode. I am testing with games that output 320×224 as well as the 240p Test Suite using the 320×224 grid. Adjusting the sample phase I can get very close but no cigar. At a quick glance it looks perfectly clear, but upon scrutinizing it there is always a slight amount of blur on one side. Low degree values give a very slight blur on the left and high ones on the right. This is a matte display, by the way.

For normal gameplay it looks perfect, however I plan to record with this setup eventually and would rather eliminate all traces of blurring if possible.

Here are my values, in case they help anyone:

Sample phase 112
H.samplerate 427
H.synclen 38
H.active 348
V.active 240
H.backporch 33
V.backporch 18
Line x5 using 1920×1200 mode.

Edit: Actually upon checking the linearity test it seems 1920×1200 stretches the image to non-square pixels. 1920×1080 keeps them square but won’t display the entire image using line x5.

[HDL]

Just updated my firmware and am trying line x5. I can get an almost perfect picture if I set the mode to 1920×1200 (although my display is 1920×1080). I have H.active set to 348 (native Genesis width plus the overscan area) and this appears correctly on my screen, but I can’t find the H.samplerate sweet spot at all. I can’t make heads or tails of those spreadsheets and I don’t otherwise know how to calculate what these values should be. My monitor is an AOC G2460PF.

[HDL]

A little late on this, but here’s what I mean about the overscan.

Here are the settings I changed:

240p_L3M2
H.samplerate 427
H.backporch 55

Those settings produce this:

This is how it should look:

There should be a total width of 348 (28 additional pixels on top of the game’s 320 pixel width). I want this to show up on the OSSC, but if I change H.active to 348 it borks the aspect ratio.

[HDL]

Is it also possible to do native aspect pass-thru? As in, can I output a 320×224 signal (Genesis) or a multiple of it?

[HDL]

Awesome update, thanks for your work.

[HDL]

Did a little research and yeah, the Wii definitely uses traditional anamorphic widescreen rather than true 16:9.

Line double doesn’t make it less blurry. The pixels get distorted either way, so I just set it back to 4:3.

[HDL]

I’m using NTSC Genesis. I played with the H.samplerate on 240p_L3M2 and it seems 427 does the trick. However it seems like 320×240 optimized mode cuts off part of the overscan on the right side. Any way to prevent that?

Edit: Seems like the H.active option is meant to address this, but I’m seeing discrepancies between the 240p test suite and actual gameplay with Generic 4:3 mode. In Generic 4:3 the full overscan in shown on the right, but in 320×240 optimized it will still get cut off even if I adjust the H.active value to make the overscan appear in the 240 test suite overscan test. You can also see this in the grid test by turning on the gray background.

[HDL]

It’s basically the “no scale” mode on my monitor, so it displays the exact resolution output by the OSSC. This is the only mode that results in bad frame rate, so I’m wondering if there are relevant settings on the OSSC that affect it.

[Author]

Posts