Philip Rideout

I see this same issue with the PreviewView that's used in https://github.com/google/filament/pull/3599

Thanks, I'll take a look next week. One potential issue is the TCP port on the remote UI server, it needs to be released properly (i.e.`~DebugServer()` must be called) otherwise...

This is expected when MSAA is enabled. The glTF spec is ambiguous with respect to ALPHA_TO_COVERAGE: https://github.com/KhronosGroup/glTF-Sample-Models/issues/221

There's nothing to do here on the Filament side. When MSAA is disabled, we "pass" the test. When it's enabled, the rendering is affected by how the browser and GPU...

I don't think we should take any actions until Khronos resolves https://github.com/KhronosGroup/glTF/issues/1668

This bug is 3 yrs old, closing.

To repro, make two changes before building filament: 1) In `gradle.properties`, change`com.google.android.filament.dist-dir` by replacing `release` with `debug`. 2) Change first constructor in `ModelViewer.kt` by passing `Engine.Backend.VULKAN` into Engine constructor.

Duplicate of #5859

I don't think it's possible to programmatically switch Chrome's backend, especially since the GPU process is shared by all tabs. There might some other workaround you could try though, e.g....

I can reproduce this even without using our glTF ubershaders, e.g. the parquet shader ball looks like this. Next I'll try playing with the opt flags.