20,741
edits
Canvas news: Difference between revisions
Jump to navigation
Jump to search
m
→Replacing PUI: https://sourceforge.net/p/flightgear/mailman/message/37720688/
m (→Replacing PUI) |
m (→Replacing PUI: https://sourceforge.net/p/flightgear/mailman/message/37720688/) |
||
| Line 6: | Line 6: | ||
== 2022 == | == 2022 == | ||
=== Releasing Canvas textures === | |||
What we’d ideally want is a C++ change so that hidden canvases release their texture memory : it’s created the first time the canvas is rendered, which is why the memory is fine until you actually show them. | |||
200MB memory is not great, but the bigger problem is the GPU-side memory : 200MB of VRAM is much more ‘valuable’ for textures than for keeping the backing store of hidden dialogs. So I would definitely say use this feature sparingly, until someone adds some C++ logic to destroy the backing texture for hidden canvas windows.<ref>https://sourceforge.net/p/flightgear/mailman/message/37720688/</ref> | |||
=== Replacing PUI === | === Replacing PUI === | ||
{{See also|PUI#Replacement_status}} | {{See also|PUI#Replacement_status}} | ||