20,741
edits
Release plan: Difference between revisions
→2.10
(→2.10) |
(→2.10) |
||
| Line 221: | Line 221: | ||
** modified shaders should be tested with other shader-related features to prevent breakage [http://flightgear.org/forums/viewtopic.php?f=68&t=18924#p175583] (there might be a way to automate this a litle by catching GLSL compiler errors?) | ** modified shaders should be tested with other shader-related features to prevent breakage [http://flightgear.org/forums/viewtopic.php?f=68&t=18924#p175583] (there might be a way to automate this a litle by catching GLSL compiler errors?) | ||
** to address all the intel GPU related issues, we may want to show an info dialog on computers where /sim/rendering/gl-vendor contains "intel" as a substring and provide an option to disable all shaders [http://flightgear.org/forums/viewtopic.php?f=37&t=18050&p=175774#p175774] | ** to address all the intel GPU related issues, we may want to show an info dialog on computers where /sim/rendering/gl-vendor contains "intel" as a substring and provide an option to disable all shaders [http://flightgear.org/forums/viewtopic.php?f=37&t=18050&p=175774#p175774] | ||
** we probably need a separate article detailing GLSL coding requirements to ensure that portable constructs are used [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39278.html] so that problematic shaders are not just identified at the end of the release cycle | |||
* '''Installer''': | * '''Installer''': | ||