Duimon - HSM Mega Bezel Graphics and Presets - Feedback and Updates

RetroArch Additions Overlays
#4825

It is absolutely the right place to ask. :grin:

My Gameboy presets use a bunch of Mega Bezel tricks to try and make it look a bit like the Gameboy-DMG shader.

The preset in your shot probably uses plain LCD-GRID and the monochrome parameter.

To get it to look like this you would have to change a lot of parameters or edit my preset.

The latter is probably the easiest.

Make a copy of my preset (e.g. Gameboy-[STD]-[LCD-GRID]-[Night].slangp >> Gameboy-[STD]-[LCD-GRID]-[Night] - Copy.slangp.

edit the line…

// DEVICE :: CRT
#reference "../../../res/crt/GB.params"

to

// DEVICE :: CRT
//#reference "../../../res/crt/GB.params"

Before

Aladdin-240220-212950
Aladdin-240220-2129503840×2160 1.27 MB

After

Aladdin-240220-213041
Aladdin-240220-2130413840×2160 1.76 MB

Then turn on monochrome to “GREEN”, adjust the Saturation…

monochrome
monochrome3840×2160 1.19 MB

…and save a preset.

2 Likes
#4826

thanks for your in-depth reply, I managed to replicate the look. one last question, if you don’t mind: how can I tweak the intensity of lights on the sides of the case (upper left, lower right)?

1 Like
#4827

There are Contrast, Hue, Saturation, Brightness, and Opacity parameters for the Ambient lights. They are a ways down on the list. (Only the general opacity is near the top.)

You can also chose which ambient layer to use. (The light position/zoom and intensity varies with each.)

1 Like
#4828

Hey @Duimon, I wanted to ask if something changed within your N64 preset. It looked perfectly crisp a few months ago, when I last played and now it looks like this with massive “moire”

Super Mario 64-01
Super Mario 64-011920×1080 655 KB

This is with the following shader preset:

N64-[ADV]-[Guest]-[Bezel]-[Night].slangp

I regularly update Retroarch, cores and your Shader presets, so I don’t know when this change occured.

Any idea why it is like this, now?

EDIT: Same issue with GameCube emulation as well (dolphin core)

EDIT 2: Even if I switch integer mode on and remove curvature, I still get these thick lines:

Super Mario 64-01
Super Mario 64-011920×1080 633 KB

1 Like
#4829

Nothing has changed on my end. My suspicion is that you have changed the internal resolution scale.

If that is intentional, and you don’t care about scanlines, then you can turn them off. If you want scanlines you can use fake ones at 240p explicit res.

#4830

I swear to god I haven’t touched any settings. Internal resolution has always been at x4 on the mupen core for me on N64 (but again, this happens on other 3d cores, such as dolphin, too)

EDIT: I just remembered that I did in fact test some N64 games (using an original N64 controller) 2 weeks ago. I’m positive that this issue was not present during my testing.

I’m at a complete loss here. It looked perfectly and now I cannot get it to work again =(

#4831

Are you using a different monitor, is it 1080p or 4K?

Here is N64 at 4x internal res on my box.

Super Mario 64-240221-150519
Super Mario 64-240221-1505193840×2160 795 KB

It appears I was wrong about internal scale. Are you using any downsampling in the RDP settings? (LOL, Mario’s eyes just happened to close as I took my shot, it is not a glitch.)

#4832

No, as I said I haven’t changed anything in my setup, besides updating retroarch (which does not alter any settings), your shader presets and of course windows updates & Gefroce GPU drivers.

I’m on the same 1080p TV that I have been on for the last 8 years.

EDIT: I’m not using any downsampling

1 Like
#4833

If you have an *.opt in your config folder, you might want to temporarily rename it and start from scratch with your settings.

Nothing has changed with the shader or my presets that would cause this.

Edit: There may be always be something in the latest RA version that could. I will update and see.

#4834

I have just redownloaded a fresh retroarch and started from scratch, and the issue persists. =/

#4835

I hate to disagree, but I changed my resolution to 1080p using NVIDIA’s Integer scaling.

Super Mario 64-240221-152158
Super Mario 64-240221-1521581920×1080 275 KB

I believe I was correct in my initial assumption… it is the internal scale. My proposed solutions still apply.

#4836

I just tried the previous Retroarch Version (1.16.0), and it works here. No issues whatsoever. But it does seem like scanlines are completely invisible there… Maybe they somehow didn’t work properly on 1.16.0? maybe that’s why the moire never stuck out to me?

EDIT:

Take a look: Exact same settings, but on the previous retroarch Version

Super Mario 64 (USA)-240221-223702
Super Mario 64 (USA)-240221-2237021920×1080 503 KB

I don’t know what is different, but something definitely is.

EDIT 2:

I think it’s not the retroarch Vewrsion, but something in the default settings of 1.17.0 that causes y issue. Will try and report back

#4837

Yeah… I upgraded my Retroarch so can’t test. Maybe @hunterk has an idea what change may have caused this.

#4838

Done some more testing. Don’t know what is at fault. It’s not just the retroarch settings. there is something else going on. I have just managed to set up a 1.17.0 version and it works, too. I’m at a complete loss. Probably need to set up everything from scratch. And I don’t know what the heck is wrong.

1 Like
#4839

That doesn’t explain why I got moire when I tested though. :frowning_face:

#4840

Exactly. It’s really damn weird. But you’ve seen the picture above.

#4841

Duimon’s pic with the moire looks like functioning scanlines with a high internal res.

If something looks weird on the new version and you’re using your old config, try moving the config file somewhere else temporarily and see if it persists. If not, you have a bad setting somewhere. To pinpoint which one it is, you can “bisect” your config like this:

How to bisect your config: take a blank text file named retroarch.cfg, copy half of your old settings into it. Start RetroArch and try to reproduce the behavior. If the problem comes back, the bad setting was in that half, so try again with half of that half. If not, it was in the other half, so try that one instead. Rinse/repeat until you find the offending setting

2 Likes
#4842

OK @Duimon & @hunterk I got something:

When I use the freshly downloaded retroarch, both 1.17.0 and 1.16.0, it works, but if I go to online updater and update the slang shaders, the moire suddenly appears.

tested 2 times, it’s reproducable.

However, strangely enough, if I delete the updated shaders again and copy the original shaders from the retroarch zip file to my retroarch folder, the moire stays.

#4843

ah, okay. Sounds like a shader has changed settings somewhere.

#4844

But why, if I delete the updated shaders again and copy the original shaders from the retroarch zip file to my retroarch folder, does the moire not go away?

I’m so confused …

EDIT:

ARGH, so now the issue is not reproducable anymore. If I set up a completely new retroarch Install, the moire is there. What the hell is happening?

EDIT 2:

I’m at a loss here. I guesss I’ll just switch interlace mode to -1 to avoid scanlines altogether.

1 Like