Hackathon Proposal: CompositeViewer and Canvas: Difference between revisions

Hackathon Proposal: CompositeViewer and Canvas (view source)

535 bytes added , 16 November 2020

no edit summary

343

edits

@@ Line 29: / Line 29: @@
 * We can't yet change a Canvas View to show a different view, e.g. swap between tail-camera and gear-camera. The underlying CompositeViewer has full support for destroying and creating new views, and Canvas supports adding/removing elements, so hopefully this will be relatively easy to address.
 * Frame rates might be significantly affected even if a Canvas View is only showing a small part of the scene.
-* Apparently it should be possible to make a Canvas View show different affects, such as infra-red vision.
+* Apparently it should be possible to make a Canvas View show different affects, such as infra-red vision or artificial terrain. The implementation internally uses a Compositor instance to manage the view's rendering pipeline, so it is possible to completely change the Effects and shaders that the view uses.
+* Canvas cameras being in the scene graph is a problem in the long run and should be revisited. The scene graph cameras are being rendered for each slave camera present in the rendering pipeline (i.e. each Compositor render pass), so there are definitely other motivations to make this happen separate from this particular proposal.
 |summary=[[CompositeViewer Support]] already allows us to create multiple top-level windows showing different views of the same scenery.