Bureaucrats, checkuser, Administrators
304
edits
Feature Requests / Proposals / Ideas: Difference between revisions
import
(Linked to PDF uploaded to wiki.) |
Hellosimon (talk | contribs) (import) |
||
| Line 184: | Line 184: | ||
* At http://freshmeat.net/projects/installbase/ or more specifically at http://installbase.sourceforge.net/main.shtml there's an open source cross platform GUI installer available that may be an interesting option for creating binary FlightGear installers. The whole thing is based on TK and works with statically precompiled interpreters that serve as stub for an ASCII config file that contains all relevant information for cross platform setups,including a tarball of installation specific files for each platform. The installbase installer is very convenient and works entirely with a very powerful GUI frontend that allows you to set up, test and export installer packages. Given that the final config file is ASCII, it would probably be quite possible to simply put all this into some sort of Makefile, so that the whole package creation could be handled automatically, i.e. by doing something like "make win32-package" or "make macos-package". The [http://installbase.sourceforge.net/screenshots.shtml screenshots] look very convincing. That way, all FlightGear binaries could easily use an identical installer and configuration wizard. | * At http://freshmeat.net/projects/installbase/ or more specifically at http://installbase.sourceforge.net/main.shtml there's an open source cross platform GUI installer available that may be an interesting option for creating binary FlightGear installers. The whole thing is based on TK and works with statically precompiled interpreters that serve as stub for an ASCII config file that contains all relevant information for cross platform setups,including a tarball of installation specific files for each platform. The installbase installer is very convenient and works entirely with a very powerful GUI frontend that allows you to set up, test and export installer packages. Given that the final config file is ASCII, it would probably be quite possible to simply put all this into some sort of Makefile, so that the whole package creation could be handled automatically, i.e. by doing something like "make win32-package" or "make macos-package". The [http://installbase.sourceforge.net/screenshots.shtml screenshots] look very convincing. That way, all FlightGear binaries could easily use an identical installer and configuration wizard. | ||
* Set up a cross compiler version of gcc at flightgear.org to automatically create binary packages (releases) of FlightGear for platforms such as Win32 or MacOS. | * Set up a cross compiler version of gcc at flightgear.org to automatically create binary packages (releases) of FlightGear for platforms such as Win32 or MacOS. | ||
== User Perceived Improvements == | |||
This is meant to provide an overview of things that users perceive as insufficient or simply inconvenient in FG, so that the developers can get an impression of issues that users would like to see eventually addressed in FlightGear. Among others, inspired by- and based on references to discussions posted by Melchior Franz to the developer's mailing list, on 02-11-2006: | |||
* http://digg.com/software/Awesome_Free_Flight_Sim | |||
* http://www.macupdate.com/info.php/id/16997 | |||
* http://happypenguin.org/show?Flight%20Gear%20Flight%20Sim | |||
* http://www.winfuture.de/news,23149.html | |||
* http://nickles.softonic.de/ie/47000/Flightgear | |||
Evaluating the merits of such discussions should eventually enable us to determine which areas in FlightGear need to be specifically addressed in order to make FlightGear appeal to more users. Please feel free to add new entries. | |||
* non-intuitive scenery modification and installation | |||
* non-intuitve aircraft modification and installation | |||
* non-intuitive joystick configuration | |||
* non-intuitive aircraft panel creation (lack of GUI frontend) | |||
* non-integrated startup wizard (requires fgrun) | |||
* lacking performance | |||
* significant startup times | |||
* currently no glass cockpit support | |||
* lacking documentation | |||
* insufficient mac support | |||
* webpage appearance | |||
* FDMs partially not very convincing | |||
* not fully animated 3D models | |||
* insufficient weather modelling and -effects | |||
* multiplayer not yet too playable | |||
* non-standard GUI, not too appealing to many users | |||
* outdated FAQ | |||
* no integrated tutorial/ground school or learning mode | |||
* no realistic helicopter support | |||
* no multi screen support | |||
* airports/runways cannot easily be modified/re-created | |||
* non-configurable approach lighting for runways | |||
* no blade element FDM | |||
* GUI does not yet expose many of FlightGear's features that are available via command line | |||
* no real scenario/adventure support | |||
* no combat support | |||
* hardly realistic scenery-missing/inappropriate textures, objects, landmarks. | |||
* no realistic water modelling | |||
* no ground traffic modelling | |||
* hardly localized UI: GUI, command line, error messages | |||
* no localized help dialogs (basic commands, keys...) | |||
* no Voice ATC | |||
* not very advanced AI ATC | |||
* no moving map directly integrated in FlightGear | |||
* warnings and error messages are only rarely informative | |||
* no flight planning facility integrated/available | |||
* no support for sailgliders, hanggliders - unpowered flight | |||
* no scripted demo flights that users could "play" to see a simple flight (pattern) including landing | |||
* no ATC facilities for real life controllers (VATSIM like) | |||
* does not work well on lower end hardware | |||
* starting FG takes a while and FG seems to have crashed, the window (splash screen) is not redrawn-unresponsive until finally started up | |||
* no water effects for ocean and rivers (waves/streams) | |||
* no support for weight & balance (and fuel) for aircraft | |||
* currenlty not a suitable VFR simulator | |||
* few buildings have proper night textures | |||
* significant initial download (>100MB) - might be a good idea to try to reduce the base package size where possible | |||