20,741
edits
Release plan: Difference between revisions
→2.10
(→2.10) |
(→2.10) |
||
| Line 220: | Line 220: | ||
** 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] | ||
* '''Installer''': | |||
** The installer should be updated to show a warning regarding TerraSync update time [http://flightgear.org/forums/viewtopic.php?f=68&t=18942&p=175779#p175779] | |||
** When Flightgear releases a new version, can the staff create a way for the average computer users to install a new version without doing anything to the old version but still use the terrain files from the older version? [http://flightgear.org/forums/viewtopic.php?f=22&t=18706&p=175762#p175762] | |||
** I believe Fred intentionally chose to use the same registry key from one version to the next. Thus if you install a new version over the top of an existing version it will end up in the same path under C:\<PF> [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39246.html] | |||
* '''FGData related (Base Package)''': | * '''FGData related (Base Package)''': | ||
| Line 228: | Line 234: | ||
** {{Thumbs up}} also, it would apparently make sense to provide tutorials for the default aircraft: "At first startup, I noticed the "Need help? use help->tutorials" message, and because I had no idea how to start up the plane (it would be just plain try and fail, than try something else), I did just that and started some basic tutorials. I wouldn't say going through the tutorials was frustrating, but they were quite boring and I was eager to get in the air as soon as possible." [http://www.flightgear.org/forums/viewtopic.php?f=28&t=16795] (also see [[Release:Aircraft Selection Criteria]]) | ** {{Thumbs up}} also, it would apparently make sense to provide tutorials for the default aircraft: "At first startup, I noticed the "Need help? use help->tutorials" message, and because I had no idea how to start up the plane (it would be just plain try and fail, than try something else), I did just that and started some basic tutorials. I wouldn't say going through the tutorials was frustrating, but they were quite boring and I was eager to get in the air as soon as possible." [http://www.flightgear.org/forums/viewtopic.php?f=28&t=16795] (also see [[Release:Aircraft Selection Criteria]]) | ||
** "I discovered however, that there can be some problems on Linux about the planes (eg. some versions of the L39 Albatros undergoing several improvements lately). The problems can be caused by Linux being case sensitive about file paths (Windows is not), and I suspect, more models could suffer from some developers not knowing that. It's easy to fix if you know about the problem, but it would better be done on the developer side, as you never know if the smoke is just not implemented or missing due to this. Not to mention how lengthy it would be to go through more aircraft..." [http://www.flightgear.org/forums/viewtopic.php?f=28&t=16795] | ** "I discovered however, that there can be some problems on Linux about the planes (eg. some versions of the L39 Albatros undergoing several improvements lately). The problems can be caused by Linux being case sensitive about file paths (Windows is not), and I suspect, more models could suffer from some developers not knowing that. It's easy to fix if you know about the problem, but it would better be done on the developer side, as you never know if the smoke is just not implemented or missing due to this. Not to mention how lengthy it would be to go through more aircraft..." [http://www.flightgear.org/forums/viewtopic.php?f=28&t=16795] | ||
* '''Usability''': | * '''Usability''': | ||