I’m thinking about what I need to do to setup a repo playground. In the meantime, here’s the two versions of chrome I see the discrepancy with:
Version 116.0.5845.110 (Official Build) (x86_64) - my 2017 MacBook pro (good)
Version 116.0.5845.110 (Official Build) (arm64) - gf’s 2023 m1 MacBook pro (bad)
Most of the terrain is rendered normally without these weird bumps, but every so often you see the weird bumps. It’s happens every so often when the shaders I’m using use calls to the texture sampler methods in both glsl and wgsl. This happens in both the webgl2.0 engine and the webGPU engine. The assumption here is because the issues are with texture sampling, the openGL texture sampling method is going awry.
It looks like it could be a driver bug…
Have you tried to force WebGL1? Also, does it work in Firefox?
Can you setup the PG please?
I have both M1 pro and a windows PC available so I can have a look at it as well.
Hmm could it be mipmap related?
@Evgeni_Popov @roland @jeremy-coleman apologies for the delay.
I have not been able to repo this issue in a playground despite setting up what I believed to be the relevant parts of our code. At this moment it’s starting to look more like something todo with our usage of
PBRCustomMaterial. If I can confirm in a playground, I’ll post here again but for now all I can say is that there’s some sort of rendering artifact that only shows up on M1 and M2 MPs. It’s really weird, but less generalized than we initially thought. Sorry for the false alert there.
I use an m1 max macbook pro as my primary computer but didn’t notice anything weird yet with any PG (except it’s incredibly fast - LOL) . As you wrote it might be really an issue on your side with the custom material.
If you manage to setup the PG I’ll gladly test it and help to identify the problem.
Have a nice day!