Difference between revisions of "Template:AtlasVsCanvasCameras"

From FlightGear wiki
Jump to: navigation, search
m (update)
m
 
Line 1: Line 1:
[[Canvas_Maps#Moving_Maps|Tom originally suggested]] to directly render an orthographic view of the scenery/terrain to the canvas, thus the atlas-based approach should also work using a custom [[Canvas View Camera Element]], based on the [[Hackathon Proposal: CompositeViewer and Canvas]] experiments.(see the ideas summarized at [[Canvas Tile Element]]) <noinclude>
+
[[Canvas_Maps#Moving_Maps|Tom originally suggested]] to directly render an orthographic view of the scenery/terrain to the canvas, thus the atlas-based approach should also work using a custom [[Canvas View Camera Element]], based on the [[Hackathon Proposal: CompositeViewer and Canvas]] experiments (see the ideas summarized at [[Canvas Tile Element]]). Fernando agreed already that it would be straightforward to apply custom node masks, LOD ranges and even effect schemes per [[Compositor]] instance. <noinclude>
 
{{Informative template|1=
 
{{Informative template|1=
 
__NOTOC__
 
__NOTOC__

Latest revision as of 14:14, 2 December 2020

Tom originally suggested to directly render an orthographic view of the scenery/terrain to the canvas, thus the atlas-based approach should also work using a custom Canvas View Camera Element, based on the Hackathon Proposal: CompositeViewer and Canvas experiments (see the ideas summarized at Canvas Tile Element). Fernando agreed already that it would be straightforward to apply custom node masks, LOD ranges and even effect schemes per Compositor instance.

The following template description is not displayed when the template is inserted in an article.

Goal

This template can be used when mentioning the above in an article.

Usage

{{AtlasVsCanvasCameras}}