SSAO properties not applied in my project

Questions
1

Hello!

I am using the SSAO2 Pipeline but I can’t set properties liek samples and strength on it in my code.

I copied my setup code into this playground: Babylon.js Playground
In the playground this code works. The samples and strengths are set to the correct values.

But in my environment (with a more complex surrounding setup) when I set the samples and strength nothing changes in the effect (also no value change in the inspector).

I am quite at a loss how to even start debugging that.
Any clues?

Thanks!

2

Do you have any console errors?

3

Nope, no error, warnings or other messages. It just does nothing.

4

Would you be able to share the project? Some more information on the way it is built? This could be related to side effects not loaded, but then I would expect some form of a console error, which you are saying are not present.

5

Sadly no.
It’s quite a big project with a bigg-ish build & content pipeline attached.
It’s one of those “Let’s just activate SSAO at the end” type of scenarios :smiley:

6

The best scenarios! and of course it should be working…

Are you using es6? @babylonjs/core?

7

I just found some Babylon warnings! But they don’t seem like a big issue?

[Violation] ‘setTimeout’ handler took 126ms - scene.ts:2303
[Violation] ‘setTimeout’ handler took 126ms - scene.ts:2303
[Violation] ‘load’ handler took 191ms - fileTools.ts:260

8

i doubt these are related

9

Is your SSAO pipeline visible in Inspector?

11

I have actually seen similar behaviour like you describe once in a project of my own , it was user error on my side , creating the ssao more than once I think. then adding it doesnt actually add , as it has one already. Then the changes to your code do nothing ( and dont update the inspector either ) because its not actually pointing to the ssao currently in use in the scene

1 Like
12

Yes it is. This is where i can see that the values are not set.

13

Yea, had something like that happen to me once as well :wink: But sadly not in this case. It’s just instantiated once.

14

Could you check if values are set or not at the end of your code adding

console.log(scene.postProcessRenderPipelineManager)
15

I went home yesterday, today I started the project up again and the values are set correctly. That smells a little bit like some race condition somewhere… I am not doing something fancy with threading or something (at least not to my knowledge). Makes it even harder to find. But thanks so far!

1 Like
16

Are you using latest as there were a few changes on post processes recently cc @Deltakosh as it might be related to async load of shaders ?

1 Like
17

Unfortunately with no repro I cannot help :frowning:

1 Like
18

Did you declare a camera in the 4th parameter?

image
image900×72 6.27 KB

1 Like
19

i had the impression ssao and fxaa were exclusionary at the moment
I think vignettes do the same thing
yall doin somethin special?

20

Yes, we are using the vignette feature. But I guess that was not the problem since the SSAO was applied (just very ugly because of too little samples :D)

21

Yes we did declare a camera as well. Did not change anything.

1 Like