20,741
edits
OSGText Issues: Difference between revisions
Jump to navigation
Jump to search
m
→Mapping to Canvas
| Line 105: | Line 105: | ||
The practical next step which might be feasible, and which we’re waiting for, is for someone to prototype some solutions: for example rendering all <text> to a single internal FBO/texture-atlas and then building textured-quads to hold pieces of that texture in the same place as the old osgText nodes; the quads can then get an Effect applied. There’s variations on that approach, some exploration and R&D is needed for sure. <ref>https://sourceforge.net/p/flightgear/mailman/message/37149210/</ref> | The practical next step which might be feasible, and which we’re waiting for, is for someone to prototype some solutions: for example rendering all <text> to a single internal FBO/texture-atlas and then building textured-quads to hold pieces of that texture in the same place as the old osgText nodes; the quads can then get an Effect applied. There’s variations on that approach, some exploration and R&D is needed for sure. <ref>https://sourceforge.net/p/flightgear/mailman/message/37149210/</ref> | ||
In mid-2020, Gaétan Allaert reported that he was still working on the replacement of the 2D panel by canvas.<ref>https://sourceforge.net/p/flightgear/mailman/message/37042351/</ref> | |||
== References == | == References == | ||