20,741
edits
OSGText Issues: Difference between revisions
Jump to navigation
Jump to search
m
→Background: update based on recent comments
mNo edit summary |
m (→Background: update based on recent comments) |
||
| Line 42: | Line 42: | ||
The breaking change was introduced with OSG 3.6.5, and was also recently merged into OSG 3.7.<ref>https://sourceforge.net/p/flightgear/mailman/message/36732917/</ref> | The breaking change was introduced with OSG 3.6.5, and was also recently merged into OSG 3.7.<ref>https://sourceforge.net/p/flightgear/mailman/message/36732917/</ref> | ||
== Status == | |||
'''02/2021:''' The issue with needing an osgText replacement so we can move the windows build to OSG 3.6 has not been forgotten, but neither James nor Stuart are looking at it right now.<ref>https://sourceforge.net/p/flightgear/mailman/message/37216308/</ref> | |||
For the time being, this has not been addressed: James would be happy to be wrong about that. But hasn't seen any code change which would fix it, and indeed, he does not believe a simple ‘change X to do Y’ fix is actually directly feasible. (Because fundamentally you can’t use two shaders programs together, and osgText now uses shaders)<ref>https://sourceforge.net/p/flightgear/mailman/message/37208161/</ref> | |||
As to upgrading to OSG 3.6, we'd sooner not do that without a clear way forward about osgText support. It doesn’t need to be perfect but at least some idea of a timeline. If we have a solution we can jump to OSG 3.6.n without hesitation.<ref>https://sourceforge.net/p/flightgear/mailman/message/37208145/</ref> | |||
== Background == | == Background == | ||