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

Multi volume #3133

Draft
wants to merge 12 commits into
base: master
Choose a base branch
from
Draft

Multi volume #3133

wants to merge 12 commits into from

Conversation

bruyeret
Copy link
Contributor

@bruyeret bruyeret commented Oct 1, 2024

This PR adds support for multi volume.
It is not intended to be merged, as the shader takes too much time to compile on some systems (e.g. Windows + NVidia + Chrome).
It gives an overview of how it can be done one wants to add multi volume support to vtk.js.

See Examples/Volume/VolumeMapperLightAndShadow/index.js for an example that uses multiple volumes.

See #3132 for the PR that is based on this PR, that adds multi component

These functions used a `getInput` method that doesn't exist
It is not a breaking change as these functions instantly crash when called
The ImageSlice actor already used a more concise code.
Do the same for the base Actor and and Volume actor.
The prop3D has three children that were redefining `getBounds` in the same way.
Move the definition of `getBounds` in the prop3D.
Update typescript accordingly.
BREAKING CHANGE: Move vtkVolumeMapper's properties related to rendering in vtkVolumeProperty.
Add a clear error message for these widely used methods.
This is part of the MultiVolumeMapper feature.
This work is part of the MultiVolumeMapper feature
Fix the getVolumes function which didn't return an array
Instead of comparing a big state that take all actor properties into account,
compare the mtime of the actor as it takes properties into account
Support multiple images as input
Shader compilation is too long
Even longer on Windows + NVidia
Use clang-reformat for a uniform styling of shader
@bruyeret bruyeret requested a review from finetjul October 1, 2024 17:03
@finetjul
Copy link
Member

It is to be noted that #3132 has various fixes that are not in 3133.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants