Sounds interesting I’ll try it. I thought it was already possible to use a bg_under.png since some textures were named this way.
This workaround you suggested sounds interesting, mind that what I’m trying to do is have the light reflect on a metallic layer not come through it, I don’t think the end result will be the same. But I’ll test it and show you.
Yeah, i suppose you’re right:
through => alpha blend modulates a mix
on => alpha blend modulates an add
I’ll try to add an option so that ambient lights are added instead of mixed to/with bg_over and bg_under.
@Starman99x
I pushed a possible solution right now:
Also, colorization size, set to a low value, will avoid the ambient light to bleed over the tube, keep it in mind.
As a side bonus, since i was there, i decided to allow to always add a certain amount of the led lights over the foreground image when the alpha blend mode is set to add, this gives a nice effect:
Have fun!
Wow! This looks cool! I’ll play around with it and see what I can make.
But I have one small issue with the rotation stuff we discussed before, so I tried to load different texture files for different rotation states, but I couldn’t follow your instructions well, and it didn’t work, here’s how I named things:
bg_over= “…/shaders_slang/bezel/koko-aio/textures/FBN_$VIEW-ASPECT-ORIENT$_FBN_R.png”
FBN_VIEW-ASPECT-ORIENT-HORZ_FBN_R.png
FBN_R_VIEW-ASPECT-ORIENT-VERT_FBN.png
Here’s the texture files too:
I know you have to run the latest retroarch for it to work, and according to this doc it seems it should.
What happens when you run your presets? An error or maybe it seems to ignore the substitution?
To test, i’d need the whole slangp too.
I can give a deeper look by tomorrow…
This is what happens:
It loads the default bg_over.png. Here’s the slangp too.
Take your time, sorry for making a lot of requests.
Gave a quick look and It seems right, but didn’t tested it.
@HyperspaceMadness : do you agree?
@Starman99x: Are you sure you’re using the latest RA version?
What puzzles me is that it doesn’t throw an error, but just uses the main texture, like the override is missed through the reference jumps.
what happens if you simplify and just use a single reference?
Are you sure you’re loading the right preset? Sorry for the question, but I couldn’t find an answer by myself.
Yes I’m using version 1.15.0, I’ll try your suggestion and see what I can do.
Looks right, but what I recommend is opening the log window as mentioned in the docs which will show you warnings/logging about what it was looking for
This is my thought as well.
Ok actually now I see the problem, there is no space after the texture name, it needs a space E.G.
bg_over =
vs
bg_over=
I need to see if we can add some sort of warning for this when a config or preset file is loaded, since this is a general retroarch issue
Now, @kokoko3k - I need to complain: How will I EVER be able to make a new release of the arcade shaders if you provide additional killer features on a weekly basis?!?!?
Edit: New screenshot, I apply 85% Alpha just on the bezel, and it takes the color from the ambient light very nicely … so here goes my release, back to work.
What a killer feature!!!Indeed, that was the problem. But now we have another problem:
While the horizontal orientation worked fine, when rotating screen orientation via RetroArch/Output the rotated/vertical texture is not being utilized, instead it’s the horizontal one zoomed in:
I tested this with both MAME and FBNeo cores.
Here’s a new zip that contains a test preset with new textures, the preset goes into Retroarch/shaders. While textures go into koko-aio/textures.
I downloaded your texture and presets, but it’s not clear to me what are you trying to achieve.
First, take in mind that after changing any retroarch option, you have to reload the shader for it to react to changes and behave differently.
As far as i can understand, the wildcard you are using is to load different textures for rotated and unrotated output displays, so your goal is to use different textures for whan the viewport itself is rotated, gotcha.
…but there are incongruences in your slangp.
You used:
bg_over = "shaders_slang/bezel/koko-aio/textures/FBN_Vertical_$VIEW-ASPECT-ORIENT$_FBN_Rotated.png"
The you provided 2 textures:
wildcard matching will never select the first one, see that it ends with “Vertical”, while the wildcart itself $VIEW-ASPECT-ORIENT$ is supposed to assume two different values:
VIEW-ASPECT-ORIENT-HORZ or VIEW-ASPECT-ORIENT-VERT
So the correct naming for it to pick different textures is:
…and in the .slangp: bg_over = “/path/to/same-pre-string-as-other-$VIEW-ASPECT-ORIENT$_same-post-string-as-other.png”
In other word, texture names has to be identical, the only things that can change are the strings in place of any $WILDCARD$
-edit-
…and understood.
Since koko-aio is aware of the rotation state, it already had the ability to rotate the background image, and it does exactly that.
It is configurable:
from koko-aio docs.md:
Rotate image mode
This could be needed when dealing with vertical games.
Use -1 to let the shader try to guess if the rotation is needed.
So, it you want to provide different textures by yourself and manage this externally, set the option to 0.0
Other issues regarding the texture naming are still valid.
Hi there estefan,
I was rethinking to the Wrap mode function i added a while ago and come to the conclusion that it is useless and maybe I started this mess by answering you the wrong way.
The right answer is “yes” there is an alternative way to do that.
bg_under_wrap_mode and bg_over_wrap_mode can take several values:
…and you set them in .slangp the same way you set any other parameter.
So my question is:
Is really needed to change the wrap mode as a runtime option in the shader?
Ditching it would free the code from some branching and complexity.
I’d ask you to try to set Wrap mode in koko-aio to default and use the retroarch’s builtin bg_under/over_wrap_mode instead.
If you’ll be able to do the same things as before, i’d cut that code from koko-aio.
Can you send the properly named files and properly edited slangp so I can take example from them? Because I’m still a bit confused about naming.
Hi again, @kokoko3k. I do not need a runtime option, although it is of course nice to test in real time. But no problem to edit that in the preset. In my use case, I will hardly ever head for a repeat option as it looks weird with real looking artwork. Best, Stefan
@Starman99x
Stripping the file paths for clarity, In slangp i used:
bg_over = “same-pre-string-as-other-$VIEW-ASPECT-ORIENT$_same-post-string-as-other.png”
The filenames i used:
See? the only thing that can change is the BOLD TEXT
@estefan3112, right then, i’ll cut it off.
…done, i made another static option in config.inc:
// #define ALLOW_BG_IMAGE_TEXTURE_WRAP_IN_SHADER
That way you can easilly have the old functionalities by removing the leading “//” and it won’t impact performance as long as it stays commented.
koko please go easy on me 
I still don’t get it, what does this mean:
and this:
If you can just provide a ready to use preset with properly named textures, I’ll be able to follow you more clearly.
It means that text is common to both filenames. I literally use that filenames!
Just use that in place of your bg_over=xxxx (prepend the path ofc) and everything will work.
#reference “shaders_slang/bezel/koko-aio/monitor-slotmask-bloom-bezel-backimage.slangp” BG_IMAGE_OVER = “1.000000” DO_AMBILIGHT = “0.000000” DO_GLOBAL_SHZO = “1.000000” GLOBAL_ZOOM = “1.005500” BG_IMAGE_WRAP_MODE = “1.0” bg_over_wrap_mode = “clamp_to_border” bg_over = “shaders_slang/bezel/koko-aio/textures/same-pre-string-as-other-$VIEW-ASPECT-ORIENT$_same-post-string-as-other.png”
This is what happens when I turn auto rotate image off:
Now the horizontal image is flipped wrong.
And the vertical image/texture still doesn’t show up when I rotate the display. Even after reloading the shader.
So I decided to give up on this and just make a separate slangp for rotated displays.
But if somebody is willing to help make this possible (to make an auto rotate preset), here are the files I used, so make something that works with them, and I’ll include it in the upcoming pack I’m making from @soqueroeu new designs.
Maybe there’s a better way to do things if we take a look at the “Updated vertical presets with automagical variables” by @Duimon I just couldn’t figure it out on my own (I’m still a newbie).
It worked for me, weird. btw, maybe those new features deserve a thread to be explored deeply.
