However you will not be able to configure SweetFX 2.0 in realtime as the files are not ported to the new format and do not make use of any UI variable annotation or support using preprocessor items in the UI! In the future when all SweetFX shaders are ported, you can do that, but then you'll have to adapt all config variables from old SweetFX config format to new ReShade ini file format. There might be some compiler warnings (not errors so all is fine for you) because the file system changed or something (at least I get those on GTA V but I also use a deprechated SweetFX 2.0 build). Configure SweetFX as usual, the configs from TheLazy come into the SweetFX folder, everything as usual.
ReShade 3.0 (even unconfigured) will pick up the Sweet.fx in the game directory and a single technique "SweetFX" will be visible (if not, reload). Do not copy over the ReShade.fx because ReShade 3.0 will load both Sweet.fx and ReShade.fx (which in turn loads Sweet.fx and all that behind) and basically applies SweetFX twice and cause major confusion in the Home tab with the settings.
To delete them, delete the "Shaders" and "Textures" folder where you installed ReShade. ReShade 3.0's shader system would technically allow using all of them together but in case you just want to fire up a preset and you're not used to using ReShade in general, this just creates more confusion. In case you already got them ,just delete them.
In case you have SweetFX 2.0 still around on your PC, you can use the build like this (method should also work with the Framework and MasterEffect but I did not test this, feel free to do that on yourself though): Use SweetFX 2.0 with ReShade 3.0 (temporary solution)Īlthough I can understand that crosire wants people to use the newest ReShade version and including old versions will cause people to ignore the update, only distributing the 3.0 build renders all SweetFX configs on useless until all SweetFX shaders are ported to the new repo.
0 kommentar(er)
