20,741
edits
Post FlightGear 2020.2 LTS changes: Difference between revisions
Jump to navigation
Jump to search
m
→Canvas: https://sourceforge.net/p/flightgear/mailman/message/37289641/
m (→Canvas: https://sourceforge.net/p/flightgear/mailman/message/37289641/) |
|||
| Line 82: | Line 82: | ||
=== Canvas === | === Canvas === | ||
{{Caution| we are indeed still adding Canvas cameras to the scene graph, but we should be adding them as slaves to the viewer. We might be using as much as 5 times the amount of VRAM that Canvas actually needs.<ref>https://sourceforge.net/p/flightgear/mailman/message/37289641/</ref>}} | |||
{{See also|Unifying the 2D rendering backend via canvas}} | {{See also|Unifying the 2D rendering backend via canvas}} | ||
* Note that the canvas currently assumes render-to-texture, but for the GUI I'm not sure that's actually desirable - simply a separate camera per GUI window may be sufficient. Since the camera already arranges everything beneath the RTT camera this should be fairly minor change, if it's desirable.(Saves some memory, makes re-sizing GUI windows a little easier, might make clipping or other state management less efficient in the main GUI camera ... but probably not)<ref>https://sourceforge.net/p/flightgear/mailman/message/29608899/</ref> | * Note that the canvas currently assumes render-to-texture, but for the GUI I'm not sure that's actually desirable - simply a separate camera per GUI window may be sufficient. Since the camera already arranges everything beneath the RTT camera this should be fairly minor change, if it's desirable.(Saves some memory, makes re-sizing GUI windows a little easier, might make clipping or other state management less efficient in the main GUI camera ... but probably not)<ref>https://sourceforge.net/p/flightgear/mailman/message/29608899/</ref> | ||