![]() The hope is to make OpenGC/fggc and some related things obsolete, since the same XML+Nasal can be used in the main sim or stand-alone. Which is why you'll currently either need a fairly powerful computer, or use a workaround. While FGPanel is great, it's a separate code base, and as such needs to be maintained separately, it also isn't as flexible - and cannot be scripted or used for glass avionics, it also doesn't support any of the existing hardcoded displays - so it's stricly about 2D panels and static/property-driven transformations.Īt the moment, there are a handful systems/features in FG that need to be disabled manually, and others that cannot be disabled at all. Realistically, it is only feasible to support such use-cases by having a single common backend that knows how to deal with multiple windows, rendering contexts, GPUs or multiple fgfs instances.īasically, FGCanvas is going to be just FlightGear, in a custom startup mode, to make certain features and subsystems optional, so that the runtime footprint is reduced over a conventional full fgfs instance, and computing resources freed. We've been talking about having a FGCanvas mode built right into the fgfs binary at some point, analogous to how FGPanel works - just as an integrated part of the main code base, while not only supporting 2D panels, but also MFD-style cockpits and even GUI elements. Realistically, we could accomplish many things already - and if someone is interested in pursuing this, we can provide a ton of pointers and also help to varying degrees. For the time being, there are 3 core developers working towards this and a number of other contributors willing to help to get this done. Obviously, this assumption is based on the manpower currently available, and people interested in helping with this. However, there are still several things that need to happen for this to become feasible - currently, it seems this is at least another 3-4 releases away (i.e. by implementing a 2D panels parser via Nasa/Canvas. This would then also make FGPanel obsolete, because we're hoping to unify the 2D rendering back-end using Canvas, i.e. However, we're hoping to eventually absorb fgpanel functionality back into fgfs and come up with a special startup mode for running Canvas-based instruments in a standalone "FGCanvas" window, where the majority of subsystems would simply be disabled: a NavDisplay) will require a hard-coded instrument, or Canvas - both of which are unsupported by fgpanel. FGPanel really only supports classic 2D panels that are built using stacked textures.Īnything more sophisticated than that (e.g. Such instruments are also not supported by fgpanel. The majority of "glass" instruments are still hard-coded, i.e. In general, we still have very few Canvas-based instruments. Standalone Canvas Applications (MFD, instruments etc) Again, that would be a way to join forces with other Sim dev communities. Should there maybe be a separate project to build an embeddable GPS navigator with different faces/UIs (and a default standalone front end)? As others have mentioned, a lot of the backend logic is the same, like doing a gradual transition from RNAV to Localiser on intercept to avoid a sudden jolt in the A/P, or calculating a turn past a fly-by waypoint. That crop plane didn't take us far." The passengers were bussed to Norfolk.If we wanted to build a tablet-based emulator ourselves, we could at least join forces with the FSX and X-Plane communities to do it to grow up the pool of talent. ![]() A passenger commented: "Right engine stopped in midair. The aircraft climbed to 3000 feet again, the crew managed to extend the gear and positioned for a second approach to runway 01L completing a safe landing on runway 01L about 30 minutes after departure and vacating the runway. The aircraft positioned for an approach to runway 01L and was on final approach descending through 1500 feet when the crew advised they were going around single engine because the gear didn't want to come down. The aircraft continued the climb to 3000 feet, advised they were still working the checklists and needed to return to runway 19R. A Commutair de Havilland Dash 8-200 on behalf of United, registration N362PH performing flight C5-4979/UA-4979 from Washington Dulles,DC to Norfolk,VA (USA), was in the initial climb out of Dulles' runway 30 when the crew reported an engine failure and requested vectors. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |