Missing MSAA 4x and too low minScale value on DynamicResolution about sceneview-android HOT 5 CLOSED

@Veerarma The sample viewer is part of https://github.com/google/filament . It's included in the releases for desktop platforms.

from sceneview-android.

Here is a picture of the same Punto model loaded into the sample Filament viewer

.
As discussed with grassydragon it might be a mipmapping issue not anti-aliasing.

from sceneview-android.

After some more investigation I could reconstruct similar artefacts on the sample-gltf-viewer.
Those are the settings on the sample-gltf-viewer

And this is the resulting scene

The appearence of the scene changed the most when Dynamic Resolution was turned on. And below a minScale of about 0.5 the effect is getting quite noticeable espacially when MSAA 4x is turned off as well.

So it might be a combination of MSAA 4x beeing turned off and Dynamic Resolution turned on with minScale too low.

from sceneview-android.

var view = sceneView.renderer.filamentView
view.renderQuality = view.renderQuality.apply {
  hdrColorBuffer = View.QualityLevel.MEDIUM
}

view.dynamicResolutionOptions = view.dynamicResolutionOptions.apply {
  enabled = true
  minScale = 0.7f
  maxScale = 0.8f
}

view.multiSampleAntiAliasingOptions = view.multiSampleAntiAliasingOptions.apply {
  enabled = true
  sampleCount = 4
}

view.antiAliasing = View.AntiAliasing.FXAA

It turned out the issues was that the default settings of the filamentView were applied and the have MSAA disabled and dynamic screen resolution turned on with some minScale and maxScale values applied by default. The above code makes it possible to access some of the render settings. But things might change with RIP Renderer (?)

from sceneview-android.

Hi!,
where I can find this sample-gltf-viewer?

from sceneview-android.