I like this reflective frame very much, but I want to remove the scan line. I tried a variety of methods, but failed to remove it? Is there any way to remove the scan line, but keep other functions?
2 Likes
You can turn the “Interlace and Fake Sanlines Trigger Res” parameter down, (You can go as low as 0.00 and then turn the “Fake Scanline Opacity” to 0.00. You will also need to scroll down to the [MASK]___________________ section and turn off the mask
I usually switch the mask type to CGWG then turn the “0 & 7 Strength” parameter to 0.00.
2 Likes
Thank you, it’s solved, it’s amazing
2 Likes
Thanks for the early peek at the auto cropping…can’t wait to try this out! One step closer to curing the eternal headache that is N64 settings 
2 Likes
7 Likes
Thank you very much, it looks great, between this and the @Duimon presets is the perfect Retroarch.
6 Likes
Nice 
When I set curvature mode to any of the 3D settings I’m getting audio crackling/stuttering with the standard preset. Anyone else? I installed a portable version of Retroarch 1.9.1 to test the new shader features. My main install at the moment is Retroarch 1.9.0 with the last version of Mega Bezel Reflection shader that worked for that build. I’m not encountering the issue on that install.
2 Likes
WOW this is awesome, Duimon working on Layouts for 3DS, and its amazing, i can’t wait for update HSM and put it on my 3DS library 
3 Likes
Can you post some images? Also I’m going to shift the discussion about shader issues like this to the main Mega Bezel thread, just so we can help keep Duimon’s thread more on topic, focusing on the graphics & presets.
This can often be related to how small we are asking to scale the screen with the LCD Grid shader. There are some existing issues with my version of the LCD Grid shader which need to be fixed, but I’m unsure if this is related or not.
Try taking a look at these handheld border shaders and see if the same issue exists within them: Handheld Border Shaders
If it looks good there but doesn’t look good with the same scaling in the Mega Bezel then there is something wrong with the LCD Grid in the Mega Bezel which needs to be fixed. If it looks bad there as well then it’s just beyond the limits of the LCD Grid shader
3 Likes
Thanks for the reply @HyperspaceMadness and happy to move the conversation here. Wasn’t sure where was best so I picked up from where it was last mentioned.
This is how it looks in your Dual Screen-DS_MBZ_2_STANDARD_LCD-GRID preset: Looks good to me
This how it looks in Duimon’s Advanced NDS Vertical shader preset: Does not look good to me
No matter what I try to I can’t get Duimon’s preset looking like your LCD preset image (what I was referring to as “clean” - no uneven lines or banding). Same Core, Same Game, Same resolution (native).
Hopefully you can see what I mean from the screenshots. If there is something to be tweaked in the preset to get there I will happily take the instructions and try to get it sorted.
Thanks as always!
3 Likes
Yeah, no worries 
I haven’t looked at Duimon’s preset, but the difference is probably because the default preset is using the integer scale settings in the shader parameters and Duimon’s isn’t. And he probably isn’t so that you can see more of the handheld body. To test you can go to the scaling settings and choose integer scaling mode 2 which is horizontal and vertical integer scale.
And now that I think about it I think tatsuya79’s handheld presents all use integer scale as well.
Edit:
Another thing to note is that one of the ds screens is 192px tall, the default preset screen is 384px tall (2x) and the screen in Duimon’s preset is 415px tall. Since it’s such a low multiple of the original resolution it’s not surprising its having a hard time distributing the pixels evenly with a strong grid pattern. A good question is if the standard lcd grid preset look the same at the same resolution. The way to test that would be to set a retroarch custom aspect ratio of the exact resolution and see what it looks like. Duimon’s screen that you captured is about 552x415
1 Like
It seems to me that you have the wrong post, it was the post of @Duimon where you wanted to post. https://forums.libretro.com/t/duimon-hsm-reflection-shader-graphics-feedback-and-updates/28146/1127
1 Like
About 3DS, I was expecting a lot for this!
2 Likes
All I did was set the Scanline direction multiplier to 50, both vertical and horizontal. I mentioned this when I did it.
here:
And the fact that some people wouldn’t like it. 
Notice the severe banding in the shot I was trying to fix.
As small as the screen is it might be worth a shot to switch the reference to a CRT shader and turn of scanlines, but leave a mask.
Here’s a test using a Lottes mask.
Here’s a shot using integer scale using the only offset that works with the graphic.
It does look very nice. If you guys think the trade-off in screen size is worth it, I would be willing to modify the graphic to fit the integer scale.
I really just think that even in the second shot, that the LCD-GRID isn’t doing it’s usual awesome job. like this…
3 Likes
For my personal opinion I would go with the integer scale if the preset is going to use the lcd shader.
You may want to figure out what the non-integer scale is to match the results of the integer scale at 1080p, then set it to non-integer scale with this percentage. Then on 1080p And 2160p you will get the exact integer scale, and at other resolutions the screen will still fit your graphic.
1 Like
Yeah, I really think that it’s because the screen ends up so small that it has only a couple pf pixels to draw an lcd element
1 Like
That’s the question isn’t it. At 4K the LCD-GRID using integer might look great but at 1080p the lcd elements are so small it’s really not worth the bother. It’s really odd because the DS resolution is only 256 × 192.
The Game Boy Color at a similar size still looks good with the LCD-GRID.
Could it have something to do with the way the core renders the screens?
1 Like
I stunt think it would have anything to do with the core. For the gameboy in this example there are 2.7 pixels for each lcd element vs the ds example where there were 2.15 pixels per lcd element.
Here are some shots using the handheld borders you linked to, the elements are pretty small in there as well.
The first shot is, like mine, true to the real device layout. The creator uses a 90 pixel gap.
The second is less true and uses the ideal gap of 64 pixels.
I am strongly considering redoing the graphic to use both integer scale and a 64 pixel gap.
2 Likes