Posts made by Surface

Will it be possible to output 15khz via the "VGA" D-Sub connector? (While also getting audio via HDMI?)

I just realized I probably misunderstood what you're trying to do. If what you want is to set the video mode (screen resolution) rather than the game resolution on a per-game basis, then yes it does look like there's still no way to do that. The best thing to do for now seems to be to set a video mode that works well with the game resolution you want, and display the game's native resolution (via custom config) within that video mode. For example, I think a 320x224 game fits nicely on a 640 (or any multiple of 320)x240 screen.

You still need to figure out a way to get custom video modes over to your VGA monitor though. If HDMI is not working for you then a hat for VGA output like the Retrotink would be a good solution for you.

@lumbeechief081 I thought we could already set per-system resolution overrides by adding them to the recalbox.conf file. For example for games that have a vertical resolution of 224 or 256 instead of 240 I add:

segacd.videomode=hdmi_cvt 1920 224 60 1 1 0 0
x68000.videomode=hdmi_cvt 1920 256 60 1 1 0 0

which overrides the global 1920x240 custom hdmi video mode.

And then for per-game resolution configs you can go to the retroarch configs folder and add name of rom.cfg with

aspect_ratio_index = "22" (custom, or maybe it's 23 can't remember)
custom_viewport_width = whatever you need
custom_viewport_height = whatever you need

If that guide did not work for you perhaps your VGA monitor is simply not compatible with that custom hdmi mode. It could also be due to the HDMI to VGA adapter you're using. It might also help to put a sync processor in between the adapter and the monitor, such as an Extron RGB interface.

I know this has been asked before in old topics from a year or two ago, but I would like to know if the current Recalbox 6.0 supports the ability to change what button A and button B do on EmulationStation/The Recalbox OS only (without affecting input mappings on Retroarch cores).

Across multiple systems, the right-most button (A in Nintendo systems, C in Sega systems, O in Sony Japanese systems, etc.) works to "accept," while the bottom button (B in Nintendo, B in Sega, X in Sony Japanese) works to "cancel/return." Therefore, the current ES/Recalbox accept/cancel scheme goes against a strong habit (except for users mostly used to the non-Japanese Sony scheme). Currently, other frontends like RetroPie and Lakka/Retroarch default to the rightmost button as the accept button.

My current workaround has involved swapping A and B on the controller configuration setting of ES, but then I am forced to swap accept/cancel on Retroarch cores and use overrides, and to change the remap settings for each core and save remap configs for each. This is okay now that I'm only using a few systems/cores, but as I add more this will become a troublesome workaround.

If there is no way to make this configuration setting, I suggest adding it as an optional configuration on the next Recalbox release. Thanks for your time and input.

@lumbeechief081 said in How to change resolution per-game?:

@greenalex I'm using a VGA CRT monitor therefore 15khz isn't possible.. Even though "Switchres" is present in Retroarch on both RecalBox/RetroPie it would be cool if it actually worked on a Raspberry Pi through an HDMI to VGA adapter.

The switchres setting does have a 31khz option that you could try. I'm using a 15khz monitor and the switchres 15khz setting (and 1920 as the super resolution) already seems to be working on the current Recalbox via HDMI to VGA adapter (and then combining HV sync to S for the monitor), after setting up config.txt as detailed here: https://github.com/recalbox/recalbox-os/wiki/Connect-your-recalbox-to-a-CRT-with-HDMI-(EN)

It looks to be working since loading different games/systems with different resolutions and refresh rates results in smooth scrolling (as long as the game's vertical resolution does not exceed 240 by too much), and the OSD notification does show different refresh rates being set. I've only been testing this for a couple of days though. Is it really not supposed to be working yet?

It also seemed to work the same way using Lakka, but that whole frontend seemed less stable than Recalbox using the above configuration.