|
From: Wayne B. <kil...@co...> - 2018-09-09 19:34:47
|
FYI: Currently the state overlay only has a default state and so will adapt to whatever you choose in location. If you leave the "on approach" selected, then you will startup with the aircraft configured for an approach. It will keep all setting the same as the last time you shut down the sim as far as variants, unless you startup choosing a new variant. The only thing the state will change is what it takes to put the aircraft in an "on approach" state, ie: flaps position (depending on distance out) carb heat gear down (amphibious) brake off mixture (set per altitude) throttle (depending on distance out) If you use a parking position with "on approach" selected, then you will start at that parking position with the engine running but configured for an approach. If you are in the QT-launchers default or automatic state where there is no location radio button selected but the "on approach" is selecrted then you start on the "default" runway with engine started but configured for an approach. We left the ability to save switch states or not depending on what you choose in the GUI, except the above mentioned "on approach" which has to override some of the saved aircraft-data. So without "on approach" set you will start on either the runway or parking per your last choices in the QT-launcher, the last variant selected and in last state you chose in the sim, either "save switch state" or not. Our team (c172p) still needs to define what we want to use the state overlay feature for and decide how to best arrange saved aircraft-data to meet that end. Wayne On 09/09/2018 12:04 PM, wki...@gm... wrote: > > > FWIW: i just pulled master from the c172p dev repo... selected it in > the launcher and forgot that i normally start with the UFO at 1000 > feet ASL and located over the KRDU control tower... i left the craft > at "default" for the startup scenario... the craft auto-started in the > air (with default craft settings) and i was able to give it fuel to go > around a little bit via keyboard controls and lucky enough to land it > quite nicely in the grass near the airport... i normally use the 180hp > engine and have numerous craft options set but they were apparently > cleaned during this startup... i don't see a version number in the > aircraft-data/c172p.xml file so i don't know why my craft settings > were reset to the defaults... > > > anyway, here's the run... > > > ** Start Date: 2018-09-09 12:39:38 -0400 ** > ** RUNCMD=/home/myuser/flightgear-dev/next/run_fgfs.sh --launcher > --config=/home/myuser/myflightgear/fg-150km-horizon.rc ** > > FlightGear: Version 2018.3.0 > FlightGear: Build Type Dev > Built with GNU C++ version 4.8 > Jenkins number/ID 0:none > Failed to load default (en) translations > [...] > Image loading failed:Warning: reading > "/home/myuser/myflightgear/Aircraft/c172p" not supported. > [...] > FGPropertyManager::GetNode() No node found for hydro/active-norm > ignoring unknown axis-alignment'yx-plane'. > ignoring unknown axis-alignment'yx-plane'. > ignoring unknown axis-alignment'yx-plane'. > empty 'not' condition > [...] > Starter on > Electrical system initialized > Astro Tech LC-2 Chronometer Loaded > Starting hard-coded terrain presampling > Garmin 196 loading cities > Garmin 196 loading cities done > Hobbs system started > Starter off > Nasal runtime error: non-numeric string in numeric context: '' > at /home/myuser/myflightgear/Aircraft/c172p/Nasal/state-manager.nas, > line 75 > Primer reset to 0 > Hobbs system stopped > > ** End Date: 2018-09-09 12:48:23 -0400 ** > ** Total Elapsed Time: 0 days 0 hours 8 minutes 45 seconds ** > > ** Build Info: ** > *********************************************************************** > PLib: a542b8a03f8de1fe844af6ab4734b64d11e272e9 > OSG 3.4: 1f89e6eb1087add6cd9c743ab07a5bce53b2f480 > Simgear: 32189b72391c6f255bd5d87151ecbb110a5282fe > FGFS: f39b81c8723f34363a0b0e54b758a81208ef73c4 > FGData: ab9805ca9b7cd3129d6b85b650df62d71906e3c1 > FGAddon: r3504 | isaakd | 2018-09-07 13:05:54 -0400 (Fri, 07 Sep 2018) > *********************************************************************** > > c172p: 2332916f03638ff08e2da379e0f3f0e088ec3f63 > > > |