Duimon koko-aio Presets

[Duimon]

@Starman99x

Absolutely beautiful work

Thank you. I did have to go into my Hybrid Illustrator source and create/render a new graphic. The screens could be a bit bigger but the artist in me wants to preserve enough of the outer details to justify the decision.

@Starman99x

consider bg_over for most handheld overlays

I am using background over, for the presets that require an overlay. (Dual screen.)

@Starman99x

it would make the images inflate in size because of the .png requirement.

Not only that but I would have to re-render all the handheld images.

I will consider the idea for some time in the future. I used the Mega Bezel to render the handheld images, using the “Black Screen” rendering parameter. Even so, the night images don’t select cleanly. I would have to r-render and do post on at least 67 images.

FYI. I actually used the Mega Bezel to render all of the images. I just used various layer order parameters to hide the screen and the bezel when I needed to.

@Starman99x

it retains that tiny shadow over the image

Again, I would have to create that shadow.

I do like the shadow. The edge shadow feature in the Mega Bezel was one of my first feature ideas for the shader. HSM was gracious enough to add it in.

[Starman99x]

Understandable. But is there a disadvantage to just using your RA Overlays instead of remaking everything? I did that for my personal setup and would like to mind any downside I didn’t notice:

[Duimon]

The only disadvantage is that I reduced the bezel height and width for handhelds while I was rendering for my koko-aio pack.

The advantage would be that the overlays were updated along with the Mega Bezel so they are ahead of my koko-aio pack. (Which is also a disadvantage because they wont be a drop in replacement. Some parameter adjustment besides BG_IMAGE_OVER will be required for the updated art.)

Go ahead and use them for your personal stuff, but my OCD probably wont let me use them in my pack.

[Starman99x]

Here’s my take on ambilight overrides for everyone to try:

BG_IMAGE_NIGHTIFY = "0.50"

DO_AMBILIGHT = "1.000000"
AMBI_STEPS = "10.000000"
AMBI_FALLOFF = "0.300001"
AMBI_POWER = "0.500000"
AMBI_GAMMA = "1.200005"
AMBI_OVER_BEZEL = "2.000000"
AMBI_OVER_BEZEL_SIZE = "0.250000"
AMBI_BG_IMAGE_BLEND_MODE = "1.000000"
AMBI_ADD_ON_BLACK = "0.000000"
AMBI_BG_IMAGE_FORCE = "1.000000"

It’s hard to balance things out between dark and light bezels, bright and dim games. So I recommend using Duimon’s day bezels combined with a nightfy override, like the examples above. The default parameters would not look right (depending on base presets) as they were made for different use cases.

Any suggestions and examples would be highly appreciated as I’m still experimenting.

[Starman99x]

There’s an additional glcore flipping case that needs to be addressed, like in vertical Atomiswave and Naomi games, where the content is rotated and flipped at same time (Flycast core):

[Duimon]

I’ll take a look at the arcade preset to see what I can do but it doesn’t make sense to do anything with the dreamcast presets.

I’m not sure it will be possible to use wildcards to do this automatically. I may have to create a dedicated preset.

I am unsure why I didn’t include my SEGA Naomi graphic in this pack, it may have something to do with the bezel.

I’ll take a look because using that graphic for this case seems logical.

Can you give me an example game I should test?

[Starman99x]

@Duimon

Can you give me an example game I should test?

For Atomiswave there’s waidrive, for Naomi there’s ikaruga.

There’s also Sega ST-V games with Kronos core, like “batmanfr”, since this core has a glcore flipping issue as-well.

[Duimon]

Here’s what I’m getting with the current Arcade preset.

Atomiswave…

Naomi…

ST-V.

Flycast and Kronos already have wildcards set up and it looks like they are working as intended.

[Starman99x]

I’m not sure what is causing the problem on my side. My video driver is set to glcore, and I’m loading the preset as it is, no overrides. And I keep my cores up to date from the default nightly builds url. The “Allow Rotation” for cores is also ON (default).

[Duimon]

Having your driver set to glcore is not ideal.

I recommend having it set to Vulkan and enabling the “Allow Cores to Switch video driver” setting.

Since you have yours set to glcore, make sure none of these cores are using software rendering internally.

Also, I am using a development build of the shader. When I get home I’ll try the current version.

[Duimon]

@Starman99x

I’m not sure what is causing the problem on my side.

Apparently both the cores you mentioned support Vulkan, so my tests were successful.

This is an issue with rotation using glcore.

I will have to do some thinking on how to gracefully handle this. I’ll probable need to set an additional wildcard to handle rotation on Kronos and Flycast.

I’ll post when I have a solution and add it to the upcoming update.

[Duimon]

I’ve got a solution for Flycast. Now I just need to make it elegant.

Baby steps.

[Duimon]

I’m not liking the mess this is creating with the presets and wildcards.

I’m going to create specific “Arcade_Flycast-[Bezel-V]” etc. presets instead.

If the Kronos core works with the same preset I will name in accordingly, otherwise we’ll get a Kronos preset as well.

---

The biggest issue is that FB-Neo and MAME aren’t affected by this issue, and I have no way of knowing what core users will use with the preset.

Edit: I’m not noticing an issue with the Kronos and ST-V games using glcore.

Background is the correct orientation and the bezel is shaded correctly.

Are there any vertical ST-V games?

[Duimon]

@Starman99x @kokoko3k

Making a lot of progress. The bezel and cab style presets are all updated. Here are shots from the tilted cab.

Horizontal

Vertical-90

Vertical-270

I edited all my cabinet graphics, both tilted and non-tilted, lowering the height of the joysticks to give more room for the bezel.

The original graphic depended on being able to layer over the bezel via Mega Bezel.

I’ll have to recreate the Flycast specific references next. Then go through all my “Monitor” presets that use a bezel.

[Starman99x]

A recent windows update broke open gl on my pc so I can’t confirm this, but there’s a potential glcore bug that you might want to check.

The PSP preset (potentially others) might need a different global Y override when using glcore.

[Duimon]

Confirmed.

I’ll go through every core that I have a wildcard for and see if any are affected.

Thanks for the report!

[Duimon]

@Duimon

I’ll go through every core that I have a wildcard for and see if any are affected.

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.)

[Duimon]

Here’s one more. (The last from my Vintage TV pack.)

Panasonic TH20-B8

No fancy dual reflecting bezel, but very functional.

[Duimon]

@LaFrance

don’t know the best way to reach you

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.)

[Starman99x]

So how do you force the exact bezel color you want in koko-aio? hex codes for example.