FlightGear Newsletter May 2021: Difference between revisions

Jump to navigation Jump to search
m
Line 40: Line 40:
Anyway, Fernando tested it and it looks fine to him. If someone who is more used to using osgText can report if the fix was successful and the text looks exactly the same as before, it would be greatly appreciated.<ref>https://sourceforge.net/p/flightgear/mailman/message/37282835/</ref>
Anyway, Fernando tested it and it looks fine to him. If someone who is more used to using osgText can report if the fix was successful and the text looks exactly the same as before, it would be greatly appreciated.<ref>https://sourceforge.net/p/flightgear/mailman/message/37282835/</ref>


Please report back via the developers mailing list and/or the issue tracker.
It is vital that people report back if this fix works for them or not, since the osgText issue has been preventing us from adopting {OSG 3.6, and OSG 3.6 can be considered a prerequisite for some other core development efforts, namely [[WS30]], [[Compositor]] and [[CompositeViewer Support]] - furthermore, once we can safely require OSG 3.6, it is also much more likely that we'll get support for [[Hackathon Proposal: CompositeViewer and Canvas|Canvas Cameras]] (for features like tail cams, rear view mirrors, shuttle RMS arm etc).
 
Thus, please report back via the developers mailing list and/or the issue tracker.


== In the hangar ==
== In the hangar ==

Navigation menu