Duimon koko-aio Presets

[Kchlangenddin]

Thank you, @Duimon and @kokoko3k, great job. I like the lightweightness of the presets, allows to utilize fast forward with such a beautiful shader. I have a problem although, bezel_001 and bezel_002 both day and night work just well, but bezel_003 yields me an error. The error: Failed to apply shader preset: Nintendo_NES-[BezeL_003).slangp

Its weird because previous two work just fine which means the installation was done in a proper way, i guess. This relates to any _003 bezel. Anything i can do on my side?

[Duimon]

That error could mean any number of things. Could you post a log?

[Kchlangenddin]

Sure, here it is: `[ERROR] [Vulkan]: Failed to create preset: */home/deck/.var/app/org. libretro.RetroArch/config/retroarch/shaders/Duimon-koko-ato/Presets/ Nintendo_Famicom/Nintendo_Famicom-[Bezel_003]-Night.slangp".

[ERROR]

[Vulkan]: Failed to create filter chain:

*/home/deck/.var/app/org.libretro.RetroArch/config/retroarch/shaders/Duimon-koko-aio/Presets/

Nintendo_Famicom/Nintendo_Famicom-[Bezel_003]-Night.slangp". Falling back to stock.

[ERROR]

[Vulkan]: Failed to acquire from swapchain (err - -1000000000).

[ERROR]

[Vulkan]: Got VK_ ERROR_SURFACE_LOST_KHR.`

[Duimon]

I’m not sure that is a complete log. If it is, it doesn’t look like the error has anything to do with my presets.

The only essential difference in the three presets is the image used to generate the bezel.

Is your log level set to “Debug”?

You can try to update your slang shaders in case it is missing something required, but the bezel_003 presets don’t do anything magical so I have no idea.

[kokoko3k]

koko-ato

Have you redacted it somehow?

“libretro.RetroArch/config/retroarch/shaders/Duimon-koko-ato/Presets”

[Duimon]

The paths are relative so the folder name shouldn’t really make a difference.

Good question though. Why are there two different paths in the log?

@Kchlangenddin, if you want help you will have to let us decide what errors are important.

[Kchlangenddin]

Yeah, i had shot logs on my iphone and copied texts it looks like it didn’t parse the rest of the path, but i can see it is the same. Sorry, i am doing it on Steam Deck and thought this would be a quick solution im going to do a debug level log tomorrow and sent it here.

[Kchlangenddin]

Here is full log, sending directly from SD;

[WARN] [Shaders]: Could not read shader preset in #reference line: "/params/b3scale.params".
[WARN] 
[Shaders]: Could not load root preset for #reference entry: "/home/deck/.var/app/org.libretro.RetroArch/config/retroarch/shaders/Duimon-koko-aio/zzz_global_params/Graphics/bezel_003.params".
[ERROR] [Vulkan]: Failed to create preset: "/home/deck/.var/app/org.libretro.RetroArch/config/retroarch/shaders/Duimon-koko-aio/Presets/Nintendo_Famicom/Nintendo_Famicom-[Bezel_003]-Night.slangp".
[ERROR] [Vulkan]: Failed to create filter chain: "/home/deck/.var/app/org.libretro.RetroArch/config/retroarch/shaders/Duimon-koko-aio/Presets/Nintendo_Famicom/Nintendo_Famicom-[Bezel_003]-Night.slangp". Falling back to stock.
[ERROR] [Vulkan]: Failed to acquire from swapchain (err = -1000000000).
[ERROR] [Vulkan]: Got VK_ERROR_SURFACE_LOST_KHR.

[Duimon]

There is a file referenced… “bezel_003.params”.

The reference line in that file appears to be missing an end quote.

I need to check why I don’t have an error on my end, but you can fix it yourself right now, and will do an update ASAP.

Thanks for the bug report.

[Kchlangenddin]

Thanks @Duimon, could you also advise please what is this artifact called when a blurred waves coming out from the center of the screen? Id like to turn them off but i cant find a proper option in parameters that responsible for that artifact.

[Duimon]

That is called moire and it is usually a result of curvature and high internal scale, or a small screen.

You can try lowering the screen curvature and/or eliminating the pixel mask.

[kokoko3k]

That should not happen, when the resolution is too low for the content (Deck screen resolution is not much), koko-aio switches to fake integer scanlines, not curved.

@Kchlangenddin, what preset and what game(s) have moire?

edit

The fake integer scanlines feature is recent, are your slang shaders updated?

[Kchlangenddin]

I am on fresh shader slang, yes. I play FF2 NES docked steam deck through my tv. TV isn’t big, perhaps under 35 inch diagonal.

[kokoko3k]

Yes, but what resolution is it set to and what preset? I need to know to try to replicate.

[Kchlangenddin]

Resolution is 1920x1080 with Famicon bezel 002 preset.

[Duimon]

@kokoko3k I am using the Monitor_Balanced base preset as default.

[kokoko3k]

Oky, i managed to reproduce. Monitor-balanced is a very steep preset, it has a slight moire at 1080p fullscreen, but as you scale it down it get worse, and even the ~5% space stolen by the bezel is enough to make it evident.

Try to turn down Vertical cell Mask from 0.4 to 0.2 or even 0.0. It will steal a bit of personality from the preset, but will help with moire and will give more brightness in exchange.

Open in full screen 1:1 size to see the improvement.

Original:

0.20

0.0

Yes, there are still wide bands on the sides, but i find them to be visible only on such solid screens, they are far less intrusive than moire itself during real game sessions.

-edit-

Weird thing is that I wrote this post on my notebook, where moire is really evident, but now that I’m on the PC where I crafted the preset, I cannot spot ANY on all of the just posted screens.

Target resolution is still 1920x1080, which leads me to think 2 things.

1. Is the screen size, other than the resolution inducing moire? my laptop screen is smaller.
   
2. Lcd panel itself may cause that due to weird behaviours with some masks.

To verify 1, I stepped away from the monitor, but still cannot spot moire, so 2 is indeed very likely, I’ve seen LCD controllers/screens going crazy with some mask patterns.

Another possibility is that the screen is doing some pixel level processing (sharpness improvements mainly) ruining the mask.

@Duimon and anyone: Please report back if you can spot moire on any of the gray screen I posted.

Using 4k or 1080p is ok as long as you see the image at 1:1 size.

[Duimon]

Yes I can see moire. It is present in all the images. (It does get better each step.)

I agree that it is really only solid colors that show it much.

As a last resort, using this slightly curved bezel, we could turn off the curvature of the screen and leave the curved bezel. (There would be some slight cropping.)

@kokoko3k

Monitor-balanced is a very steep preset

My presets allow the user to select any of your base presets. Which would you recommend for less moire?

[kokoko3k]

Thanks, so either I’ve a moire mitigating display or see #2 …what a world.

-edit

just tried on another big screen, and I can barely spot something; at this point I don’t know if it’s me or the screen, I can say for sure that on the laptop it was a disaster, very evident in the corners.

[kokoko3k]

@Duimon

My presets allow the user to select any of your base presets. Which would you recommend for less moire?

I can answer when i’ll get my hands on the laptop!