I may have found a material-oriented bug… using Booleans

Hello there, i may have found some weird meterial bug, using Booleans :

Please have a look there : https://v3d.net/rv7

You can see a test for a swimming pool configurator (after 8-pool tables, i’m going to swimming pools
The arrows are to enlarge the tiles zone, and you can grab the tiles to offset the placement (limited to 50cm X & Y)

To make things doable, i’ve used booleans : i have a large plane that is booleanes / intersect with an hollowed cube, driven with morpehrs in X, -X, Y and -Y.
It works well in USD…

Problem is i would like to use Physical shaders to get AO, and – for no logical reason – the shader is weird : instead of my texture, i get sort of inverted Roughness as diffuse / color texture.
When you move arrows or drag the plane, the texture si changed into a technical bleu squares with small triangles one, then back to the real one, that should look like the one around the water (grey stone)
I’ve double checked quite everything :
– The Physical shader is working, as if i show the plane with it, it shows ok.
– The code is ok as if i use another shader / the same shader in USD material : it works (but the AO, of course)
– The object is ok, juste not showing the right color
– The object does not exists in 3dsmax, it is created using Boolean

And another strange thing : if i deactive AO, then the booleaned object is shown differently.
As if booleans does not work with AO, with Phisucal shader or both…

Here you can find the project / app :
https://e.pcloud.link/publink/show?code=XZsdJeZfK4DoC3TRg4XCd5I90KeommrOK47

Please someone help me.

PS : you can see that when i enter AR (iOS only for now), i swap PHY shaders into USD ones, then back PHY on exit.