20,741
edits
Canvas scenery overlays: Difference between revisions
Jump to navigation
Jump to search
→Canvas Integration
m (→Canvas Integration: pm preservation ...) |
|||
| Line 126: | Line 126: | ||
== Canvas Integration == | == Canvas Integration == | ||
it does make sense to delegate as much power, and flexibility, to fgdata space (effects, shaders) as possible - the Canvas system would just seem like one of the most obvious candidates to be extended to support geo-referenced placements and let its textures to be used in conjunction with various effects and shaders, as both, the input buffer but also the output buffer. | |||
we are already able to create a texture representation of arbitrary airport features like runways, taxiways etc - even in Nasal/Canvas space using a handful of APIs (navdb), which works using the Canvas::Map element to project lat/lon tuples of arbitrary Canvas::Path segments to the texture<ref>{{cite web | we are already able to create a texture representation of arbitrary airport features like runways, taxiways etc - even in Nasal/Canvas space using a handful of APIs (navdb), which works using the Canvas::Map element to project lat/lon tuples of arbitrary Canvas::Path segments to the texture<ref>{{cite web | ||
|url = https://forum.flightgear.org/viewtopic.php?p=287432#p287432 | |url = https://forum.flightgear.org/viewtopic.php?p=287432#p287432 | ||