Canvas Map API: Difference between revisions

Jump to navigation Jump to search
m (no longer wip)
Line 36: Line 36:
{{cquote|I'm thinking about using a separate canvas for each symbol so that every instance of it is just a textured quad. For efficiency reasons it would be good to draw all symbols to a single canvas/texture and put all quads into a single node. So probably I'll add a new element type for putting quads into a single element which are all rendered at once. Maybe we can even use a geometry shader to just copy the positions to the GPU and generate the full quads with the shader. Ideas and suggestions are always welcome<ref>{{cite web |url=http://forum.flightgear.org/viewtopic.php?f=71&t=17625#p166894 |title=Using a canvas map in the GUI|author=TheTom |date=Wed Sep 19, 2012 12:34 pm}}</ref>|TheTom}}
{{cquote|I'm thinking about using a separate canvas for each symbol so that every instance of it is just a textured quad. For efficiency reasons it would be good to draw all symbols to a single canvas/texture and put all quads into a single node. So probably I'll add a new element type for putting quads into a single element which are all rendered at once. Maybe we can even use a geometry shader to just copy the positions to the GPU and generate the full quads with the shader. Ideas and suggestions are always welcome<ref>{{cite web |url=http://forum.flightgear.org/viewtopic.php?f=71&t=17625#p166894 |title=Using a canvas map in the GUI|author=TheTom |date=Wed Sep 19, 2012 12:34 pm}}</ref>|TheTom}}


{{cquote|I will add a new element type to render symbols from a "Cache-Texture" to improve speed of canvasses showing lots of symbols like eg. the navigation display. You will basically be able to set position (maybe rotation) and index of the symbol in the cache-texture and possibly a color for each instance...<ref>{{cite web |url=http://forum.flightgear.org/viewtopic.php?f=71&t=21139&start=60#p193925 |title=How to display Airport Chart?|author=TheTom |date=Tue Nov 12, 2013 9:54 am}}</ref>|TheTom}}


{{cquote| The issue there (at least based on the NavDisplay) is that there's quite high variance in the symbols, e.g. colour changes. For the ND I keep the symbols at greyscale, and colour them based on parameter data (active vs tuned vs inactive for navaids, for example)
{{cquote| The issue there (at least based on the NavDisplay) is that there's quite high variance in the symbols, e.g. colour changes. For the ND I keep the symbols at greyscale, and colour them based on parameter data (active vs tuned vs inactive for navaids, for example)

Navigation menu