Yes I know. 
It also zooms only at integer jumps when it’s on, so I still think Non-integer Scale option is the best for a consistent experience.
Of course, if Integer scale is absolutely necessary, then viewport zoom works well.
Just following up on this. I was able to reproduce the issue using the MBZ__0__SMOOTH-ADV__GDV.slangp base preset.
For best results view screenshots from Oldest to Most Recent.
Manual mask size parameter already does this, but it works nicely only with “RGB” masks, making it a ‘tweakers’ option in general. For example, mask 12 (RRGGBBX) looks much nicer with 4k compared with 2-size mask 6 (RRGGBB) due to subpixel banding issues.
Masks 0,5,9,11 and 13 work with subpixels directly, making them bigger than size 1.0 would open a new topic on strangness. 
But they are very nice size 1.0 masks…
CRT Royale did something in this direction where you can specify the TVL independant of resolution, but doesn’t work or look fair enough below 4k imo.
One of the issues i’m seeing is that there is a lot of 4k optimized presets and it’s harder to get a 1080p preset from it than a 4k form 1080p by increasing the mask size. Pure 4k tweaking and pure 1080p tweaking simply give better results.
2 Likes
Thank you. “Non-integer Scale %” worked great as well. I very much appreciate everyone’s feedback!
2 Likes
See the picture below, black vertical lines will appear after moving the layer. When using the old version of Mega_Bezel0.9-2021, you can remove it by moving the viewport position X, but the black vertical lines cannot be eliminated with the latest version. May I ask if the latest version can solve this problem, thank you
That is the background mirror wrap edge, and it can’t be removed in any version because the preset is a single image layer.
You can get lucky by making tiny adjustments, which will mitigate it somewhat, but @soqueroeu will need to separate the layers if you want it to be perfect.
TBH there are also some edge artifacts in his backmost image (Desktop and wall.) that need to be eliminated.
@soqueroeu intentionally chose to make everything a single layer, for performance reasons.
1 Like
You are using a different preset, which may work better. Aside from the wrap edge (Which will be better if the position is minutely adjusted.) The preset the OP used has these imperfections which will not wrap well.
2 Likes
Missed the edge difference. I was still able to get rid of the black line but the edge would still be a problem.
1 Like
I think this is the question to the answer you’re looking for.
If you would like to “see” 1080p Optimized presets on a 4K display, you can disable scaling in your graphics card driver settings then set your desktop resolution to 1080p. This will show you a true 1080p desktop using only 1920 x 1080 of your display’s 3840 x 2160 pixels.
It might be small and uncomfortable to work with but it should still be compatible with subpixel “aware” masks.
As for maintaining consistency, you can try to use appropriate RGB Masks which maintain the RGB triads as well as a more or less consistent TVL and using your eyes, adjust the Slot Mask height to be consistent with your 4K presets.
At least this is how I went about scaling my presets to work optimally at multiple resolutions.
2 Likes
Ok thanks, I will try it, but at the moment to begin with, I will post my 4k settings tonight if I’ve got time, about 0.00 GMT +1 time. Yesterday I tried a bit on 1080p downscaling the desktop, but at least mask 6 look weird also with BGR turned on. So I need a rest at the moment to try messing with 1080p. 
But I will keep updating more pack settings with time.
1 Like
i just found out a crt shader created by sonkun which is actually quite good, and i’m wondering can i combine that shader with this mega bezel? i just want it to have a crt tv for the border and background
3 Likes
I believe @sonkun is not using a straight-up Guest Advance modification. This will break compatibility with the Mega Bezel.
So, if I am correct, this would mean it is not something that could be done at a user level.
Plain ordinary Guest derivatives, as long as they are using the same version of the Guest shader that the Mega Bezel uses, can be used in the Mega Bezel.
My next guide will detail how to do this.
It is also the last item on my list before the new guides, and an updated version of my pack, are released.
5 Likes
You can also take a look at some of the Community CRT Variations included in the Mega Bezel Examples Package or one of the many variations included in the HSM Mega Bezel Reflection Shader package itself.
Alternatively, you can take a look at these:
2 Likes
Does this only happen when the independent bezel scale is on
1 Like
@lokq12 That’s pretty much the reason my presets aren’t apart of the Mega Bezel project. I’ve gutted and added other shader passes to almost all my guest presets, I’ve taken the “composite” pass from “crtsim” to use for my 3-phase presets, “ntsc” from the “mame” shader to use for my 2-phase presets and I’ve added “sgenpt-mix multipass” to my svideo presets. The only presets that use the guest shader by itself are my rgb presets, so those could be potentially added if anything.
My presets use to be part of Mega Bezel before they commercially went mainstream so you can still use a really old version of my presets if you go backwards (not ideal.)
1 Like
Yes, so far I’ve only seen it occurring when Independent Bezel Scale is on.
More specifically, it only happens when the Bezel overlaps the viewport.
If Bezel Independent Scale is on but the Bezel does not overlap the viewport, it didn’t seem to occur, at least not in my testing last night.
Yeah, I can see what you mean, right now if you choose size 2 on one of the sub-pixel masks you get the mask blown up so that you have Magenta over 2 pixels, is that correct?
I agree that different mask setups for different monitor configs could be pretty interesting, because using the same mask at 1080p and 4k is not going to be a good result as you say.
I’m wondering if we could use some wildcard magic to choose a different params file to load, so the same preset could be loaded at 1080p and 2160p and get different mask settings optimized to the resolution,that seems like it could be a big plus, for tree user they would not have to choose presets based on resolution.
4 Likes
This is the whole idea behind CyberLab Mega Bezel Death To Pixels Preset Pack having 1080p, 1440p, 4K_Optimized folders and IV OLED Presets.
It wouldn’t necessarily give you a bad result but it won’t be consistent.
Presets made with a 1080p or 1440p display in mind tend to look softer/less harsh and end up being higher TVL if used unchanged on a 4K display.
This can be desirable in some instances and forms the basis for my Le’Sarsh_4K_Optimized presets, which are identical to my 1440p_Optimized presets.
Another thing that I’ve learned is that you need to have a certain minimum number of pixels if you want to render a particular resolution at a particular TVL properly.
When you are short on pixels, you’re more likely to get all sorts of anomalies in the fine details of the graphics which is why I ended up using high Integer Scale percentage/Offset values for my SNES presets, which led me to using Bezel Independent Scale. I’ve documented some of these anomalies.
I’ve read time and time again about moire and stuff like that especially when curvature is being used, I’ve observed that moire is less of an issue when you have enough pixels to render the TVL you’re aiming for.
I learned this when doing some experimentation using presets with Graphics. The graphics take away valuable resolution resources from the CRT effect.
I was able to solve the moire issue by using the appropriate TVL mask for the effective resolution left after taking into consideration the amount used by the graphics.
An example of what I’m speaking about could be @soqueroeu -TV backgrounds. Due to the size of the viewport you’re better off using mask settings that are optimized for 1080p than 4K, even if you’re using a 4K display if you want to minimize the chance of getting moire artifacts and other strangeness.
The next thing that makes a good case for having separate optimized presets for different display setups is the fact that the filtering looks different depending on the resolution. There was an issue where the noise and deconvergence wouldn’t scale properly but those have since been rectified in HSM Mega Bezel Reflection Shader with the addition of different scaling/behavior options.
The idea with the wildcards are that you could put whatever needed to be different per resolution in the params files and the wildcard system could choose the correct one.
Basically this would be similar to multiple presets, customized to different resolutions, but accessed by loading only one preset.
You could even have both, an Auto folder which has all the presets which auto determine which params to load, and the other folders with the presets for specific resolutions.
3 Likes