The script I created would then see what’s your current screen resolution, then start the 1080p config file if 1920x1080 is the selected screen resolution via the batch-file. I tried creating different batch-files for various screen-resolution (1080p, 1440p and 2160p), having the batch-files pointing to the RetroArch.exe file and using the command line argument -config to select a different config-file based on how many times I want to scale the image’s width- and height of the libretro core (based on the chosen screen resolution). There I can launch any rom on a big list, and it’s configured with the right commands to successfully launch the right core from RetroArch and then inject the rom from the list to RetroArch itself. The issue now is to combine all this with the way I usually run RetroArch, through Kodi via a now deprecated plugin called Advanced Launcher. The if statements checks for your current screen-resolution, and starts the selected batch file or exe file based on your screen resolution. My script written in CodeBlocks seems good enough now to run different parameters based on separate if statements. Maybe there is an automated solution for this, but I haven’t found it yet, so I would need some guidance regarding this issue. Since my RetroArch setup is configured to display 5x the native resolution to fit the Border Overlays (I have an overlay scale of 1.25), to my limited knowledge there is no way to automatically turn the Custom Aspect Ratio Width- and Height from 5x to 10x when RetroArch detects that I’m now have switched screen resolution from 1080p to 2160p and vice versa.
![retroarch disable borders retroarch disable borders](https://i.ytimg.com/vi/x1OEs31qF6M/maxresdefault.jpg)
This is all well and good on both of my 1080p screens, but sooner or later I’m going to migrate to a 4K TV, and than this setup becomes a bit more troublesome. I personally don’t like to enlarge the image too much on those older handhelds because the pixels then becomes way too big, Border Overlays can help by making a smaller image both stylish and seamless in my opinion. On the Gameboy Color I have a purple Gameboy Color Border Overlay surrounding the actual image (I use Integer Scale, Custom Aspect Ratio and a screen size that is 5x the native resolution, 800x720). So unless its something obvious to everyone, its often not until a full release with tens of thousands of people banging at it that issues can arise, with a staff of three, more people testing betas would be hugely helpful.One feature that I have become very fond of, is having Border Overlays while emulating old handhelds that have a relative low native pixel resolution. Sounds like maybe its applying a default for any system/core associated with retroarch maybe, maybe that should be another checkbox in the associated platform page, if a default bezel is required And about it seeming beta, well we do put out a lot of betas, but unfortunately few users use them, and fewer still ever bother to report issues. Because it would definitely take forever with all the systems I have.
![retroarch disable borders retroarch disable borders](https://i.ytimg.com/vi/fY4O8ZejmMM/maxresdefault.jpg)
![retroarch disable borders retroarch disable borders](https://snesclassicmods.com/wp-content/uploads/2018/01/Custom-Border-for-SNES-Classic-Mini.png)
Will add system bezels manually to every single console later maybe. Anyways, I simply just deleted them all and installed only the theme bezels. I don't quite understand why some type of code wasn't just put in to make it avoid doing this to systems like psp/ps2/wii etc. It would of been nice if there was a warning that doing recommended default would do this. Following the instructions gave by the update made it place the bezels over ALL wide screen consoles on Retroarch.