20,741
edits
(no wait... I was partly right) |
mNo edit summary |
||
| Line 5: | Line 5: | ||
Most of us enjoy understanding complex problems, and even fixing bugs - but typically a bug that you may encounter may very well never show up for people involved in developing/contributing to FlightGear. | Most of us enjoy understanding complex problems, and even fixing bugs - but typically a bug that you may encounter may very well never show up for people involved in developing/contributing to FlightGear. | ||
FlightGear is developed by volunteers across the globe, who typically will have a single computer with a certain hardware configuration ( | FlightGear is developed by volunteers across the globe, who typically will have a single computer with a certain hardware configuration (sound/graphics card, fixed amount of RAM/VRAM, certain OS/drivers). The FlightGear developer community is fairly small however - so that our new features do not get as much testing as needed to cover the majority of platforms in use by our end-users. Sometimes new features are only really getting tested widely once they're part of a new release, or once they're enabled by default. | ||
So it isn't uncommon that certain features may work well for most people, but some others may no be able to use them. In an open-source project like FlightGear without any funding, we depend on end-users to provide good feedback so that we can identify, troubleshoot and fix such issues. And we're grateful for everybody providing this very feedback. | So it isn't uncommon that certain features may work well for most people, but some others may no be able to use them. In an open-source project like FlightGear without any funding, we depend on end-users to provide good feedback so that we can identify, troubleshoot and fix such issues. And we're grateful for everybody providing this very feedback in a constructive and helpful manner. | ||
Remotely troubleshooting problems is an extremely tedious process however, that gets more tricky because of people's tendency to act in a frustrated and sometimes even disrespectful way when reporting such problems. But please keep in mind that just because FlighGear may not work for you properly, that this doesn't necessarily apply to the majority of people, or that this inevitably means that FlightGear is the culprit or that it's generally a broken piece of software. Very often, such issues are highly setup/system specific, i.e. depend on the type of hardware, operating system, drivers, application settings - and sometimes even other software installed/running locally. | |||
All this is further complicated by the fact that unlike MS FSX, FlightGear is cross-platform software, which means that it needs to run across all supported hardware platforms and operating systems (Windows, Mac OSX, Linux). | |||
Unlike a commercial software project, we're not making any significant profits to actually fund development, do Q&A testing or provide support to end-users. Commercial software companies will typically have dedicated teams testing new features across a huge variety of hardware/OS configuration. FlightGear however, depends on end-users providing good feedback to ensure that FlightGear keeps working for most people. And we also depend on timely feedback, too - given that we're volunteers, we need sufficient time to troubleshoot and understand a bug, but also enough time to fix it. Preferably, several months prior to a release, not just during the few weeks shortly before release. | |||
This is particularly important because the FlightGear developer community has historically shown a tendency to be comprised of "geeks", i.e. people using certain -very powerful- gaming hardware, and Unix-based operating systems like Linux. Thus, support for other operating systems (especially outdated versions) may sometimes suffer a bit in comparison, because new features are seeing more testing on Unix-based operating systems than on Windows unfortunately. | This is particularly important because the FlightGear developer community has historically shown a tendency to be comprised of "geeks", i.e. people using certain -very powerful- gaming hardware, and Unix-based operating systems like Linux. Thus, support for other operating systems (especially outdated Windows versions) may sometimes suffer a bit in comparison, because new features are seeing more testing on Unix-based operating systems than on Windows unfortunately. | ||
While we have been providing a way for end-users to get involved in regularly testing FlightGear pre-releases provided via the [[ | While we have been providing a way for end-users to get involved in regularly testing FlightGear pre-releases provided via the [[FlightGear Build Server]], very few users seem interested in getting involved in this, and even fewer people are actually providing bug reports via the issue tracker unfortunately so far. | ||
This is why you need to be our eyes and ears - we cannot see what you're seeing, and we cannot know what you have done. | This is why you need to be our eyes and ears - we cannot see what you're seeing, and we cannot know what you have done. | ||
| Line 39: | Line 40: | ||
Further reading: | Further reading: | ||
* [[How the FlightGear project works]] | * [[How the FlightGear project works]] | ||
* [[FlightGear and old Hardware]] | |||
* [[Troubleshooting Problems]] | * [[Troubleshooting Problems]] | ||
* [[Requesting Technical Help]] | * [[Requesting Technical Help]] | ||
[[Category:FlightGear]] | [[Category:FlightGear]] | ||