Make sure you select the "Feature request" template. It's not the purpose of these release candidates, but. Nevertheless, it might be helpful to know whether the bug was already present in former releases. Therefore it is important that testers always use the latest (development) version. With that in mind it's very plausible that the bug has been fixed already. FlightGear is under constant development and bugs are fixed almost daily. I found a bug in an older version of FlightGear. In that case, please report it at our bug tracker and include a link to the forum topic in your report. If they succeed, it's likely that it is a real bug. Other testers will try to replicate "your" bug. Try to post as much detail as you can (screenshot, system specs (OS, graphics card), full commandline etc.). Please open a topic in our special "Release candidates" subforum. I think I found a bug, but I'm not sure yet. Thorough testing is appreciated, as these aircraft will give new users a first impression of FlightGear. Try opening every menu, click every button and test if all dialogs work as expected.Īircraft in the base package are supposed to be bug-free. Do note that the earlier bugs are reported, the more time we'll have to fix them.Ĭheck the manual for spelling/grammar faults, out of date information. As the actual release is still some time away, bugs found during these tests have a fair chance getting fixed. These are basically complete releases, meant for testing by a large group of people. We've started distributing so called release candidates. You can help us create a release with a minimum number of bugs!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |