That looks like a vertical line bug. Not a checkerboard one.
I don’t mind to share it, but I need to know how to share the short preset. I’m not able to do it yet. I’ve got the simple preset saving on. But can’t find where the file saves. If I save it with the name I want, It saves with the long preset…
These files save under Retroarch/config
Hmm, this is weird, it’s supposed to save a simple preset as well
Inside Retroarch/config, what I see folders of the games and cores, with it’s own slangp. But if I open them with notepad, it comes a long list… If I save them by a custom name, it saves in retroarch shaders folder…
Can you go to your shaders/save
page and take a screenshot so I can see what it looks like?
Ok. Right now I’m at work, so when I arrive tonight at home, I’ll do it ASAP…
Cool, no hurry whenever is convenient
My settings haven’t changed at all but I updated to your latest release. I’m getting the “failed to load shader” error on any core I use. Any ideas?
You have to go to Online Updater and Update Slang Shaders.
Actually I meant a screenshot of the save page inside Retroarch
I have a very strong feeling that part of @RetroGames4K’s issue is that he might have been saving presets with the same name and overwriting them.
I’ve run into similar issues in the past when (accidentally) not saving as a new filename when updating and modifying my presets.
I try to always save as a new filename to avoid this.
Yes I think this is very likely.
There is a bug that sometimes saving over the same file that it thinks it will create a cyclical dependency of references, and therefore saves a full preset to avoid saving a preset which can’t be loaded.
@RetroGames4K I would suggest to do as @Cyber has suggested save a preset with a new name each time, or keep saving a per game preset until you are happy with it then copy it somewhere else and change the reference path.
Ok. I’ll try that. Sorry for my ignorance, but what is the reference path? The folder paths are by default, and shall I better save as Game config instead of custom name?
Either should work, by the reference path I mean the line of text in the. slangp file which starts with #reference
which leads to the original Mega_Bezel preset loaded
The reference path is the folder that contains the previous preset in the chain of presets. Simple Presets creates a chain of presets. It should be the first line that begins with reference in a shader preset file.
If you save as a Game Preset, Core Preset or Directory Preset you shouldn’t run into the same problem when updating your preset settings (aka shader parameters).
You can use Custom names you know, you just have to be very careful not to use the same name as an existing shader preset in the Shader Folder. If unsure, click on Load first and once you see a file with the name you want to use, don’t try to save a new update or preset with that same name.
You can probably change it by adding a number to the end or something.
When you’re finished all of your editing and tweaking you can then copy all of your settings into a new file of any name you choose in another folder.
Ok. I erased the config for mame, and started again from zero. But when I save the preset for the game, Still saves a long list… Sorry guys, I only can share parameters with long list. I still can’t make it, I don’t know why.
I tried with this game starting from zero, I want to share this with you…
This sounds overly complicated.
There may be a bug that rears it’s head once in a very long while, I can’t say.
But I save to “shaders/temp.slangp” many, many, many times as a regular part of development, without ever deleting it, and I never have an issue. I also load files in the shaders folder, make changes, and then save with the same name.
I have done both literally “hundreds” of times and have never had any issues.
I wonder if any if the files in his root shaders folder would be considered “Content Directory” presets if they were located in the core config folder. (i.e. have the same name as a ROM folder.
@RetroGames4K Try saving your preset using some strange name… like “donkey”, just to see what happens.
I suppose there could be some stray config file that is messing with things as well. Maybe try renaming your reotroarch.cfg and config folder temporarily.