20,741
edits
FlightGear Newsletter May 2021: Difference between revisions
Jump to navigation
Jump to search
m
→Development news: https://sourceforge.net/p/flightgear/mailman/message/37282835/
m (→In the hangar: typo) |
m (→Development news: https://sourceforge.net/p/flightgear/mailman/message/37282835/) |
||
| Line 34: | Line 34: | ||
If next works for someone, that is great, but if you want stability, stable FPS and comaptability with older hardware, there is an easy answer: use 2020.3. That's what we recommend for everyone who wants to fly and enjoy flying. <ref>https://sourceforge.net/p/flightgear/codetickets/2560/#5802</ref>}} | If next works for someone, that is great, but if you want stability, stable FPS and comaptability with older hardware, there is an easy answer: use 2020.3. That's what we recommend for everyone who wants to fly and enjoy flying. <ref>https://sourceforge.net/p/flightgear/codetickets/2560/#5802</ref>}} | ||
=== Text animations and OSG 3.6 === | |||
Fernando pushed two commits to simgear and fgdata that should | |||
hopefully fix the white osgText issue under OSG 3.6. Apparently | |||
assigning an Effect to the geode containing the osgText was enough to | |||
get it working. He thought it would conflict with OSG internal shaders, | |||
but it didn't. This might not be the case with the core profile, but has got | |||
a few tricks which should force our shaders to prevail over | |||
OSG's. | |||
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. | |||
== In the hangar == | == In the hangar == | ||