Koko-aio shader discussions and updates

[kokoko3k]

Yes, 2003+ outputs at 1024x768 so has less aliasing, where FBNeo just 640x480; They both looks ok if not zoomed in IMHO. (and for a fair comparison, the screenshots should be 1:1, but they all seem to have a different resolution (?) )

I cannot speak for other cores, as I don’t know how they render the beams; what appears evident is that the bloom is not doing its job in Mame 2003 and Mame current; that could be indeed due to an higher core resolution or a less bright picture.; That could be probably worked out by pushing the the input signal gain and/or tweaking the blur radius by a small amount.

[estefan3112]

Thank you! Sorry for the unclarity on the shots: Identical settings and identical slangp presets, only the 2003 cores having the hires presets. Screenshots then just cut out manually in order to save space.

[estefan3112]

Its identical settings. Just switched the Core Association. MAME current looks bad in both presets.

[kokoko3k]

It is like its output resolution for Vector games is really low.

[estefan3112]

Exactly, also the fonts pixelate.

[estefan3112]

Mame Current now being an eye candy:

game-specific core options:
mame_alternate_renderer = “enabled”
mame_altres = “1280x960”

preset updates (a bit overdone for the screenshot):
IN_GLOW_POWER = “1.000000”
IN_GLOW_SPREAD = “1.050000”
BLOOM_SIZE = “4.000000”
BLOOM_GAMMA = “1.000000”
BLOOM_GAMMA_OUT = “0.900000”
BLOOM_POWER = “3.799998”
So MAME current can really rock vector games!

[kokoko3k]

“neon” preset as a base?

What value you’ve set to “clip to white”, the new parameter?

edit: Nevermind, just noticed you lowered input gain.

Oh, you may want to check the very latest dev, as it changed the bloom code to better “track” thin bright lines or little points, hoping for good; vector games should benefit from it.

[K-rnivoro]

Hi @kokoko3k. I was trying to adapt my .params files from HSM-MB to Kokoaio. I’m interested in vertical layouts in particular. Thing is, many overlays use a “plastic” bezel, so the trick is to reflect over that bezel, but not actually display the generated bezel, only it’s reflection.

So, I’m not sure if there is an option in kokoaio to do that.

Also, some overlays have artwork over the bezel, like this Asteroids. My question is if the bezel can be drawn as “background”.

Thanks for your support.

[kokoko3k]

@K-rnivoro

reflect over that bezel, but not actually display the generated bezel, only it’s reflection.

There’s no option to do that, so the images have to be (soft) cutted from the monitor frame with a gfx program, and the new frame color has to be set in the shader to match the new image inner edges borders (see stock 1084S presets).

@K-rnivoro

some overlays have artwork over the bezel, like this Asteroids. My question is if the bezel can be drawn as “background”.

The user provided image can be set as background or foreground; as a consequence the stock bezel would be painted over or under.

[estefan3112]

That screenshot is already latest dev code. Compared to your eyes, I consider myself blind - but I really like the result! The asteroids in Asteroids suddenly shine in 3D, and I now also upscale to 1600x1200 - still much to explore!

[kokoko3k]

Since my Retroid Pocket 5 is hopefully on the way ( ), there’s a new static feature called Conditional FPS halver.

It halves FPS when they are higher than 49, so it turns 60 and 50 fps content into 30 and 25 content, and does not touch 30 and 25 fps content.

It can be useful to spare battery life or in cases when the GPU is not fast enough to render at higher fps, also the halved FPS have lower visual impact with smaller screens.

In my case, it allows my Haswell to run Flycast at solid 30 fps with standard presets.

This functionality requires retroarch > 1.19.1, so, you’d need the nightly builds by now.
To use it, in file config-user.txt, turn the line:
// #define FPS_HALVER
into:
#define FPS_HALVER

[kokoko3k]

Just pushed a new horizontal mask preset, named wwx, it is like the wx mask, but less spaced:

[kokoko3k]

I updated GameGear presets by looking at online shots, and also added ghosting to it, the image was too vibrant before, while the LCD screen of the Sega handheld was really poor.

Also, the mask has been set to rgb instead of the original rgb for a better look on rgb monitors.

…night presets have no added light on the display:

…suggestions welcome!

[kokoko3k]

This is possibly the new/tweaked gba preset instead; previous one was too bloomy, even there adding ghosting (about 2 frames)

[Hari-82]

GBA is looking great!

Game Gear looks nice as well but from the screens seems that the grid is not present/visible (sonic), last time I played on a real game gear was like '92 or '93 so I do not actually remember how the real thing was, just saying

[kokoko3k]

Thanks, indeed there is no grid in GG, strange, I was sure it had, maybe is a screenshot issue, will check tomorrow…

-EDIT-
I’ve messed up the preset somehow, thanks for pointing it out!

Fixed and updated screenshots.

[RetroGames4K]

These look really good! .

[p1mrx]

@kokoko3k

…however, looking at real hardware, i fear core is not good, see the shot here:

I don’t think that’s real Asteroids hardware. It looks like AAE (Another Arcade Emulator).

[kokoko3k]

@p1mrx

That screenshot illustrates the problems with libretro-mame’s software rendering. The bullets are thin vertical lines instead of glowing circles.

I am confused about why do you think is not real hardware and if that is somehow related to the isolated points not glowing enough issue.

[Jaxsown]

Did you receive your RP5 ? I’m curious about the preset you’re using for handheld and console like SNES/PSX I posted on the sbc reddit recently about your shader : https://www.reddit.com/r/SBCGaming/comments/1himf6o/for_those_who_fear_the_black_border_burn_in/