HFS Play

Configuration Overrides

aka (per-core / per-game configs)

This was just added yesterday. It's an alternative but not a replacement to core specific configs.

Core specific configs allow cores to have their own configuration file (paths, controls, shaders, etc.). It works rather well but managing all those configurations is somewhat problematic.

The new alternative is automatic and currently always enabled. It leverages the append config functionality that was usable only from the CLI. Basically what it does is it will look for a per-core config (that can be as slim or as complete as the user wants) and load it overriding the globals when content is loaded. The same applies for games, it will look for a config file named after the game and load it overriding the globals and even the core overrides.

It will look for the configurations in rgui_config_directory if defined and it will fall back to the location of your main configuration file.

Core override example:

config_directory/nestopia/nestopia.cfg


videoshader = "shaders\royalenes.cgp"
video_aspect_ratio = "-1.000000"
aspect_ratio_index = "21"
core_options_path = "nes-options.cfg"
input_libretro_device_p1 = "1"
input_libretro_device_p2 = "1"
input_libretro_device_p3 = "1"
input_libretro_device_p4 = "1"
input_libretro_device_p5 = "1"
input_libretro_device_p6 = "1"
input_libretro_device_p7 = "1"
input_libretro_device_p8 = "1"

To make this override load store it in your config dir, in a subdirectory called nestopia

This feature leverages append config so it has the same limitations:

Overrides will propagate to the main config if configuration auto save is enabled (config_save_on_exit) Actually now configs won't be saved when overrides are loaded, it's impractical but it's better than a tainted config
Configuration changes done before loading a game won't be effective

Hello, hope someone could help me, I'm really struggling with the override stuff.

1.Fresh install of RA, with only one core (gambatte) and 1 playlist (Game Boy only, not color). I didn't modify any directory or anything else. Configuration per core is OFF, Override is ON.
2.I didn't modify the retroarch.cfg file. The path ofr rgui stuff is: rgui_config_directory = ":\config"
3.I just created a folder: D:\Retroarch\RetroArch\config\Gambatte with a Gambatte.cfg file in it.

My goal is to use Gambatte for Game Boy color AND Game Boy games. I want to use specific shaders for those 2 kind of systems/games.
I edited my Gambatte.cfg file and add this line: video_shader = "shaders\shaders_cg\handheld\gameboy\gb-shader.cgp" to use theGB shader. (Inspired by what I found there: http://blog.andressm.org/new-retroarch-features-2/" onclick="window.open(this.href);return false;)

When I launch a GB game, nothing happen. No shaders loaded. I'm pretty sure that I'm really close to find the answer, but I think I need your help!

kikikirissx a écrit :tu n'as rien a faire il se debrouille tout seul
si tu as Nintendo Game Boy Color.cfg il ira chercher avec la config gbcolor dans le dossier "config" et il faut mettre aussi un fichier de shader correspondant dans le dossier "shader".

Mydriaze a écrit :Merci, mais mon probleme ne vient pas des touches de configuration!

X:\HFSBoxSP\RocketLauncher\Modules\RetroArch\RetroArch.ini
[Settings]
ConfigFolder=..\Emulators\RetroArch\configs
ConfigurationPerCore=true
Fullscreen=false
[SNK Neo Geo Pocket]
AspectRatioIndex=19
VideoShader=..\Emulators\RetroArch\shaders\shaders_cg\handheld\lcd_cgwg\lcd-cgwg.cgp
[SNK Neo Geo Pocket Color]
AspectRatioIndex=19
VideoShader=..\Emulators\RetroArch\shaders\shaders_cg\handheld\lcd_cgwg\lcd-cgwg.cgp

Mydriaze a écrit :Je te remercie, je vois ou tu veux en venir, mais on parle de RocketLauncher dans ce cas et des fichiers AHK je crois... La je suis sous RA version stand alone. Je vais jeter un coup d'oeil ce soir, car je n'ai pas les fichiers sous la main. Si j'ai bien compris, en gros, c'est que je dois éditer le fichier gambatte_libretro.dll.cfg...

Merci pour votre aide, j'espere avoir été clair dans ma question.

J'aimerai creer un fichier cfg specifique pour chaque type de console

Basically what it does is it will look for a per-core config (that can be as slim or as complete as the user wants) and load it overriding the globals when content is loaded. The same applies for games, it will look for a config file named after the game and load it overriding the globals and even the core overrides.

Dans ce cas, en effet tu n'as a rien à faire, si ce n'est mettre le bon shadder dans le fichier cfg du core

Chaque core à un fichier de conf correspondant au fichier core. C'est ce fichier qu'il faut modifier
Par exemple bsnes_balanced_libretro.dll.cfg pour bsnes_balanced_libretro.dll. Dans ce cas si tu renommes bsnes_balanced_libretro.dll en SuperNintendo.dll.cfg

J'ai relu ce que tu avais posté sur l'override et de ce que je comprend ce que tu veux faire (un fichier core pour plusieurs consoles avec différentes config), n'est pas possible.
Ce qui est possible c'est d'avoir, comme dans Mame, une config par core, puis une config par jeu

A good example of why I am doing this is :

Game Boy and Gameboy Color both use gambatte_libretro.

So for Game Boy I need to use the Game Boy overlay and for Game Boy Color I use the Game Boy Color overlay.
Also I use the original GB shader for Game Boy and use a crt sharder Game Boy Color.

Game Boy uses gambatte_libretro.dll ; Game Boy Color use gbc_gambatte_libretro.dll

Two cores, Two config files.

For whatever reason when I set the options in HLHQ for systems that use the same core. The settings do not take. For instance. If i set up Gameboy for original overlay and original shader. And load it, it works fine. But when I set up Game Boy Color with different overlay and shader and load that, the overlay and shader stays with the original Game Boy one.

The only changes I have had to make in Retroarch.ahk was to change the system id, from "LibRetro_GBC","gambatte_libretro" to "LibRetro_GBC","gbc_gambatte_libretro"

I do almost nothing in hlhq and use 1 core and 2 config files for different shaders/overlays, but you have to rename the config to the system name

marx is right, we have system cfgs in the module for that very reason. Look at the section where it chooses what cfg to load, it looks for a system config, core cfg, and finally global config.

Game Boy uses gambatte_libretro.dll ; Game Boy Color use gbc_gambatte_libretro.dll
Two cores, Two config files.