Hackathon Proposal: CompositeViewer and Canvas: Difference between revisions

Hackathon Proposal: CompositeViewer and Canvas (view source)

70 bytes added , 30 August 2021

m

no edit summary

20,741

edits

@@ Line 48: / Line 48: @@
 * 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 effects, 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: [[Post FlightGear  2020.2 LTS changes#Canvas]] {{Done}} (08/2021)
+* 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: [[Post FlightGear  2020.2 LTS changes#Canvas]] {{Fixed since|repo=flightgear|commit=83b0a3}} {{Fixed since|repo=simgear|commit=a97e14}}
 |summary=[[CompositeViewer Support]] already allows us to create multiple top-level windows showing different views of the same scenery.