20,741
edits
m (→Investigation: first reported back in 2017 ...) |
|||
Line 29: | Line 29: | ||
== Investigation == | == Investigation == | ||
{{Note|As a workaround, using a canvas for this is actually not that bad - it eats some memory equal to the size of the canvas (so make it as small as possible) but in terms of performance, it will end up about the same. <ref>https://sourceforge.net/p/flightgear/mailman/message/36113197/</ref> To be clear it’s 100% a bug that can be fixed, just that given the effort to fix it, I’d recommend going with the canvas solution instead.<ref>https://sourceforge.net/p/flightgear/mailman/message/36113508/</ref> }} | {{Note|As a workaround, using a canvas for this is actually not that bad - it eats some memory equal to the size of the canvas (so make it as small as possible) but in terms of performance, it will end up about the same. <ref>https://sourceforge.net/p/flightgear/mailman/message/36113197/</ref> To be clear it’s 100% a bug that can be fixed, just that given the effort to fix it, I’d recommend going with the canvas solution instead.<ref>https://sourceforge.net/p/flightgear/mailman/message/36113508/</ref> | ||
For the nitty-gritty details, see: https://sourceforge.net/p/flightgear/mailman/message/36240313/ }} | |||
At first glance looks as if FG would need to override those shaders with custom ones, to replicate the material animation used in the fixed pipeline.<ref>https://sourceforge.net/p/flightgear/mailman/message/36116856/</ref> | At first glance looks as if FG would need to override those shaders with custom ones, to replicate the material animation used in the fixed pipeline.<ref>https://sourceforge.net/p/flightgear/mailman/message/36116856/</ref> |