Problem rendering mesh wireframe using OSPRay raycaster with transparent background

BrunoP · October 5, 2021, 1:40pm

Hi,

I have problem when rendering mesh wireframe with transparent background using OSPRay raytracer. If image is rendered with background everything is rendered correctly, problem appears when setting transparent background. Here is an example:

Am I missing some general settings to fix this problem?

Thanks,
All the best,
Bruno

mwestphal · October 5, 2021, 1:54pm

@timothee.chabat

timothee.chabat · October 5, 2021, 2:24pm

No issue here. So you’re exporting your scene in PNG using the Use Transparent Background option, as well as OSPRay raytracer (and not the pathtracer) right ?

Could you please tell your ParaView version ? (and your OSPRay version if you build it yourself)

BrunoP · October 5, 2021, 2:30pm

Hi,

I rendered couple more examples to check.
Wireframe - surface overlay using OSPRay raycaster:

Using OSPRay pathtracer it gets even worse:
Both background mode:

Backplate mode:

BrunoP · October 5, 2021, 2:36pm

Hi timothee,

Yes, I am saving screenshot using transparent background option. As you can artefacts are appearing using both OSPRay raytracer and pathtracer.

I am using Paraview 5.9.1. for mac. I haven’t build it myself.

timothee.chabat · October 5, 2021, 2:49pm

Ok thanks for the precision! Since I cannot reproduce locally could you please write explicit steps to reproduce ? If it works with procedural sources (eg the Sphere source) you could share a state file, else if possible share the dataset you’re showing in your screenshots.

Note that camera position is not shared in state files so if you think it is relevant you can also share it (either write it or export it using the custom viewpoint dialog)

BrunoP · October 5, 2021, 3:54pm

Hi timothee,

Here are state files, camera parameters and renders (both with and without transparent background) for sphere as surface mesh and wireframe.
sphere_example.tar.gz (1.3 MB)

timothee.chabat · October 6, 2021, 7:38am

Thank you for taking the time of producing these files! I can reproduce on 5.9, 5.10 RC1 and master.

This is definitely a bug but I don’t know where it comes from so far, I’ll try to take a look at it when I can. Maybe @Dave_DeMarle has an idea here ?

mwestphal · October 7, 2021, 7:47am

Could you open an issue on gitlab @timothee.chabat ?

BrunoP · October 8, 2021, 8:49pm

Hi,
Thanks, the same artefacts appear in 5.9.0 and 5.9.1, haven’t tried 5.10 release candidate yet. On the other hand 5.8.1 renders it fine.
Could you please let me know when you create gitlab issue so I can track progress on this?

Maybe I should open new topic for this, I came across another bug when rendering textured mesh using ambient occlusion. Missing/transparent pixels present also with increased SSAO number of samples and blurring of ambient occlusion. Here is an example:

I have created state file to reproduce this with wavelet source.
wavelet_example.tar.gz (870.5 KB)
Render of wavelet isosurface using default scivis backend and AO on: