Updated electrical system ...instrument light output normalized
Added OSG hotspots to most instruments ... more to go yet
PLIB hotspots temporarily broken ..need to resize panel to avoid whiteouts...
(a waste of time ) but some still use PLIB , so needs to be fixed ... ;)
- fix breakage due to former commit (AIManager.cxx, r1.72)
- make AI properties available in AIBase
- add <valid> property for animations/nasal scripts
- support more MP and AI targets
- add target select and altitude display
Updated KFC200 ALTITUDE mode ... sets pitch hold until selected altitude is captured ... pitch controlled by switch on controller...
KNS 80 nav radio can store 1 selected radial per stored frequency ... stored distance will come when I understand RNAV better...
More instruments underway....
Aligned hotspots...
Moved kfc200.nas to Instruments-3d where it belongs...
Redoing the kfc200 flightdirector with newer functions (setlisteners) ...still in progress
Updated radios to change standby frequencies instead of selected frequencies....
Updated CitationX autopilot....
Autopilot is in flightdirector mode by default...
Until instruments are created , enable autopilot by setting "/autopilot/locks/passive-mode" to false
a cursor, after all, and the term "cursor" is already used for the startup
model. That one should really be called "model", but can't, because this is
already used for the ufo 3D model property ... sigh. :-]
- replace lon/lat adjustment with more predictable nearer/farther/left/right
adjustment (i.e. movements relative to the UFO position)
- add key bindings to move objects
This patch makes the pa24 changes to use the mag.sw from Instruments 3d.
Changed the mag_switch.ac to include the pick rectangles and the
mags.xml to use the pick automation. Also includes the edits to
pa28-161.xml and pa28-161-set.xml to use the 3d radio stack.
Changes:
1. remove typo from all the /Systems/KAP140.xml files
2. changes to put radio_stack in Instruments-3d
3. Add "pick" to vor, alt, hi, in Instruments-3d
4. changes to pa24-250 and pa28-161 to use 2 and 3.
5. add "pick" and "2d text in window" in 3d OAT in pa24-250
"This patch allows all the AC using the kap140 to use one kap140.nas
which includes Roy's move to "bool" values as well as the check for
power used by the pa24-250." (dp)
includes Instruments/fuel.xml. And *that* one creates tank[0] and tank[1]
for *all* aircraft, which is quite annoying. A generic panel should display
fuel numerically (like Lee's panels do) or as %.
I did some more work on the pa24-250 over the holidays.
1. Used nasal to emulate egt performance very similar to the real AC.
2. Changed the airspeed so the pressure altitude/temperature correction
ring for true airspeed works.
3. Modeled the OAT after the battery powered OAT in the real AC.
one left click on the "hot spot" displays OAT in C
2nd left click displacs OAT in F
3rd left click is off
times out after 5 min and turns off (to save battery)
4. Other 3d clean-up
aar.nas disables $FG_ROOT/Nasal/fuel.nas' main loop, as it should be able
to fully replace it. Ideally, there would be no aar.nas at all, and fuel.nas
would do the job for YASim & JSBSim. Unfortunately, there's a problem with
fuel.nas that's not easy to fix ...
far as this supports air refueling at all)
- make listeners keep variables up-to-date (for better performance)
- remove the ugly initialization stuff in the main loop, but wait in
an extra loop for the FDM to come up
This script works now with the a4f, too. The vulcan2 is *supposed* to
work, but there's apparently a bug in it that prevents it.
/systems/refuel/contact is correcly set, and that should be enough for it.
- if the selected model is the sign placeholder (Aircraft/ufo/Models/sign.ac;
first entry in the m-key dialog), then the export writes an OBJECT_SIGN
entry with the legend as contents (rather than the path).
Note that the input field for legend/comment is invisible if it doesn't
contain any text. You find it if you click right over the status line
entry in the lower left corner. Usability bug by design. :-)
(The dialog can also be dragged to another place.)
load the export file directly into fgfs via --config option:
--config=$HOME/.fgfs/ufo-model-export.xml (An fgfs wrapper could add
this option automatically if the file exists. Mine does. :-)
- import all /models/model[n] objects into the UFO's model manager, so
that they become editable
Both features together allow to save an UFO object session and to continue
it next time.