scope_factor settings applied to disabled shader scope AGAIN

[donizettilorenzo]

In some later changelogs

"Fixed the bug where scope_factor settings were applied to disabled shader scopes or scopes without defined radius for shader effect"

But with the lastest version the bug is here again. I disable the support for SSS (i'm using it) within ACM to disable the shader but scope_factor doesn't "reset" to 1.

[themrdemonized]

it doesnt matter what the console variable is if shader scopes are disabled

[donizettilorenzo]

But the problem is that the script is still running.

[donizettilorenzo]

See this sequence with r__fakescope set to ZERO (scopes disabled in ACM\SSS)

https://i.postimg.cc/7ZBX7cHc/0.jpg https://i.postimg.cc/gjD3pXr5/1.jpg https://i.postimg.cc/1tDpWYSy/2.jpg https://i.postimg.cc/yNMmyCwf/3.jpg

As you can see the script is running nonetheless.....

[themrdemonized]

to disable shader scopes use sds_enable 0

[donizettilorenzo]

Maybe it's a good thing to add 2 entries to ACM menu options, one for compatibility with SSS - as now with r__fakescope - and one to enable/disable the main script!

[themrdemonized]

you can forward the issue to SSS creator