To the GameCube and Wii, 240p isn't really anything special, since they just run in double-strike. On typical analog crt televisions, there is no 480p or even 240p, they run exclusively in 480i, period. So to get a 240p image in such an environment all pre-GameCube consoles double up on the vertical axis, sacrificing resolution for progressive output. Before Dolphin supported double-strike properly, you could literally see this in virtual console games. (unless you set the emulated wii to progressive mode, then it wouldn't try to use double-strike at all)
![[Image: panningzelda_thumb.png]](https://dolphin-emu.org/m/user/blog/hybridxfb/panningzelda_thumb.png)
In a progressive output that image looks stretched vertically, but to an interlaced signal that image above has 240 progressive lines. Then the XFB can cut out the black bits to the right of the rendered frame and tada, 240p! This does require XFB shenanigans since the GameCube and Wii rendrDouble-strike is a very simple technique and classic technique, so there is nothing special or weird here - this is basically identical to how the NES, SNES, and N64 work internally, just now performed by XFB. Also that's why the GameCube and Wii do not have a 240p output mode per se, since it's still 480i. Almost all virtual console games run in double-strike, since that's the best way to render classic games on analog tvs. Of course if using component, the Wii is set to 480p output, and XFB knows not to use double strike and scales on both axis evenly.
Dolphin of course only emulates some facets of the Wii's output, but thanks to emulated XFB improvements Dolphin no longer needs to tell the emulated wii that it is or isn't progressive output - Dolphin's emulated XFB can adjust things as needed without the user messing with it at all!
Anyway, here are a few times where we have talked about it on the blog!
https://dolphin-emu.org/blog/2016/02/02/dolphin-progress-report-january-2016/#40-8640-better-video-mode-detection-by-phire
https://dolphin-emu.org/blog/2017/11/19/hybridxfb/#panning
https://pt.dolphin-emu.org/blog/2015/10/01/dolphin-progress-report-september-2015/#40-7517-derive-field-timings-from-video-interface-registers-by-booto
Of course it is possible to output 240p output via component, as swiss shows, but why would you when double strike is available? Also I don't know what level of hackery swiss is committing to make it do that. I imagine quite a lot, since the consoles aren't designed for that at all!
Yea um, no. Interlacing was a bandwidth hack - basically compression, in an analog fashion. Analog CRTs were technically capable of 480p easily, as they have 480 lines of phospors, they just needed different timings. As evidenced by broadcast video monitors, crt computer monitors, component crt tvs of the 2000s, and mod forums adding circuitry to old televisions, etc etc. But typical analog televisions weren't able to switch modes since they were... well, really, REALLY dumb. They just operated on pre-set timings literally hard-wired into the devices.
In a progressive output that image looks stretched vertically, but to an interlaced signal that image above has 240 progressive lines. Then the XFB can cut out the black bits to the right of the rendered frame and tada, 240p! This does require XFB shenanigans since the GameCube and Wii rendrDouble-strike is a very simple technique and classic technique, so there is nothing special or weird here - this is basically identical to how the NES, SNES, and N64 work internally, just now performed by XFB. Also that's why the GameCube and Wii do not have a 240p output mode per se, since it's still 480i. Almost all virtual console games run in double-strike, since that's the best way to render classic games on analog tvs. Of course if using component, the Wii is set to 480p output, and XFB knows not to use double strike and scales on both axis evenly.
Dolphin of course only emulates some facets of the Wii's output, but thanks to emulated XFB improvements Dolphin no longer needs to tell the emulated wii that it is or isn't progressive output - Dolphin's emulated XFB can adjust things as needed without the user messing with it at all!
Anyway, here are a few times where we have talked about it on the blog!
https://dolphin-emu.org/blog/2016/02/02/dolphin-progress-report-january-2016/#40-8640-better-video-mode-detection-by-phire
https://dolphin-emu.org/blog/2017/11/19/hybridxfb/#panning
https://pt.dolphin-emu.org/blog/2015/10/01/dolphin-progress-report-september-2015/#40-7517-derive-field-timings-from-video-interface-registers-by-booto
Of course it is possible to output 240p output via component, as swiss shows, but why would you when double strike is available? Also I don't know what level of hackery swiss is committing to make it do that. I imagine quite a lot, since the consoles aren't designed for that at all!
DrHouse64 Wrote:The thing is, interlacing was a clever trick to double output resolution, but nowadays causes more harsh than good.
Yea um, no. Interlacing was a bandwidth hack - basically compression, in an analog fashion. Analog CRTs were technically capable of 480p easily, as they have 480 lines of phospors, they just needed different timings. As evidenced by broadcast video monitors, crt computer monitors, component crt tvs of the 2000s, and mod forums adding circuitry to old televisions, etc etc. But typical analog televisions weren't able to switch modes since they were... well, really, REALLY dumb. They just operated on pre-set timings literally hard-wired into the devices.
![[Image: RPvlSEt.png]](https://i.imgur.com/RPvlSEt.png)
AMD Threadripper Pro 5975WX PBO+200 | Asrock WRX80 Creator | NVIDIA GeForce RTX 4090 FE | 64GB DDR4-3600 Octo-Channel | Windows 11 22H2 | (details)
MacBook Pro 14in | M1 Max (32 GPU Cores) | 64GB LPDDR5 6400 | macOS 12