SC Post Effects Documentation

SC Post Effects
Version: 2.3.8
Review

4.1.Update guide #

General

Important! Make sure the console is clear of any C# compile errors before importing! Otherwise the (updated) scripts will fail to compile as well, disrupting the installation/update process.

When importing the update, the installer window will be prompted. Should it not, you can always use the Window->SC Post Effects menu option.

It’s possible some scripts are now throwing console errors, due to script changes this particular update.

Click the button to unpack the updated scripts. After which, any errors will be cleared and the asset is up-to-date

Manually unpacking the package found in the “Install” folder is not recommended! In some cases, such as major updates, the update process involves other (automated) steps that would be skipped this way!

From 2.2.0 to 2.3.0+ (Dec 2022)

When importing the update, the installer window will be prompted.

After clicking the “Update effect scripts” button, a dialog will pop up:

An automated process will be run that moves all the asset’s shaders out of any “Resources” folders (and deletes the, now empty, folders too).

The process of unpacking the (updated) scripts and shaders will simply continue after closing this dialog.

The console can simply be cleared to remove any shader-related errors, these are no longer relevant!

1.0.2 to 2.0.0+ (May 2020)

To ensures compatibility with future Unity versions, folder structure has been changed. This requires to delete the SC Post Effects folder entirely before importing. Due to many other changes, required for future proofing, all effects will be removed from any profiles.

It’s not recommended to update in production projects.

Yes No Suggest edit
Last updated on January 20, 2023
0 of 0 users found this section helpful
Suggest Edit