Duimon koko-aio Presets

RetroArch Additions Overlays
#189

Since the koko-aio presets have the parameters for the adaptive-strobe-koko bfi, does that mean it’s fully built into the preset? Using the bfi alone or layering it with the preset yields different effects.

#190

Hi there!

koko-aio integrates the adaptive-strobe-koko code so you don’t need to layer it (/append pr prepend) as a whole new shader pass; this provides a more efficient way of having that bfi-like experience, so it is lighter on the gpu.

Now, since Duimon’s koko-aio Presets references the main koko-aio ones, you don’t need to deal with adaptive-strobe-koko standalone one at all.

However, from what you wrote: “koko-aio presets have the parameters for the adaptive-strobe-koko bfi”, it seems to me you are not using the latest koko-aio.

To have adaptive-strobe working with Duimon’s koko-aio Presets:

  1. Update your slang shaders via Retroarch’s online update
  2. Enable the adaptive strobe plugin in koko-aio by copying “/shaders_slang/bezel/koko-aio/config/plugins/disabled/adaptive_strobe.txt” to “/shaders_slang/bezel/koko-aio/config/plugins/disabled/adaptive_strobe.txt” (create the “enabled” folder if missing).
  3. (Re)Load a preset.
  4. Tweak adaptive strobe to your likings, and save the preset for future use.

Hope it is clear, feel free to ask more if it isn’t :wink:

#191

Thanks for the response. I’m using Retrodeck so the online updater for Retroarch isn’t there. The config folder for koko-aio doesn’t have a plugins folder at all. But it does have a few .txt files. I checked ‘config-user-optional-template.txt’ and the adaptive strobe section says ‘// #define DO_ADAPTIVE_STROBE’.

#192

I made a copy called ‘config-user-optional’ and removed the ‘//’ in as the file suggested and now the BFI works! The screen flashes rapidly when entering the Retroarch menu but in-game it works normally. The standalone shader did that too. I’m also noticing a radial wavelike interference with the crt mask when bfi strength is above 0.50.

#193

Yeah, for older versions it was supposed to work that way; newer ones do not pollute the parameter list with disabled/inactive features anymore (that’s what the koko-aio plugin system is for).

Care to discuss that in the appropriate thread, maybe with more details/screenshots?