Koko-aio shader discussions and updates

I made this PVM style diffuse image for everyone to use:

The screenshots are using these overrides:

DO_BACKDROP = "0.300000"
BACKDROP_JUST_TUBE = "1.000000"

//The following override requires the correct path to images:

backdrop = "PATH/TO/PVM_Diffuse_1024.png"
3 Likes

2 Likes

Oh you need the latest koko-aio dev build. Just grap the entire repo and replace your current koko-aio shader folder:

shaders/shaders_slang/bezel/koko-aio

But be careful if your current koko-aio version is old, your packs might depend on that, the shader received quite some changes since version 1.9.30 that broke some packs like Duimon’s.

My packs are safe to use with the latest dev build and Duimon is working hard to update his pack too.

2 Likes

Is there a way to move the Gradius Gaiden game screen to the right so that it is in the correct position when ambient lighting is on? This game has a black blank space on the right side of the screen.

1 Like

Override game geometry/horizontal position.

Maybe you want to zoom it too to fill the screen by moving other knobs under the same section.

Documentation is here: https://github.com/kokoko3k/koko-aio-slang/blob/main/docs-ng.md

1 Like

Regarding this, I just pushed a change that allows you to target a specific TVL:

From documentation just pushed as well:

TVL: core resolution only. >0 overrrides previous.
    ---------------------------
	If you use core resolution and this parameter is not 0.0,
	the phosphor width will be computed so that the screen will
	contain the specified rgb triads amount.
	Using core resolution means that the triads will follow the
	screen curvature, hence possibly exposing moire artifacts at higher TVLs.
	To mitigate that, it is advised to set a proper
	"Phosphor width min" value.
    Tests shows that on a 1080p screen you can easilly target a typical of mid-range consumer TVs
    with a TVL of 410, provided that you set minimum phosphor width of at least 30
    and a phosphor width min->max less than 5.0.

This is an example of targetting a “TVL” of 410, I think the best you can expect from a 1080p with standard curvature values, no bloom, halos, just the mask:

The preset has just been pushed and named as Presets-ng/Monitor-slotmask-TVL410.slangp with a bit of bloom added:

6 Likes

Interesting…what would you put those settings at for a 2160p display ouput?

Find rhe maximum you can get without seeing moire; for the task ypu can use a provided test pattern (first parameter) to quickly spot it; the best is the one that show a temporal black/white fade.

Once you found the maximum TVL, decrease it till it pleases you.

I think you can go up to even 550, but then it depends on your eyesight and screen dimensions.

If ypu let me now the upper level without moire, I can add it as a reference in the docs, thanks!

1 Like

On my Sony Bravia 4k (55inch) OLED @2160p = TVL 883 seems close to the sweet spot (input signal gain at 1.0 ).

One last thing - with the new interlacing tweaks, all I get on games like Ridge Racer is flashing colours - any pointers?

Uhm, old Retroarch? Shader needs to estimate the frame timing to activate that feature only when it is low enough (50,60fps) and skip it on higher ones (25,30fps).

Yeah, I use the //#define _HAS_ROTATION_UNIFORM

Any work around?

I cannot check right now if that’s the problem, but either way, the best I could do to support older versions is to skip any check through a static option, not very useful…

Ok, no worries.

Thanks again.

1 Like

Anyway to adjust the overlay/menu opacity so that I can bearly see the onscreen menu? Will make it easier to dial in the TVL so I can provide the correct TVL strenght for 4k.

Settings, user interface, appearance, opacity.

Thanks - will test tomorrow and report back.

Odd, all I have is framebuffer opacity, which alters the background image, rather than the menu overlay.

Weird:

https://www.reddit.com/r/RetroArch/comments/knehwe/is_there_a_way_to_change_how_strong_the/

1 Like

maybe you are on an older ra release?

I think framebuffer opacity was something from older versions.

1 Like

yeah, I’m on 1.14…or should I say stuck on 1.14…batocera, that I can’t upgrade.

1 Like