Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improvements from VTK 8.2.0? #51

Closed
dmreagan opened this issue Jan 31, 2019 · 2 comments
Closed

Improvements from VTK 8.2.0? #51

dmreagan opened this issue Jan 31, 2019 · 2 comments
Labels
state: needs check We need to check if this issue is relevant type:Question
Milestone

Comments

@dmreagan
Copy link
Contributor

Kitware has announced the release of VTK 8.2.0. Is there anything FURY should take advantage of?

Relevant bits include:

VTK Python modules have been restructured to support importing specific modules without importing all of VTK. This improves import speeds substantially. To use this, import vtkmodules package instead of vtk.

Added support for testing OpenGL capabilities at run time on windows and falling back to Mesa software rendering (see vtkTestOpenGLVersion.h)

One can now modify or use custom shaders with the GPU volume mapper to tweak final rendering.

Improved the usability of custom volume shaders in vtkOpenGLGPURaycastMapper by allowing to declare and set the value of custom uniform variables through a new class (vtkOpenGLUniforms).

The default method for handling translucent rendering is now a single pass order independent simulated translucency approach which yields much nicer results than the previous alpha blending approach.

The 3D Glyph mapper has been updated and it can now take in four component vectors and better handle rotations.

PolyData based mappers now support multi-texturing

Support for Oculus touch controllers added

The hardware accelerated volume mapper can now assign a special intensity value for voxels in the clipped area. This can be used to generate smooth surface shaded faces at the clipping interface.

The volume mapper can now directly render isosurfaces, saving the time and memory usually reserved to first extract isosurface geometry.

We now have a tone mapping render pass. This is an elegant way to handle scenes like those in the real world that have high luminosity ranges.

@dmreagan dmreagan added state: needs check We need to check if this issue is relevant type:Question labels Jan 31, 2019
@dmreagan
Copy link
Contributor Author

See #116

@skoudoro skoudoro added this to the v0.6.0 milestone Jul 11, 2020
@skoudoro
Copy link
Contributor

After VTK 9 release, closing this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state: needs check We need to check if this issue is relevant type:Question
Projects
None yet
Development

No branches or pull requests

2 participants