I’ll quickly describe how RetroArch handles overlays, Retroarch handles overlays, as much as using it. Moreover, if the emulator changes its display system or changes its system of options, RocketLauncher will not succeed, it also seems to me that RocketLauncher is dependent on “AutoIt” The simplest is to have a FrontEnd ( LaunchBox, HyperSpin, EmulationStation …) that directly launch your emulator (Retrorarch, Mame, Fba, Fba-Neo …) Why ? because the configuration is already not very simple, if in addition you add an extra layer, you will quickly get lost and especially spend a lot of time. My opinion, which can be questionable, is to avoid going through this kind of program. Here’s what it can do with and without overlays :Īlmost all emulators have a system of overlays, and when the emulator does not have it is possible to go through external program like RocketLauncher. The screens, at the time, were in a 4/3 format (rather square), now most screens are in 16/9 (rectangular), which leaves a blank space on the sides of the game. Overlays allow to add visual effects to an emulated game, it allows to simulate CRT screens or to add on the sides of the game an image that can be related to the console type, or in relation to the game itself. Today, I’m going to give you my feedback about the overlays in RetroArch.
0 kommentar(er)
