Photo dome on mobile phones has a visible seam when useDirectMapping-option is false

The seam can be seen in playground example:

Happens on Android and iPhone devices. Please help :slight_smile:!

EDIT: Here’s a screenshot. You can see the seam almost in the middle of the picture. Taken on a physical mobile device (Android, Huawei Mate 20 Pro)

Any takers on this? Should I make a Github issue instead? :frowning:

Hey sorry somehow I missed your post.

I do not repro on my iphone unfortunately. It seems driver related.
Can you tell me which phone precisely are you using? Like OS version, etc…

The seam shows on my desktop pc as well, but it’s smaller. I looked for the cause but couldn’t find it :disappointed:.

I have Intel HD Graphics 630.

What I’ve looked at:

So without directMapping, it sets a reflection texture instead of a diffuse texture. It sets the wrapV to clamp, but not the wrapU, but setting that manually in the PG doesn’t solve it.

I guess this is where it gets the uv coordinates for the reflection?

The seam is right on the outer ends of the texture, so I thought maybe there’s some floating randomness of from which end of the texture to grab a pixel. Could that be? :thinking:

The really weird thing is that I cannot repro on any of my devices :frowning:
Does anyone else can see it on their computer?
Pinging @PirateJC @sebavan @bghgary @syntheticmagus @Drigax @PolygonalSun @thomlucc @Cedric

Tested on my desktop on Firefox and LG V20 phone using Firefox Mobile, but I don’t see the seam either :cry:

Tested on GalaxyS8 Edge and Chrome, my pc using Edge, Chrome and Firefox and I didn’t see the seam

Works for me as well :frowning:

Just tested on an iPhone 8 Plus and I can repro. I see the seam.

Ok I tried:

  • with better precision (reducing maxZ): nope
  • with and without wrapping: nope

I’m afraid yes.

Can you try with a smaller file? just in case the texture is too big and was scaled down

@Deltakosh, I know that I’m a bit late to the party but I was unable to repro on both my PC and my phone (Pixel 3)

1 Like

Hi everyone and thank you for trying to figure this out! :heart:
So far I’ve managed to reproduce this with at least:

  • Huawei Mate20 Pro (tested with Chrome and Firefox)
  • iPhone SE (tested with Safari)
  • iPhone XS (tested with Safari)
  • Samsung Galaxy S10+ (tested with Chrome and Firefox)

Would be nice to have a fix for this, trying to push Babylonjs into our project since I personally love it :slight_smile:

Found the issue lying inside some drivers :frowning:

The fix will be in the next build shortly