![]() labels, buttons, text fields, check boxes, radio buttons), however it is highly portable (using OpenGL) and is known to work pretty well on all platforms supported by FlightGear. Atlas itself uses the same GUI library as FlightGear: PLIB's PUI:, this is a pretty simplistic widget library that contains only very basic controls (i.e. approach evaluation).Depending on the level of usability you envision, you might also want to have some sort of "overview" page, where all configurable properties are directly visible or at least accessible, so this is where some sort of GUI library/toolkit would come in. a "winds" button to configure the winds, a "temperature" button to modify the temperature etc.If you do intend to head towards a instructor station, most instructor stations for professional simulators also feature a profile view, this is something that Atlas does not yet support.So, Atlas might probably benefit from a corresponding vertical profile view in that case, so that the flight path can be depicted with regard to the underlying terrain, which would also add the possibility for instructors to do evaluations based on AGL altitude/terrain height (i.e. via some sort of history buffer) or later on, possibly even map such properties/macros to certain buttons/action, i.e. in order to configure environmental settings (such as winds, temperature, clouds etc.) or in order to change/reset the runway/position, daytime.FlightGear itself also supportes a so called "raw" mode for the specific purpose of automated telnet access, so that you do not have to do any complicated parsing when you set properties in order to fail a piece of equipment such as cockpit instruments, engines, flaps or the navcom.Of course, directly issuing telnet commands manually would probably become somewhat inconvenient for an instructor sooner or later, so you might want to sort of save frequently used properties (i.e. Besides, atlas itself is already written with portability in mind, so it would be straight forward to keep doing so.Basically, the only thing you might immediatley want to add would be an integrated telnet client (this can be accomplished using PLIB's netchat object), so that you can issue commands to FlightGear, i.e. I'm brand new to FlightGear, and>all these ideas seem like great starting points to work from.If you check out Atlas at you will see that it is indeed very well suited to be used as a framework for an instructor/obvserver station, where the mapping aspect is usually one of the more complex ones. taken in/with FlightGear.>Thanks for being so helpful.Those are all great ideas,>especially the mapping aspect, we were kind of envisioning>something like that as well. Screenshots, videos, sound recording etc. Please read the introduction topic for details.ġ87 Topics 2283 Posts Last post by MariuszXC Release candidate testers are encouraged to post their feedback here. Subforums: Aircraft, Scenery, New features, AI Traffic, Weather, Nasal, Spaceflight, Effects and shaders, Canvas, Add-ons, Documentation, Google Summer of Code 11731 Topics 192364 Posts Last post by helijah ![]() In the need for help on anything? We are here to help you. Subforums: Virtual airlines, Air traffic control 1662 Topics 40576 Posts Last post by Mike MillerįlightGear is opensource, so you can be the developer. Find out details of upcoming events, register for competitions, or organize your own tour of a favorite location. Virtual fly-ins, fun flies, competitions, and other group events. Subforums: Installation, Compiling, Hardware, Flying, Multiplayer, Graphics, Interfacing, osgEarth, 3rd Party Repositories, FGRun, FGCom, Atlas, FGx, OpenRadar, ATC-pie 13333 Topics 98449 Posts Last post by unhappytroll There are lots of users and developers to help you out. Subforum: News 575 Topics 7983 Posts Last post by ImDedĪll general support: help on flying, installation, hardware, getting online etc. Questions about the FlightGear organisation, website, wiki etc.
0 Comments
Leave a Reply. |