… Otherwise, if you keep your shaders outside of the RetroArch root folder (as I do) you may encounter relative path issues.
I notice that at least some files have the correct relative path setup, though, such as:
bezel\Mega_Bezel\Presets\Variations\Dual-Screen-3DS__MBZ__2__STANDARD__LCD-GRID.slangp
@HyperspaceMadness: I’ve been following this thread and Duimon’s for a while now. I wanted to say thank you for all the effort you’ve put into this incredible shader! It’s now the default for all of my Retroarch cores. Hard to describe what a difference it makes!
Thanks! It’s still going in part because of the feedback that people are using and enjoying it!
So this is something that I have gone back and forth on and I’ve settled on the following:
Presets in Base_CRT_Presets (Which are the full base presets which define all the passes) use relative paths for all the shaders textures. Relative paths are used since this is the only place these base presets should live, and it also supports someone who puts their shaders folder somewhere else.
Presets in Variations (These are Simple Presets which have the #reference line in them) use absolute paths, e.g. :/shaders/shaders_slang… This is so that they can be copied anywhere else and edited by the user and they will still work.
Basically we are faced with the decision of if the presets should be relocatable, or the entire Mega_Bezel should be relocatable (But this means all the presets must be stored under here and they are not re-locatable without changing the paths inside them)
So in the end I opted for making the presets relocatable as these are the things which most likely need to be able to be copied and moved so they don’t get mixed up with the Mega Bezel package and maybe deleted when you update the Mega Bezel package. If you are still seeing some presets in variations with relative paths, then they are some that I missed and still need to convert to absolute paths.
What I would suggest if you like to keep your shaders somewhere else, is to do a search and replace after you update your Mega Bezel package to replace the absolute paths with relative paths. You can replace
:/shaders/shaders_slang/bezel/Mega_Bezel/
with
../../
I suggest Visual Studio Code for this as it will let you search and replace through many files very easily, it’s a fantastic code editor and it’s also free
Thank you, my friend, for this detailed explanation and the advice on how to edit filepaths. It is very thoughtful of you.
For what it’s worth - I wondered if it would be best for the HSM shader folder to sit ALONGSIDE the standard RA shaders folder (named, say, ‘shaders_HSM’). That way all HSM shader file include declerations can be set as relative paths. Advantages of this approach would be:
All HSM shaders are portable. only requirement is to have default RA shaders folder alongside it.
RetroArch’s in-built asset update process won’t be in danger of overwriting / deleting HSM files.
RA installer won’t overwrite HSM assets.
… I am sure there are drawbacks to this approach, but I figure it might give you some food for thought
Here’s a sneak peak of the screen edge curvature I’m working on over here with almost no screen curvature, so even with strong scanlines I don’t see any moire
I’ve had a great deal of fun the last few days getting used to this incredible shader pack. I have some questions I would like to run by you good people.
Is possible to disable the “Mega Bezel” splash screen that appears when I launch a DS preset shader? Please do not take this question as a form of ingratitude x
Is it possible to to alter the gap size between the two screens when running a DS shader? I use the wonderful MelonDS core which, sadly, does not include a core option to tweak gap size. It would be great to see a HSM preset that only adjusts the screen locations (i.e. no bezel). I think that would be very powerful. I must admit - I could not see how to make this change as I went through the shader scripts.
Over the last 2 days I’ve seen some lovely screenshots of a dark red 3DS using HSM shaders in this forum thread… @Duimon 's work?. Looks ace! Is this preset and border graphic available, or is it in development?
Yup, it’s made to be disabled if desired, it’s down nearer the bottom of the parameter list, the parameter is called
[ INTRO SEQUENCE ]____________________
Show Intro - OFF | When Content Loads | Repeat
Set this to 0 to disable it. You can also put in your own graphics if desired. It currently needs a fix when dealing with dual screen presets, it stretches over both screens when it should probably only go on the first screen, I will probably fix this soonish.
Yes I’ll add one like this, it will be a BASIC-BORDER version so will run the fastest it can.
Yup, just increase the following value
[ DUAL SCREEN ]____________________
Position Offset Between Screens
Yup that’s @duimon’s great work, it’s probably the 3ds with a HSV color offset.
Would you consider adding this one? Classic Trinitron from the 70s, bezel is centered so no extra fiddling with parameters would be required to make it fit.
I would be happy to. I hadn’t planned on adding any more vintage TVs until I finished the rest of the core graphics, but I am flexible and there is no deadline. I’ll push it a little higher up the list.
Any chance on a model number so I can find some more sources?
To get a list of the possible textures you can look at in the base presets near the bottom
Sometime soon I’m going to try to add a feature to retroarch so you can choose a texture through the UI which would be much more user friendly . It’s the next feature I’m going to work on in retroarch. It requires making changes to the UI which is a real pain , so wish me luck!
Impressive how Sony demonstrated superiority in all its TV models.
You can see it on the Trinitron line. Even in the 1970s, TVs always look better developed and flatter than those of other manufacturers.
you adjust the shader parameters to fit the graphic.
, so wish me luck!
