I’m a huge fan of the raytracing option and I use it every time I can to enhance my results. However there is something annoying I notice while using it : there is no distinction between viewport and renderer as we can find in most commercial raytracing tools like blender.
It comes to a problem when I want to generate screenshot, it takes an incredably long time to juste save the image (Paraview has first to generate the image, when done I can click on savescreenshot and there it also lasts forever to actually save the image, like if Paraview is rendering again a second time my image…). Naturally, I want a high number of rays per pixel in order to have a good quality BUT I don’t need a good quality in the viewport (low quality there is enough to check that everything’s alright), as it can considerably slow down the performance of the computer. Blender, for example, provides the possibility to independantly set the number of rays (among others) for the display in the viewport and the one in the renderer (ie when saving screenshot etc). Would it be possible to add such an option in Paraview? This could really enhance the users experience when generating the final render of results.
Indeed switching to pvbatch after I preset my view in the GUI is the workaround I found too. It’s convenient when I know I’ll have repetitive images to generate, less when it’s just a one shot. Also considering the fact that the save state in python format does not generate some elements, like the import of material library or texture files that could have been attached to parts in the GUI. So it requires some tweaks here and there.
It’s also adding a python step in the process that not everyone is familiar with.
I mean I don’t know if it’s an easy modification to bring up in the GUI, but it could benefit to the ones using ray tracing.