Duimon koko-aio Presets

RetroArch Additions Overlays
#148

The koko-aio docs describe it like this:

textures/side_shade-helper.png
    Bezel frame inner area, the reflective part, is shaded by default so that
    upper area is less bright and lower area is a bit brighter.
    While the shader does not expose controls to change that, if you want,
    you can edit this file to alter the shades.
    The more a primary color is saturated, the more the shade will turn to dark.

So maybe it’s already working on top of your bezel wether custom or default (I didn’t confirm). I think rotation (90/270/180) works now by automatically rotating this side shade helper texture too, alongside bg and spot.

1 Like
#149

Yup, but docs are a bit outdated. There’s a parameter in the shader that is able to modify the contrast between the bright and the dark shade.

2 Likes
#150

Apparently, none of my koko-aio presets will load in the nightly. Either do any of my Mega Bezel presets where I am using a wildcard in a reference.

I can reference another file, that references a wildcard, but I can’t call one directly.

@hunterk do you know if this is intentional or maybe a progression on the existing wildcard issue?

Everything loads in the stable release.

I need to create some files and change some references in a test preset to see if any of the wildcards actually do anything or if the workaround is just hiding the fact that they are broken.

#151

Hmm, when did you update last? There haven’t been any commits that would have touched any of that for a while.

1 Like
#152

Minutes before I posted.

Before that I was running the stable, so it could have been quite some time ago.

1 Like
#153

@hunterk

I did some testing… here’s the exact issue to make it clear.

In my "RetroArch\shaders\Mega_Bezel_Packs\Duimon-Mega-Bezel\Presets\Standard\MAME\MAME-[STD]-[Guest][CABINET].slangp" preset, I have the line…

#reference "../../../res/layers/MAME/CAB_$CORE-ASPECT-ORIENT$.params"

…it fails to load on the nightly but loads in 1.20.0.

If I add an “auto-settings-cab.params” file to the folder… containing just the line…

CAB_$CORE-ASPECT-ORIENT$.params

…and reference that file instead, it loads, and the wildcard works.

My concern is that it is an unintended side effect, and that the behavior will revert to normal before a stable release.

If it’s intentional, for some reason, then I can do the work to get things functional again.

BTW, @HyperspaceMadness already uses a similar method in his presets, so my workaround doesn’t solve the $CORE$ wildcard issue. :frowning_face:

3 Likes
#154

The changes aren’t intentional, no. We would want that stuff to keep working as-is.

2 Likes
#155

Thank you for your quick response.

What I can do then is just update for the 1.20.0 stable with broken $CORE$ wildcards.

It won’t be any more inconvenient than before we had wildcards. :grin: At least that will get me up to date with kokoko’s shader.

Thanks for saving me a ton of work, and here’s hoping things in the nightly will improve soon.

4 Likes
#156

Hi there, it seems gameboy advance presets has issues with hi resolution content like 3ds; even if I’m not sure why this happens, at least the fix is easy: just set IN_GLOW_WARPSHARP_GAMMA to something higher; 0.5 should be ultra-safe.

2 Likes