20,741
edits
PUI: Difference between revisions
Jump to navigation
Jump to search
m
→Background: https://forum.flightgear.org/search.php?st=0&sk=t&sd=d&sr=posts&keywords=anthrax+gui
m (→Background: https://sourceforge.net/p/flightgear/codetickets/2213/) |
m (→Background: https://forum.flightgear.org/search.php?st=0&sk=t&sd=d&sr=posts&keywords=anthrax+gui) |
||
| Line 115: | Line 115: | ||
PUI related OpenGL code is particularly infamous for causing rendering artifacts for people on AMD/ATI and Intel hardware (especially in combination with certain fonts/styles and [[Effects|effects]]/[[Shaders|shaders]]), see {{Issue|2213}}. | PUI related OpenGL code is particularly infamous for causing rendering artifacts for people on AMD/ATI and Intel hardware (especially in combination with certain fonts/styles and [[Effects|effects]]/[[Shaders|shaders]]), see {{Issue|2213}}. | ||
PUI is also known to affect rendering performance quite significantly, while also preventing FlightGear from using a more recent version of OpenGL<ref>http://sourceforge.net/p/flightgear/mailman/message/34532040/</ref><ref>http://forum.flightgear.org/viewtopic.php?f=71&t=24046</ref>. | PUI is also known to affect rendering performance quite significantly (see {{search |keywords=anthrax+gui}}), while also preventing FlightGear from using a more recent version of OpenGL<ref>http://sourceforge.net/p/flightgear/mailman/message/34532040/</ref><ref>http://forum.flightgear.org/viewtopic.php?f=71&t=24046</ref>. | ||
However, improving the frame-rate and modernised 3D rendering, can’t be worked on until the PUI code, 2D panels and Shiva are removed, but doing so is a frustrating slow path<ref>{{cite web | However, improving the frame-rate and modernised 3D rendering, can’t be worked on until the PUI code, 2D panels and Shiva are removed, but doing so is a frustrating slow path<ref>{{cite web | ||