I’m saving the shader presets for a certain core and then, when I create another preset, it frequently erases the previous one and replaces it with the current shader preset I’m saving, replacing even all the particular shader presets I’ve made for each game with that preset. This is so strange.
2 Likes
Sounds like your game presets are using the simple preset feature and referencing your core preset. When you change the core preset it will carry through.
I think there is something broken with your workflow but you could just turn off simple presets.
Of course this is just a guess. I would need to look at your presets to make sure.
1 Like
I’ve seen something like this occur if I save a simple preset, then change something then overwrite that saved preset it ends up like a messed up full preset. Doesn’t happen if I change the name.
I’ve also seen some exciting stuff take place when I accidentally typed a / in a preset filename and RetroArch saved it but Windows could no longer properly recognize the file. Not even to delete it. I was able to delete it using 7Zip file manager though.
1 Like
That doesn’t sound at all like what the OP said was happening. 
He said his preset was overwritten and so were all his game presets.
BTW. I just loaded a preset, made a few changes, saved a new preset, loaded it, made a few changes, and saved it with the same name. It worked exactly as it should.
If you find a repeatable bug though, you should open an issue.
This does sound like an issue that should be raised. I would assume if you used a special character in a filename it would either not save it, throw an error, or just plain crash.
1 Like
Yes, I agree. Do you want to attempt to reproduce this one and see for yourself?
I also attempted to repeat this behaviour just now and it didn’t happen. It happened about a month or 2 ago though and it did have something to do with overwriting a preset and then opening that preset and seeing what looks as if the previously simple preset had now become a full preset. Since then I have avoided directly overwriting presets from within RetroArch. I instead save my changes to a new preset and manually update my existing ones using notepad.
Oh, I just thought that my issue matched the general topic description of incorrect saving of shader presets.
There are some checks in place to avoid things like self referencing. If one of the checks is triggered, the system will save a full preset.
The simple preset feature was never intended for actual shader development. Only modifying existing presets.
You’ll notice in the Guest thread, (And the “Please show off what CRT shaders can do!” thread.) that the shaders posted are usually full presets.
In any case. For both development, and some workflows, the full preset can be used.
1 Like
Seems to have stopped now that I deleted the very first preset I saved. When I did that, the other presets I did from that one got broken.
3 Likes