For the last couple of weeks, cvs fgfs does not allow initialization by
--prop:/environment/clouds/layer[0]/elevation-ft=
--prop:/environment/clouds/layer[0]/thickness-ft=
--prop:/environment/clouds/layer[0]/coverage=
either using fgrun or from the command line.
What I am getting is two layers
Stuart Buchanan wrote:
Dave Perry wrote:
For the last couple of weeks, cvs fgfs does not allow initialization by
--prop:/environment/clouds/layer[0]/elevation-ft=
--prop:/environment/clouds/layer[0]/thickness-ft=
--prop:/environment/clouds/layer[0]/coverage=
either using fgrun or from
Hi All and Happy New Year,
After updating SimGear and fgfs source from cvs yesterday, I noticed
that at low throttle near or on the ground, there is a vertical plane in
the field of view such that all the view beyond the prop disc and beyond
this plane is darker. This is in the pa24-250 which
John Denker wrote:
Hi --
On 01/01/2009 01:17 PM, Torsten Dreyer wrote:
Please find attached a patch as a proof of concept that has been in my head
for a while now. Here is a short description of what it does:
Check if /systems/electrical/outputs/dme exists (but don't create)
If yes:
John Denker wrote:
On 01/01/2009 05:05 PM, Martin Spott wrote:
Different aircraft are equippped with electrical systems of different
nominal voltage. You can buy most of the common instruments for at
least two different voltages,
I have no objection to standardizing on real volts
John Denker wrote:
Question: In the current CVS, why are there five inequivalent copies
(six copies total) of kr87.xml?
Similarly, why are there four inequivalent copies of kx165*1.xml?
And other examples
Other things being equal, such lack of modularity might be
somewhat
This may have already been reported. This is with cvs fgfs and SimGear
and osg from svn all updated last Monday and plib-1.8.5 running with
up-to-date f9 on a amd athlon XP 3200+ with 2 GB ram and a GeForce 7800
SG OC with 256 MB GDDR3 from BFG.
I took off in the pa24-250 from Dare CO KMQI
Typically, the bendable trim tabs on aileron and rudder are used in real
life to get near hands off performance at typical cruise with the ball
centered. So a modeller will use the property browser and adjust the
values to achieve this so the ball is centred with wings level and no
aileron
Stuart Buchanan wrote:
dave perry wrote:
You were correct. I had not set the weather scenario to METAR. I ran
fgfs once with 3D clouds and once w/o 3D clouds, both with
real-weather-fetch and scenario METAR. I only got 1 fps with the 3D
clouds. Earlier with 3D clouds, I got about
gerard robin wrote:
On lundi 08 décembre 2008, Stuart Buchanan wrote:
Heiko wrote:
The clouds looking great now- the order problem is 99% solved so much as
I can see!
Yes - I think we're pretty much done.
I see only some few problems still:
-against a second
Jon S. Berndt wrote:
The JSBSim C172 FDM assumes the thrust line is the X axis. I'm not sure what
the angle of incidence of the wing is, but it seems that at rest on the
runway the pitch of the C172 should be 5 degrees, according to the picture
you attached.
Jon
But as others have
Stuart Buchanan wrote:
Dave Perry wrote:
The 3D cloud appearance is much improved. Thanks to all involved!
Several questions and comments.
1. At night, the emmissive seems very very bright.
2. Are you intending that the 3D cloud base should match the lowest
level in the current
Is there a reason that com1 and nav1 are the lower kx165 while the nav1
vor head is on top?
--
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.
dave perry wrote:
Hi All,
snip
Would it not be more realistic to rotate the 3D model about -3 or -4
degrees about the ac3d z-axis.
I did not make myself clear in the initial questiion. The video link
only detracted from my point. The model in the .ac file is just a rigid
body
Curtis Olson wrote:
Hi Dave,
I just commited a tweak to FlightGear cvs that relaxes the check for a
stationary versus moving
view point to account for the moving view offset as the aircraft flies
by. See if things work any
better for your now.
Thanks Curt,
This fixed it so the doppler
Curtis Olson wrote:
I've done some work on the sound system in main.cxx and have attached
a patch for folks to review if they want to look at what I did.
I made a simplifying assumption that the listener is either stationary
(stationary enough) or it is tracking with the aircraft model
Curtis Olson wrote:
Hmmm, I don't see anything obvious in the code that would cause this.
Actually, you should only get the doppler effect in stationary
views. Chase views will inherit the model velocity. But you should
get doppler effect in the fly-by view and tower views ... is this
Hi all,
Over the weekend, I compiled osg from svn update, SimGear from cvs
update, and FlightGear source from cvs update. My frame rate is now
less than 10 fps and it was a solid 31 fps with
--prop:/sim/frame-rate-throttle-hz=30 and 50 to 70 fps w/o the
frame-rate-throttle. The before
dave perry wrote:
Hi all,
Over the weekend, I compiled osg from svn update, SimGear from cvs
update, and FlightGear source from cvs update. My frame rate is now
less than 10 fps and it was a solid 31 fps with
--prop:/sim/frame-rate-throttle-hz=30 and 50 to 70 fps w/o the
frame-rate
Heiko Schulz wrote:
The Noratlas Landing light is crude, not perfect. Versus
the snapshots from
Torsten which is smooth and more realistic :)
Smooth?
The lightcircles could need a bit more segments, but for me it looks like
your approach.
Nethertheless- fine that you both
and recompiled all three. The 3D instruments were still not
visible.
- Dave Perry
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK win great
Hi,
I just rebuilt fgfs with plib-1.8.5, OpenSceneGraph-2.4.0, and cvs
SimGear and FG source. The menu bar is now very small and has no text.
Has something changed so I need something else?
- Dave Perry
-
This SF.net
initialized (I speculate) until this is done.
- Dave Perry
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01
Ron Jensen wrote:
On Sat, 2008-03-01 at 20:37 -0700, dave perry wrote:
I just noticed that the recent electrical updates to the kt170.xml
submitted by Ron Jenson make the kt70 bright white if the instrument
lights are turned on in the pa24-250 and the pa28-161. This is because
I just noticed that the recent electrical updates to the kt170.xml
submitted by Ron Jenson make the kt70 bright white if the instrument
light are turned on in the pa24-250 and the pa28-161. This is because
the material animation factor should be between 0 and 1 and this change
makes it equal
LeeE wrote:
On Monday 11 February 2008 13:59, Melchior FRANZ wrote:
* Thomas Förster -- Monday 11 February 2008:
At least I think conservative is the right term.
Oh, I didn't think that it was wrongly used. It's just that
the decision was meant to be reasonable for the
Curtis Olson wrote:
On Feb 13, 2008 2:59 PM, dave perry wrote:
I have the thread from 2006-08-26 between Curt Olson and Frederic
Bouvier on this subject. The connection to the 496 is via a db-9 to
super small usb cable I got from garmin as suggested in the garmin
user's
I have the thread from 2006-08-26 between Curt Olson and Frederic
Bouvier on this subject. The connection to the 496 is via a db-9 to
super small usb cable I got from garmin as suggested in the garmin
user's guide. From a dmesg, I expect that com1 is /dev/ttyS0 on my f7
system. I use the
Hi Curt and Frederic,
My wife gave me a Garmin GPSmap 496 for Christmas. Nice wife, huh!
Anyway, I recalled this thread and want to confirm whether either of you
have had success with the --AV400 beyond what was reported in this
thread. Did you get FlightGear to drive the Garmin GPS III
Tim Moore wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
dave perry wrote:
| Tim Moore wrote:
| -BEGIN PGP SIGNED MESSAGE-
| Hash: SHA1
|
| dave perry wrote:
| | Tim Moore wrote:
| | -BEGIN PGP SIGNED MESSAGE-
| | Hash: SHA1
| |
| | I've checked in a fix
Tim Moore wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
dave perry wrote:
| Tim Moore wrote:
| -BEGIN PGP SIGNED MESSAGE-
| Hash: SHA1
|
| I've checked in a fix that addresses the non 4:3 problem and also fixes
the osgviewer
| distortion issue. It turned out to be pretty
dave perry wrote:
Tim Moore wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
dave perry wrote:
| Patch adds a member function to FGRenderer class that returns the
| current aspect ratio. Uses this in place of 4.0/3.0 in setFOV and
| setNearFar.
|
| The diff follows
Tim Moore wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
dave perry wrote:
| Patch adds a member function to FGRenderer class that returns the
| current aspect ratio. Uses this in place of 4.0/3.0 in setFOV and
| setNearFar.
|
| The diff follows:
|
This seems a little confusing
Patch adds a member function to FGRenderer class that returns the
current aspect ratio. Uses this in place of 4.0/3.0 in setFOV and
setNearFar.
The diff follows:
? renderer.diff
Index: renderer.cxx
===
RCS file:
this
is happening to no avail. But I am still just learning c++. Can
someone help me chase this down?
dave perry wrote:
Hi all,
I have not had a working osg build since late September when I installed
F7. Yesterday, I did fresh check outs of osg, simgear, and flightgear
source and data. I now have
dave perry wrote:
Concerning the first bug;
snip
In the osg branch, it seems to me that the
verital and horizontal fov are simply scaled the same which results in
the distortion. I have looked in the source to try and find where this
is happening to no avail. But I am still just
Patch fixes the bad assumption in osg fgfs that aspect ratio is always
4:3. I tested all the standard views and also resizing the window.
Would someone with cvs submit capability check the patch and then commit it.
- Dave P.
? renderer.diff
Index: renderer.cxx
dave perry wrote:
Patch fixes the bad assumption in osg fgfs that aspect ratio is always
4:3. I tested all the standard views and also resizing the window.
The testing done above was with no sdl or osgviewer (just freeglut).
This works fine. But with --enable-sdl or with --enable
Hi all,
I have not had a working osg build since late September when I installed
F7. Yesterday, I did fresh check outs of osg, simgear, and flightgear
source and data. I now have two problems that are not there with V1.0,
or the plib cvs branch.
1. Wrong ASPECT RATIO on non 4:3 monitors
the effective fov, not the aspect ratio.
- Dave Perry
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01
Hi all,
I searched this list for a change to trim initialization but did not
find any. This is from the plib branch, essentially V1.0.
I have initial values specified in the -set.xml file for
/controls/flight/elevator-trim
/controls/flight/aileron-trim
/controls/flight/rudder-trim
which are
dave perry wrote:
Hi all,
I searched this list for a change to trim initialization but did not
find any. This is from the plib branch, essentially V1.0.
I have initial values specified in the -set.xml file for
/controls/flight/elevator-trim
/controls/flight/aileron-trim
/controls/flight
I noticed that with the mode selector set LOC NORM, if you turned off
the ALT to use PITCH to do a step-down, and then went back to ALT on,
the GS would never be acquired. This one-line patch fixes this problem
that affected both the pa24-250 and the SenecaII. Would someone please
commit
LeeE wrote:
On Monday 24 December 2007 02:37, dave perry wrote:
dave perry wrote:
I was enjoying the new gallery pictures when I noticed that the
rudder and vertical stab of the comanche do not cast a shadow
on the stabilator. So I tried to discover why not. With
shadows
. But they do cast a shadow on the trim tab even with
transparency on. The model was done in ac3d. I could have not yet
found documentaion on shadows on aircraft. What do I need to change to
correct this?
Dave Perry
-
This SF.net
dave perry wrote:
I was enjoying the new gallery pictures when I noticed that the rudder
and vertical stab of the comanche do not cast a shadow on the
stabilator. So I tried to discover why not. With shadows on and
transparency off, the rudder and vertical stab do cast a shadow
that better matches
the specifications ?
-Dave Perry
-
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http
made the final product
significantly better and this joint effort is one of the most rewarding
aspects of being a part of FlightGear.
Regards,
Dave Perry
But I will go with what the consensus becomes on this issue.
-
SF.Net
a model of this AC to FlightGear.
-Dave Perry
-
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http
dave perry wrote:
The same pair owned a copy of the Curtis-Wright pusher with a real gnome
rotary (stationary crank with rotating case and cylinders). That flew
quite well and was very maneuverable although the rotary caused a lot of
precession force with maneuvers.
Correction
response and aileron inputs from the AP almost 180 degrees out of
phase. If you turn on auto coordination, the oscillations disappear. I
tried Jon Berndt's suggestion of adding a scaling value. It had only
minimal affect. Even with this set to 0.0, the yaw problem persists.
-Dave Perry
for the c172p with the
kap140 autopilot and the SenecaI with the AltimaticIIIc autopilot.
Setting turbulence = 0.0 from fgrun will not zero these values. Using
--turbulence=0.0 on the command line will result in all the turbulence
values being zero.
-Dave Perry
of FlightGear.
-Dave Perry
-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http
dave perry wrote:
Laurence Vanek wrote:
I believe, however, that something else is going on with the A/P during
ILS approach. I do not get the behavior you report on approach. The A/P
begins to make large over corrections about one mile out, to the point
where I need to disable
\
data/Aircraft/wrightFlyer1903 \
Cheers,
Durk
-Dave Perry
-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let
approaches even in light turbulence.
Original Message
Subject:Re: [Flightgear-users] Seneca II - couple of user comments
Date: Sun, 02 Dec 2007 19:10:05 -0700
From: dave perry [EMAIL PROTECTED]
Reply-To: FlightGear user discussions
[EMAIL PROTECTED
SydSandy wrote:
Hi all , still seeing the global error message pop up on MP , so I did a
check and found these still using global.
I'd be happy to fix them , but they aren't mine :)
Instruments-3d/Century-III/AltimaticIIIc.xml
Instruments-3d/Century-III/CenturyIII.xml
I just emoved the
,
Dave Perry
? pitts.diff
Index: pittss1c.xml
===
RCS file: /var/cvs/FlightGear-0.9/data/Aircraft/pittss1c/pittss1c.xml,v
retrieving revision 1.1
diff -p -u -r1.1 pittss1c.xml
--- pittss1c.xml 10 Nov 2007 17:18:47 - 1.1
dave perry wrote:
Stuart Buchanan wrote:
The model and FDM are fairly basic, but it is quite fun to fly, and a
challenge to land. Comment and any modifications are very welcome.
This is my first YASim aircraft, so I'm sure the FDM could benefit
from some tuning.
Stuart
started with what you need to be ready to take-off.
Regards,
Dave Perry
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files
Melchior FRANZ wrote:
* dave perry -- Wednesday 07 November 2007:
There is a strange worble in the sound [...]
Please update (src/Main/main.cxx) and try again.
That fixes this issue. Thanks!
While testing this, I noticed another issue. When one switches on the
nav1 ident
on the ground seem normal.
Dave Perry
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your
dave perry wrote:
I just did a cvs up -dP for SimGear, fgfs, and data and then compiled
both for the plib branch. There is a strange worble in the sound that
gets worse at high angles of attach. This was not there after a similar
update last weekend. I have only checked the pa24
both.
Side comment. There are some AC in fgfs that start with the engine off,
but no hot spots or help to point to how to get the AC started. This
definitely is bad. AC designers need to include starting help.
Really great to have you back!
All the best,
Dave Perry
leee wrote:
On Monday 08 October 2007 02:17, dave perry wrote:
While optimizing the aitopilot config files for the Century IIB and III
autopilots for the pa24 and the Altimatic IIIc for the SenecaII, a
significant difference between the values of parameters (gains in
particular) that give
autopilot implementations once they are in cvs.
Cheers,
Dave Perry
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX
?
Regards,
Dave Perry
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy
to complete that model for the SenicaII.
Between the approach to handling the coupler mode selector and the
roll knob and the kap140.nas from Vegard Ovesen, this should not be
more than a few evenings work. Any problem with contributing to you
fine model?
Regards,
Dave Perry
dave perry wrote:
I am getting the following error building osg:
CMake Error: Error in cmake code at
/usr/local/source-osg/OpenSceneGraph-2.1.5/src/osgPlugins/osgFX/CMakeLists.txt:15:
Unknown CMake command SETUP_PLUGIN.
I get it withOpenSceneGraph/trunk as well as with 2.1.5 from
I am getting the following error building osg:
CMake Error: Error in cmake code at
/usr/local/source-osg/OpenSceneGraph-2.1.5/src/osgPlugins/osgFX/CMakeLists.txt:15:
Unknown CMake command SETUP_PLUGIN.
I get it withOpenSceneGraph/trunk as well as with 2.1.5 from the zip
archive.
I am
gh.robin wrote:
On sam 18 août 2007, dave perry wrote:
I am getting the following error building osg:
CMake Error: Error in cmake code at
/usr/local/source-osg/OpenSceneGraph-2.1.5/src/osgPlugins/osgFX/CMakeLists.
txt:15: Unknown CMake command SETUP_PLUGIN.
I get
I submitted 3 patches via Melchior today.
pa28-161 update
Last year after I completed the pa24, David Megginson sent me all the
detail pictures he had taken of his Piper Warrior II and indicated that
I should finish up the details on the pa28-161 in FlightGear. I spent
the last three weeks,
Curt,
You left a FIXME comment that the altitude should be for 29.92 inHg
and rounded. The encoder reports mode-c-alt-ft, so this patch points
the altitude node to this value and removes the redundant + 50 from the
FL rounding routine.
This requires a working encoder. Any AC using the encoder
After update of simgear, source, and data using
cvs up -Pd -rPRE_OSG_PLIB_20061029
for each update, I am getting the error when I run fgfs:
Unknown top level section: wxradar
Fatal error: Detected an internal inconsistency in the instrumentation
system specification file. See earlier errors for
On Wed, 2007-07-11 at 01:26 +0200, Csaba Halász wrote:
On 7/11/07, Dave Perry [EMAIL PROTECTED] wrote:
After update of simgear, source, and data using
cvs up -Pd -rPRE_OSG_PLIB_20061029
for each update, I am getting the error when I run fgfs:
Unknown top level section: wxradar
Fatal
On Tue, 2007-05-15 at 11:17 -0500, Curtis Olson wrote:
Here's a question for the group. We don't need to decide now, but we
need to figure this out before the final official 0.9.11 release.
Currently the data package is released with only a subset of all the
available aircraft:
On Wed, 2007-03-28 at 21:57 -0600, Ron Jensen wrote:
Dave,
I've been running John's code for a while now and have not noticed any
problems with it. I compiled with your patch this morning but have not
had a chance to fly it yet.
One change I would like see from a neatness point of view:
On Sat, 2007-03-03 at 08:31 +0100, Melchior FRANZ wrote:
* Dave Perry -- Saturday 03 March 2007:
Have you asked to have atmo.diff applied to cvs?.
I don't think it can be applied as it is. I'm no physicist and
can't comment on the logic, but there are some formal aspects
to fix IMHO
I get the following trying to update data.
[EMAIL PROTECTED] ~]$ cd $FG_ROOT
[EMAIL PROTECTED] data]$ su -c 'cvs update -dP'
Password:
cvs [update aborted]: error writing to server: Connection reset by peer
[EMAIL PROTECTED] data]$
Tried last evening and again this morning with the same
On Sat, 2007-03-24 at 12:33 -0400, John Denker wrote:
On 03/23/2007 11:01 PM, Dave Perry wrote:
Does anyone know what happened to John Denker?
Secondly, if he actually cared about my well-being, he would
talk *to* me rather than talking *about* me on this list.
This is not about you
Hi all,
Does anyone know what happened to John Denker? I am still interested in
the improved altimeter/atmosphere model being added to FlightGear. I
keep adding these back in after cvs/svn updates.
Dave perry
-
Take
On Sat, 2007-03-17 at 01:19 -0500, Laurence Vanek wrote:
Dave Perry wrote:
I get the following compile error well into the OSG compile on my just
installed FC6.
Entering directory freetype
make[3]: Entering directory
`/usr/local/source-osg/OpenSceneGraph/src/osgPlugins/freetype
With either the current fc6 fltk and fltk-devel installed (version
1.1.7-2) and fgrun-0.4.8 compiled from from tar ball, both the screen to
select AC and the screen to select the airport are blank.
I tried removing both fltk and fltk-devel rpms and compiling fltk-1.1.7
(from tarball) with
On Sat, 2007-03-17 at 08:48 -0500, Curtis Olson wrote:
Did you carry over your osg compile tree from a previous install of
linux? Perhaps there is some bits and pieces left over from the way
your previous system was structured.
That was it. Thanks!
A clean checkout from svn solved it.
Dave
On Sat, 2007-03-17 at 22:36 +0100, _hj_ wrote:
Dave Perry wrote:
I tried removing both fltk and fltk-devel rpms and compiling fltk-1.1.7
(from tarball) with
./configure --enable-shared --enable-threads
You have to add --disable-largefile to the configure line in fltk.
Hans
Thanks
I get the following compile error well into the OSG compile on my just
installed FC6.
Entering directory freetype
make[3]: Entering directory
`/usr/local/source-osg/OpenSceneGraph/src/osgPlugins/freetype'
make[4]: Entering directory
Quick response with a few factual corrections:
On Fri, 2007-03-02 at 00:56 -0500, John Denker wrote:
On 03/01/2007 08:02 PM, Dave Perry wrote:
there are only 3 options still being put forward; all having to
do with how the kap140 gets the baro shift. These are:
1
against cvs and let others test them
before submitting both to cvs. I am attaching a tar.gz patch against cvs
for what I am presently running so others can try it. It includes the
bug fix.
Regards,
--
Dave Perry
alt-encode-kap140.tar.gz
Description: application/compressed-tar
are
really serious about putting this in cvs. The options are of course
with and without the 2 lines of code to save the kollsman shift.
After sharing this analysis with the list, I will go with what the
community sees as the best option.
Comments from others?
Dave P
--
Dave Perry
On Tue, 2007-02-27 at 19:07 -0700, Dave Perry wrote:
Sorry,
I copied from the wrong version. I will add the missing line and delete
a declaration:
Here is an obvious fix for this bug in the update code:
void
Altimeter::update (double dt)
{
if (_serviceable_node-getBoolValue
-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
--
Dave Perry [EMAIL PROTECTED
On Sun, 2007-02-25 at 01:55 -0500, John Denker wrote:
On 02/25/2007 12:30 AM, Dave Perry wrote:
I have been communicating off and on with both John Denker and Roy
Vegard Ovesen off list concerning this topic. I am running an edit of
John's most recent altimetry patch and have modified
On Sun, 2007-02-25 at 06:39 -0700, Dave Perry wrote:
On Sun, 2007-02-25 at 01:55 -0500, John Denker wrote:
On 02/25/2007 12:30 AM, Dave Perry wrote:
The altitude capture in the current cvs kap140.nas used
altFt = pressureAltitude + hpartial * (baroSetting - 29.92
,
--
Dave Perry
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http
On Sun, 2007-02-25 at 15:14 -0500, John Denker wrote:
On 02/25/2007 02:39 PM, Roy Vegard Ovesen wrote:
I have not, and I don't think Dave Perry has either, expressed optinions to
indicate that the pressure altitude should not be quantized. What we have
said is that indicated altitude
On Sun, 2007-02-25 at 16:19 -0700, Dave Perry wrote:
What is contested is how to model the baro shift. What you suggest is
retrieve the indicated altitude and then subtract the PA to get the
encoder baro shift and then add back in the PA. This means the
kap140.nas has to retrieve the value
On 2/12 Dave Perry wrote:
It occurred to me that we should use John's interpolation function in
several other places:
1. We use a form of this function in kap140.nas without the efficiency
of the interpolation.
2. The encoder uses a similar interpolation that a general form
. Is the encoder
used anywhere other than by the KAP140? If so, we should use a separate
instantiation as suggested by John.
Regards,
--
Dave Perry
altimetry.tar.gz
Description: application/compressed-tar
-
Take Surveys. Earn Cash
On Sun, 2007-02-18 at 18:02 -0700, Dave Perry wrote:
I am not sure the new patch is giving the
same results, but I have not done any controlled comparisons;... I will
double check and compare some examples with the previous patch.
I was wrong. Both are giving the same results, much
for a switch.
Melchior,
Please rename Aircraft/Instruments-3d/mag.sw to
Aircraft/Instruments-3d/magneto-switch
and apply the attached patch, both in cvs.
--
Dave Perry
? Instruments-3d/magneto-switch
? j7w/j7w.xml.dp
Index: pa24-250/Models/pa24-250.xml
101 - 200 of 272 matches
Mail list logo
