ufo position, but the selected objects: ctrl-mmb left/right/up/down move
the objects left/right/away/nearer, and ctrl-mmb-lmb l/r/u/d rotate them
all around the active object ('m'-key marker!) or raise/lower them.
(the gear-key 'g' can for now be used as a Ctrl replacement for people
with 2 button mouse; will probably be moved to a better place ...)
When holding the gear key or button down (as a kind of modifier) and after
left-clicking on the terrain, teleport the UFO to the click position.
Keep heading if no model is active, otherise look there. Keep altitude-agl.
(but disabled) by default. You won't notice any difference, unless you
place, let's say, an A-10-model.xml in the scenery. Some of the A-10's "select"
animations unselect the fuselage and other parts, when they thinks the A-10
is in cockpit view, not knowing that it's actually the *ufo*, which is in
cockpit view.
This patch for the 3d artificial horizon enables the movement of the
reference bar like the 2d instrument and corrects the wrong display of
pitch.
The original version already has a reference bar object in the .ac file
called bezel, but it is not bound to a animation. And the pitch is
indicated approx. 25% low so a pitch of +10deg is indicated as approx.
7deg.
"I have been working with Torsten Dryer to model
these three autopilots that are very common in aircraft manufactured in
the 1960s through the late 1980s. The Altimatic IIIc in the SenecaII is
a variation on the Century III and uses the same nasal model."
mf: these should be in cvs since a while; somehow I missed them, sorry
"For more than a month, I have been working with Torsten Dryer to model
these three autopilots that are very common in aircraft manufactured in
the 1960s through the late 1980s. The Altimatic IIIc in the SenecaII is
a variation on the Century III and uses the same nasal model."
A camera tool for making fgfs videos (heavily used by Michelle) and for
tracking MP and AI aircraft. It's planned to include this into the regular
ufo, but for now it's better to keep them separated. Comes with its own
panel, which (hopefully) is self-explaining.
Shouldn't be announced on the fgfs page as separate aircraft (if that's
possible). Work in progress ...
At the moment only the range can be changed via panel click action
(click on the range numbers). Weather radar can be turned on in
/instrumentation/radar/display-controls/WX. ai/mp display to come.
For those who miss the old 2D panel, just use an aircraft with a decent
panel and add --fdm=ufo for the same effect.
algorithm (needed for the file selector and useful for other purposes, like
assembling lists of livery or screenshot files etc.)
- io.nas: move fixpath to string.nas (it's not only useful for file paths
but can also be used for property paths)
- screen.nas: move trim to string.nas (used by screen.nas and nasal-console.xml)
- gui.nas: add pattern matching to FileSelctor
- ufo.nas: use patterm matching (only *.ac and *.xml files shall be listed)
- in replay mode
- when trying to raise the flaps, but they are already fullly up
- when trying to retrace the gear, but it is already retracted
more cleanup later ... much later :-)
- Automatic pitch trim (use autopilot/KAP140/settings/auto-pitch-trim to turn
on/off)
- Aural altitude alerter. Uses the same sound file as the stall warning.
- Replace custom flasher routines with nasal aircraft.light objects.
- Cleanup.
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.
I missed a few things in the last patch.
1. prop size did not match prop disc size.
2. rescaled yoke to match measured yoke.
3. messed up hot spots for heading indicator knobs when I tweaked the
panel last patch.
The fix that could not wait was #3, so I also re-textured the pilot head
with outdoor face photos. Yep, that's my face. The hair is now
textured also which looks better close up.
1. Added a pilot.
2. Cleaned up the panel, added a working park brake lever, added the
remaining placards, added "materials lighting for the remaining
switches and knobs tied to the nave light switch.
3. Doubled the resolution of the transparent rgb, added propdisc spin,
and realigned all in the ac file so the spin was concentric.
- add status line (green: active model -- clicks will plant it;
orange: selected model -- adjustable/removable)
- make manually selected models active (that is: further clicks will plant
this model type); doesn't apply to automatically selected models (after
removing)
- cleanup
TODO: yet more cleanup, add missing terminal output, etc.
that the --dme option sets the switch position correctly, but the
preferences.xml file is read after that and sets the switch back to 1.
And then we do *correctly* get nav1. Ideally, we would only let
preferences set the switch position if it wasn't set before, but
for now lets just comment that out there.
I have implemented a Honeywell MK VIII EGPWS emulation for FlightGear.
The MK VIII is an Enhanced Ground Proximity Warning System aimed at
regional turboprop and small turbofan aircrafts such as the Citation,
Citation Bravo, B1900D, Beechcraft 99 and L410.
Frederic Bouvier:
make the MSVC compilation possible. Rearrange base package directories.
I put 3 patches and a sound file in this tar. The c172p... patch
removes an unnecessary patch I submitted to the c172p. It has no affect
on performance. The Instruments-3d... patch adds a working skid ball to
the tc and switches the vor xmls to using params so it is easier to
edit. It also constrains the glide-slope needle to -32 to 32 degrees.
The pa24-250... patch fixes an edit error (corrects a misnamed switch
"click", no change in performance) and adds a "squish" sound to the
primer pump action.
Here is a patch that included the changes in my 2/22/06 posting plus the
3d-instrument light "emission" animations. I also added a magnetic
compas mount and moved it forward and down to better match the real ac
and make it easier to read when adjusting the hi. Ignore the "?" flaged
files at the beginning. none are required. I noticed that there is a
backup copy of pa24-250.ac in the pa24-250 folder in cvs. It can be
deleted. The only copy of that file required is in pa24-25/Models.
I "flew" a shake down instrument XC from 2v2 (Longmont, CO) to KLVN
(Airlake, just south of Minneapolis, MN). Even the fuel management is
realistic. The autopilot on the menu bar works well. Give the changes
a try and enjoy!
Here are the latest updates.
- Most of the changes involve moving instruments / animation / hotspot files
to instruments-3d.
- Some re-texturing.
- Finished Aerostar gear animation.
- I tried adding a LONG variable to the nav radio property tree,
but the conversion kept coming out wrong. Multiplying frequencies
by 100 and outputing that to another DOUBLE worked, but I cant find
the Comm frequencies property updating for the life of me ..... oh
well Nasal works.
I made a minor change to one file in the c172p that accommodates a
feature I added to the navcom-kx155.xml and the dme.xml in the
Instruments folder. I wanted to leave the frequencies, etc. on these
dark until there was voltage applied to
/systems/electrical/outputs/nav. This was accomplished by adding a
param and property alias pointing to the appropriate value. Since the
c172p "always" applies 28 volts, this made no change in the c172p, but
allowed me to model the avionics master and battery master realisticly
in pa24-electrical.nas. I put in comments explaining this at the change
points.
There is a useful "help > aircraft help" that walks you through the
start procedure and lists the key bindings as well as the key to "light
up" the hot spots.
feature I added to the navcom-kx155.xml and the dme.xml in the
Instruments folder. I wanted to leave the frequencies, etc. on these
dark until there was voltage applied to
/systems/electrical/outputs/nav. This was accomplished by adding a
param and property alias pointing to the appropriate value. Since the
c172p "always" applies 28 volts, this made no change in the c172p, but
allowed me to model the avionics master and battery master realisticly
in pa24-electrical.nas. I put in comments explaining this at the change
points.
There is a useful "help > aircraft help" that walks you through the
start procedure and lists the key bindings as well as the key to "light
up" the hot spots.
I made a minor change to one file in the c172p that accommodates a
feature I added to the navcom-kx155.xml and the dme.xml in the
Instruments folder. I wanted to leave the frequencies, etc. on these
dark until there was voltage applied to
/systems/electrical/outputs/nav. This was accomplished by adding a
param and property alias pointing to the appropriate value. Since the
c172p "always" applies 28 volts, this made no change in the c172p, but
allowed me to model the avionics master and battery master realisticly
in pa24-electrical.nas. I put in comments explaining this at the
change points.
There is a useful "help > aircraft help" that walks you through the
start procedure and lists the key bindings as well as the key to "light
up" the hot spots.
