Whoa whoa whoa. Different anon but I could actually use your new reshade in 3.0.8? :o that would be everything!
Sure. The best way to do it would be to backup your 3.0.8 shaders (just rename the folder to something different, you can leave it where it is - maybe to reshade-shaders-308), and download the 3.4.1 shaders and put them in your Bin folder (and then follow the rest of my install instructions, wrt quint and my replacement/extra shaders.
You can try it with the 3.0.8 shaders anyway but if there are any little differences in how they’re written it might mean something doesn’t quite look as it should (but like I said the only real difference I can think of is with the rewritten mxao shader — I made Hazy Days and Blueberryade with 3.0.8 and upgraded to 3.4.1 and all I had to do was tweak mxao, the rest looked identical).
ReShade the tool and individual shaders are different things that work together, created by different people. A good rule of thumb is that as long as you stay within the same major version (so, any 3.x version, or any 4.x version) the shaders written for one minor revision (let’s say 3.0.8) will work with any other minor revision (for example with 3.4.1).
Nothing major is happening to ReShade the tool during minor revisions, just bug fixes and the odd feature update. The big changes happen between major revisions — the change from 2 to 3 was massive - the entire language and directory structure was rewritten; the change from 3 to 4 was less of an upheaval, and shaders will in theory work between them but need some adjusting sometimes, so I wouldn’t recommend mixing them unless you know what you’re doing — I’m using some 4.x shaders with 3.4.1 at the moment in my personal build of Clear Bloom, and I had to edit a few things in the shader code to make it work but nothing major, just the way the sliders work when tweaking values.
Shaders, however, get rewritten whenever a shader author fancies. That can be mid-version, or it can coincide with a major version revision of ReShade the tool. Marty McFly in particular frequently makes changes to his shaders, always trying to improve them. Most of the time you won’t notice the difference, but sometimes it’ll be a bigger rewrite. That’s what happened with mxao at some point between 3.0.8 and 3.4.1. He could have not rewritten it and it still would have worked with 3.4.1. Or he could have rewritten it while we were on version 3.0.6 and it would have worked just as it does in 3.4.1. The ReShade version is immaterial because all 3.x versions work the same in terms of shader language and implementation.
The problems came when people were making presets with 3.0.8, updating to 3.4.1 and noticing that mxao didn’t look the same anymore. That wasn’t because of anything fundamental to ReShade, but because Marty rewrote mxao, which he could have done anytime, it just happened to be then. I think people’s unfamiliarity with how ReShade actually works led to lots of worry and concern and big statements like “ONLY COMPATIBLE WITH 3.0.8”, which in turn made people who use presets but don’t create them think there was something integral to each version of ReShade the tool that tied a specific preset to it.
Anyway, that’s a lot of words just to say any 3.x shader will work with any 3.x version, and that when it comes to mxao try to stick to the version of the shader the preset used when being created so it’ll look the same, but otherwise just chuck the shaders in and have fun.