Confirmed.
I’ll go through every core that I have a wildcard for and see if any are affected.
Thanks for the report!
Confirmed.
I’ll go through every core that I have a wildcard for and see if any are affected.
Thanks for the report!
Turns out PPSSPP is the only core affected. (Vectrex was spared because it always uses glcore.)
Any other preset that might have an issue was created recently so I am confident all is well.
While I was elbow deep I decided to add three new presets.
TV5
TV6
9519
9519 Night
None are perfect (Nor do they perfectly reflect my Mega Bezel versions.) but I think they look pretty good. (I had to do some quick Photoshop magic on the TV5 source, and some manual compositing on the 9519 Night graphic.)
Here’s one more. (The last from my Vintage TV pack.)
Panasonic TH20-B8
No fancy dual reflecting bezel, but very functional.
You can click my name at the top of this post and message me. I’d prefer that to my private email. (At the start of the conversation at least.)
So how do you force the exact bezel color you want in koko-aio? hex codes for example.
I use an early version of @hgoda90’s bezel color converter. (Now a preset editor.) I had created a python script that took a hex value input but abandoned it.
The current preset editor should work just fine.
The latest koko-aio update is now merged into main RetroArch.
I’m excited for your upcoming update.
That is good news. I have some work to finish, then some testing… it should happen fairly soon.
Wrong thread I think.
Oh lol
This is my own fault for trying to multitask. My time has been totally overtaken by schoolwork lately, and the one time I decide to post something on here… I done goofed.
Hi everyone, I wanted to report this resizing problem. I use a POCO M4 Pro smartphone. Of course everything is updated to the latest available version and I have set the resizing aspect to “full”, I also use the Vulkan libraries. I attach some example images with the first one only with Kokoaio and the other two (where you can see the problem) with duimon-kokoaio:
What is it that you expect exactly? koko-aio doesn’t adapt to screen aspects like the Mega Bezel.
I have plans for a 21:9 pack but other aspects are probably off the table.
Ok thanks, I had the chance to try your package only on smartphone and not on Computer, since on Smartphone I can only use koko-aio. So in this scenario it’s normal, I understand. Thanks for the answer.
It seems LRS2 is finally out of Alpha:
This requires some file renaming for the glcore flip params.
Is the next update coming soon? just checking to see if I should manually fix the broken parameters from the older koko-aio versions, or wait.
If you are talking about the auto flip wildcards… they all use the $CORE$ wildcard… which is broken ATM.
I fully plan on updating anyway but it has been so long that I will need to do a deep dive into koko-aio to at least add new base presets. (I will assume that the wildcard will be fixed at some point so leave that as is and add a new LRPS2 entry to the list.)
I have been waiting for my new glasses to arrive, which they have.
We’ll see what I can find time for in the very near future.
So… I started digging into this and it turns out I left it in a very incomplete state. I think I had some questions that have since been answered. (About updates that were recent at the time.)
There are a lot of wildcard references that may not be required so I need to dig into my presets a bit to clean things up.
Rest assured that I am in elbow deep now and will stay there until I get this thing updated.
Thank you for your hard work!
So… I think I am stuck.
I just tested the nightly and the $CORE$ wildcard bug is still there.
Changes koko made will let me eliminate flipped versions of my bezels (Since the shader handles the bezel color variations now.)
The problem is that I have no way of testing my wildcards to verify that the shader handles the bezel correctly. (Or if I need to add some parameters to handle it.)
The user can fix the flipping and save a new preset. It’s inconvenient but not out of the ordinary. (That’s the way things were before wildcards.) I just don’t want them to also have to tweak the bezel.
Going in and blindly removing seemingly unnecessary bezel graphics and parameters seems like a bad move at this point.
My only hope is that @HyperspaceMadness, or the dev who performed the wildcard “cleanup” can fix it sooner than later.