-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSAO seems to be inverted in my scene? #115
Comments
yep, noticed it, too, postprocessing changed how ssao works it seems. i tried to look up what's going on but it seems to go through a major refactor and it's not so easy to figure out what the steps we would have to take are. pmndrs/postprocessing#279 |
Did this work with previous versions of |
hello @vanruesc yes, this came with an npm update, not a patch, a minor feature update. - "postprocessing": "^6.23.3",
+ "postprocessing": "^6.24.0", |
Is there any existing SSAO sandbox I could play around with? |
I ran into the same thing yesterday. Here's a broken version. |
I tracked down the issue to this line:
NormalPass never gets re-enabled and thus never runs.
|
oh my, what a typo :-S that fixed it! thanks a bunch @vanruesc |
Indeed, v2.1.5 fixes it! Thank you so much for the quick action! |
I'm on @react-three/postprocessing 2.1.6 + postprocessing 6.25.0 it seems I have this problem. |
I've updated all the libs to the latest, it's ok! |
So i am kind of out of ideas for what this issue could be. But i am trying to simply implement SSAO in my three fiber scene. Using these settings (and with blendFunction NORMAL) I am able to get this showing:
But the SSAO seems to be inverted and incorrect, if anyone has an idea what i am doing wrong or with what settings i could fix this, i will be eternally grateful!
The text was updated successfully, but these errors were encountered: