VTK issueshttps://gitlab.kitware.com/vtk/vtk/-/issues2022-07-27T09:50:59-04:00https://gitlab.kitware.com/vtk/vtk/-/issues/18615OSPRay volume rendering of vtkImageData doesn't support blanking2022-07-27T09:50:59-04:00Andrew BauerOSPRay volume rendering of vtkImageData doesn't support blankingWhen volume rendering a `vtkImageData` that has cells blanked (i.e. `vtkGhostType` field data attribute) the cells are still rendered when using OSPRay. This appears to be a deficiency in the OSPRay structured regular volumes API (see ht...When volume rendering a `vtkImageData` that has cells blanked (i.e. `vtkGhostType` field data attribute) the cells are still rendered when using OSPRay. This appears to be a deficiency in the OSPRay structured regular volumes API (see https://www.ospray.org/documentation.html#structured-regular-volume for information and https://github.com/ospray/ospray/issues/531 for the github issue to address the deficiency).
Adding an issue here to note the unexpected behavior and to also track OSPRay development.https://gitlab.kitware.com/vtk/vtk/-/issues/17422vtkOSPRayPass counter-intuitively depends on OpenGL2018-10-24T09:42:52-04:00Sean CurtisvtkOSPRayPass counter-intuitively depends on OpenGLIn the [documentation](https://www.vtk.org/doc/nightly/html/classvtkOSPRayPass.html#details), the `vtkOSPRayPass` is billed as "a render pass that uses OSPRay _instead_ of GL" (emphasis mine). One would deduce from that that making use o...In the [documentation](https://www.vtk.org/doc/nightly/html/classvtkOSPRayPass.html#details), the `vtkOSPRayPass` is billed as "a render pass that uses OSPRay _instead_ of GL" (emphasis mine). One would deduce from that that making use of the OSPRay renderer would put the user beyond issues of OpenGL contexts. That's certainly, philosophically, consistent with the fact that OSPRay comes (ultimately) from Intel and taxes the life out of a computer's CPUs.
However, the reality is quite different. The current implementation of vtkOSPRayRenderPass still relies on the OpenGL machinery to register actors, lights, etc. The implication of that is it makes "offline" rendering impossible (say, via ssh into a server). No available OpenGL context --> no OSPRay rendering.
Making the separation from a purely conceptual "instead" to an implemented "instead" would enable users to use OSPRay in an offline rendering context.https://gitlab.kitware.com/vtk/vtk/-/issues/17334OSPRay scivis renderer draws outside of the hull of unstructured grids2018-10-23T10:32:43-04:00Michael MiglioreOSPRay scivis renderer draws outside of the hull of unstructured gridsWhen there are holes in the bounding box of an unstructured grid, it looks that OSPRay fills space without cell with the color corresponding to value 0 and 100% opacity.
* VTK renderer:
![Screenshot_from_2018-06-07_14-57-12](/uploads...When there are holes in the bounding box of an unstructured grid, it looks that OSPRay fills space without cell with the color corresponding to value 0 and 100% opacity.
* VTK renderer:
![Screenshot_from_2018-06-07_14-57-12](/uploads/0e223a9a73e69089a985df7fd2195c5a/Screenshot_from_2018-06-07_14-57-12.png)
* OSPRay scivis renderer:
![Screenshot_from_2018-06-07_14-56-59](/uploads/60c88ffafea536b4b7629dbd7956965b/Screenshot_from_2018-06-07_14-56-59.png)https://gitlab.kitware.com/vtk/vtk/-/issues/17291ospray sci vis renderer lacks materials2021-08-11T14:43:22-04:00David E. DeMarleospray sci vis renderer lacks materialsmost likely will need some support in ospray
We should expect that materials in scivis will has less fidelity than path tracer, but should be approximations of full versions there.most likely will need some support in ospray
We should expect that materials in scivis will has less fidelity than path tracer, but should be approximations of full versions there.https://gitlab.kitware.com/vtk/vtk/-/issues/17185ospray unstructured volume render limited to tets and float and point aligned...2020-06-26T12:35:00-04:00David E. DeMarleospray unstructured volume render limited to tets and float and point aligned arraysopening it up to other word types should be easy. For any type that ospray doesn't have a match for we should just convert as we send over.
cell aligned data is a little tricker, a cell to point filter type averaging would work
other c...opening it up to other word types should be easy. For any type that ospray doesn't have a match for we should just convert as we send over.
cell aligned data is a little tricker, a cell to point filter type averaging would work
other cell types should eventually be supported by ospray. We could tetrahedralize until then at some cost in both time and memory.David E. DeMarleDavid E. DeMarle