![]() Then, what you need to do is use the custom aspect ratio. However it is possible to do various things with custom modelines and the scaling options of RA.įor example you can have two different super resolution modelines, one for NTSC (240p), and one for PAL (288p). Working with cropping makes sense on a hi-res LCD where you use (integer) scaling, on a CRT it’s usually not supposed to be that way. It has borders on the left and right and top and bottom. A real C64 does not fill a CRT screen, certainly not with the PAL resolution (384x272") that’s requested by default. I think you are getting hung up on the term “native resolution” and because you want to do stuff that actually doesn’t occur on the real hardware. Is this the way to go or where can I get this knowledge from someone, who actually uses RetroArch for more than one emulator? And on top of that you need to take care of per core crop settings. ![]() Then tweaking it on CRT further, so it will get associated with that modeline inside CRT monitor firmware. The only thing I could think of is adding custom resolution for all these modelines. All these cores I need to setup and fix manually and even so, the result is still mediocre.īecause all the cropped core resolutions will in the end use 320x200 or 320x240 and will not directly output native resolution, when tweaking “knobs” on CRT monitor, it will remember them for these resolutions. In General Settings of RetroArch I already have crop enabled and aspect ratio: core provided. Where is documentation about this? Documentation about core setup for native CRT resolution? This should be on your RetroArch Wiki. : Requested Resolution: it will switch to 320x240 with 20px border at the top and 20px border at the bottom (there is still some border on left and right, so the crop is not the best it could be). If in core menu you choose core crop: automatic, then it will request this: : Requested Resolution: resolution is outside of 320x240, so it will choose the closest 640x480 and it is very very ugly. Tvs also can have service menus where V-Size can be increased, I would expect a PVM to have something similar, maybe an actual knob. This will of course move you away from NTSC spec, and more in a custom direction. You would have to try and lower that, to see if the image get’s bigger. You see that both of your modelines end with 261 total lines. ![]() You have some flexibility in the horizontal direction with the way modelines can be set up so borders can be made less visible, but that won’t work that good in the vertical direction. The picture your PVM displays is what I would expect.Ĭropping borders can be convient for emulation, it’s more something for LCDs though. Borders were supposed to be part of the image, sometimes developers could also do effects in that area which is why any emulator worth it’s salt will include them. It’s unlikely to find one that’s by default set up to only display 192 lines though. Overscan on earlier TV’s (like 80’s) was bigger. ![]() So it cannot natively display 256x192 resolution right? What TV would natively display ZX Spectrum resolution through RGB (RGBHV) or YBGRB cable? Sony PVM is probably natively 240p or 640i. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |