Is it possible to have a render window with multiple viewports and have only one vtkRenderer instance that each of the viewports views from a different perspective?
Currently, the only way I have been able to do this is to create many separate vtkRenderers and simultaneously update them all. In PyVista, we have a way to set up many renderers under viewports of arbitrary geometry in a render window (many thanks to @marcomusy), but I’m looking for a way to view a single scene/vtkRenderer from different perspectives to get something that looks like this:
It creates a lot of overhead (mainly on the code side of things) if the scene gets complicated/has many actors in it - if I want to add/remove actors from the scene, I have to make sure that is repeated for all sub plotting renderers.
I suppose I could add hooks so that anytime the “primary” renderer is altered, those changes propagate to the other renderers as well. So my main technical complaint is really that the code to manage that will get messy.
vtkView may be of interest here in terms of helping manage the complexity. Views are responsible for displaying vtkDataRepresentations. Bundling your renderers into a view and passing in a single representation of your data may make managing the complexity easier - ParaView uses views and representations. See vtkPVOrthographicSliceView for an example that uses several renderers to show data from a common representation.
Since you literally want to look at the same scene from different angles, you maybe able to play some tricks. For example, you can render the scene in backbuffer (or offscreen buffers) from each of the sides and then just past those buffers on the side renderers. Thus, the side renderers are simply images and don’t really have the full scene and are not interactive. You just need to make sure you update them whenever the active scene changes.
@utkarshayachit, what you describe is exactly what I want! No need to interact with those 3 plots to the right so static images would work well.
I’m not sure I’m familiar with this task, how exactly would that be implemented? Would I have a hook that takes those three screenshots anytime the renderer is modified or at a specified time interval? How would I do this without making the camera go wild in the “primary” scene?
it’s definitely non-trivial code, but something like the following is a start.
you’ll still have multiple renderers. the interactive scene is one render while the others only have the Image actor (or whatever people tend to use to show a 2D image data – I can’t remember of the top of my head)
After the scene has been setup (or changed), simply capture the window 3 times changing camera appropriately for each of the side views into a vtkImageData using vtkWindowToImageFilter. Make sure it renders in offscreen or backbuffer. Since the window has the side renderers too, you may want to extract a subset from the generated images using vtkExtractVOI.
Now pass these 3 images to the the 3 side renderers’ actors.
Next stage would be to see how the back and forth from GPU to CPU to GPU can be avoided for the side renderers, but this should get things going.
Ah that’s very clear, thanks @utkarshayachit! I think I can handle all of that in PyVista, however capturing the 3 screenshots of the primary renderer off screen still seems a bit confusing.
Would I basically perform the following workflow:
Save the current camera position in the primary renderer
Ensure the vtkRenderWindow is set to off screen rendering .SetOffScreenRendering(True)
for each of the camera positions I want, change to that camera position, take a screenshot, add that screenshot to the its static renderer and repeat
Reset the primary renderer to the original camera location
Reset offscreen rendering to False (or its original state)
For the most part, you’re correct; .SetOffScreenRendering(True) may be unnecessary though; I think vtkWindowToImageFilter has API to tell is render to back buffer, which should avoid showing the results onscreen and thus will be faster than using offscreen buffers. In otherwords, there are options there, so just bear that in mind.
Would it not be simpler to add a root vtkAssembly to each vtkRenderer and then just manage adding/remove actors (AddPart/RemovePart) from that one assembly? That would eliminate the synchronization issue. You can handle nested actors this way too. https://vtk.org/doc/nightly/html/classvtkAssembly.html
