Norman Vine writes:
FYI
http://openlight.com/fdui/
Interesting ... are these people aware of FlightGear? It looks like
they are doing cockpit UI type research (?) and they could plug right
into FlightGear to drive their displays.
Curt.
--
Curtis Olson IVLab / HumanFIRST Program
Interesting ... are these people aware of FlightGear? It looks like
they are doing cockpit UI type research (?) and they could plug right
into FlightGear to drive their displays.
Huh? I read into it that they were using flight deck metaphors to create
user interfaces - not necessarily
Once upon a time, you were sitting and writing:
Thanks Dave. It has more than enough information
(although it is not a typical electrical diagram).
I have a few dirty tasks for the weekend (like evaluating
a signal processing exam), so I won't be working on the
computer.
All the best,
On Friday 27 September 2002 9:47 am, Curtis L. Olson wrote:
Jon Berndt writes:
Interesting ... are these people aware of FlightGear? It looks like
they are doing cockpit UI type research (?) and they could plug right
into FlightGear to drive their displays.
Huh? I read into it that
I'm now seeing this when I do a 'cvs update -dP' in the development CVS tree.
cvs server: cannot open directory
/var/cvs/FlightGear-0.9/FlightGear/src/Systems/Vacuum: No such file or
directory
cvs server: skipping directory src/Systems/Vacuum
Is this anything I've done locally?
Matthew Law writes:
I'm now seeing this when I do a 'cvs update -dP' in the development CVS tree.
cvs server: cannot open directory
/var/cvs/FlightGear-0.9/FlightGear/src/Systems/Vacuum: No such file or
directory
cvs server: skipping directory src/Systems/Vacuum
Is this anything I've
I've just added a static port system and a new altimeter model to
CVS. Now, if you set the property
/systems/static/serviceable
to false, the altimeter will freeze. Otherwise, it displays the
altitude based on the difference between outside air pressure (with a
slight lag from the static
Just trying my first CVS update in a couple of weeks. I see there is a
new repository for the trunk, so I changed all my CVS/Root files to
point to the -0.9 one and logged in with the new password. [Why not
just have no password?] But I get:
cvs server: Updating .
cvs [server
Two base package files,
Input/Joysticks/CH/pro-pedals-usb.xml
Input/Joysticks/CH/pro-yoke-usb.xml
both still (or again) contain
nameMicrosoft-PC-Joysticktreiber /name
namePilote de joystick PC Microsoft /name
which is less than useful as discussed before. Please could someone
Julian,
which is less than useful as discussed before. Please could someone
remove those lines, and could contributors please be careful not to
include such lines in their contributions.
This was me :-( at a time when we did not yet completely figure where/how
the joystick is handled under
The username changed too.
Just trying my first CVS update in a couple of weeks. I see there is a
new repository for the trunk, so I changed all my CVS/Root files to
point to the -0.9 one and logged in with the new password. [Why not
just have no password?] But I get:
cvs server:
The static system itself needs a little more work, including support
for multiple static ports, sideslip errors, and alternate air (from
inside the cabin); those won't be hard to add, but if anyone (Alex?)
wants to take a look at src/System/static.[ch]xx and add them in
before I have a
The VSI and ALT are connected to the static port. When that port is
blocked,
Don't forget to put in the alternate static source switch on the panel,
and cause it to read as a slightly rearward facing static port.
the ALT will freeze at its current altitude reading, and the
VSI will
On Fri, 2002-09-27 at 15:09, Alex Perry wrote:
The static system will probably be more challenging as that's where most
of the subtle errors seem to crop up. Cessna gives tables relating IAS
to CAS (which is largely the static source error). If that's standard
practice, incorporating a
Alex Perry writes:
The static system itself needs a little more work, including support
for multiple static ports, sideslip errors, and alternate air (from
inside the cabin); those won't be hard to add, but if anyone (Alex?)
wants to take a look at src/System/static.[ch]xx and add them in
Alex Perry writes:
You need to handle the special case of large dt (as well as negative)
more carefully ... for the same reasons as I did in Steam's function.
Nice timing. In fact, I copied your low-pass function into
Main/utils.[ch]xx just a short while ago and am now using it.
All the
Curtis L. Olson writes:
Yes, if you use an int and track time in increments of 1 / 1,000,000
then you get about 30 minutes before you hit an anomaly. This bug
caused problem in the past such as radio station searches to only
happen every other 30 minute period, or panel text to stop
Tony Peden writes:
And so, I stand by my statement. Most of the time the static errors
are the ones that you need to worry about. You don't spend alot of time
at either high angles of attack or high sideslip angles.
Unfortunately, the little bit of time you do spend in heavy sideslips
Curtis L. Olson writes:
Yes, if you use an int and track time in increments of 1 / 1,000,000
then you get about 30 minutes before you hit an anomaly. This bug
caused problem in the past such as radio station searches to only
happen every other 30 minute period, or panel text to stop
However, the airspeed indication will be inconsistent and
a full instrument scan will immediately identify the problem.
When will you connect the ASI between the pitot and static ?
I think I need a fresh day for that one -- it's a little complicated.
The TC will be easier as soon as
Norman Vine writes:
Yep there is a problem if you try to run a FGFS session on a
Windows box much over 49 days :-)
I wouldn't know anything about that, and far be it from me to
blatantly bash windows, but if you manage to have your windows box run
that long, I'd definitely recommond that you
David Megginson writes:
And so, I stand by my statement. Most of the time the static errors
are the ones that you need to worry about. You don't spend alot of time
at either high angles of attack or high sideslip angles.
Unfortunately, the little bit of time you do spend in
David,
Just had a look at the latest additions, good work, this is an area
that has been very lacking in flightgear and it's nice to finally be
addressing it.
The airspeed indicator is still working for me, even when the static
system not servicable.
David Megginson writes:
I think I need a
We must all be a bunch of pathetic geeks if the list traffic takes off
on friday and saturday nights. :-)
Contributing-to-the-traffic-ly yours,
Curt.
--
Curtis Olson IVLab / HumanFIRST Program FlightGear Project
Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED]
Curtis L. Olson
Norman Vine writes:
Yep there is a problem if you try to run a FGFS session on a
Windows box much over 49 days :-)
I wouldn't know anything about that, and far be it from me to
blatantly bash windows, but if you manage to have your windows box run
that long, I'd
Norman Vine writes:
Hmm... I can't rememeber crashing this box in a long time
and if it wasn't for needing to reboot in order to access the CVS ...
Oh right I don't need to do that anymore :-)
So remind me to send you one of these in a cople of months :-)
510 src
$ cat
Alex Perry wrote:
The username changed too.
Yes, I forgot to mention that. However, you can see that my problem was
not logging in but updating.
Someone must know how to get around this ... anyone?
- Julian
Just trying my first CVS update in a couple of weeks. I see there is a
new
Julian Foad writes:
Alex Perry wrote:
The username changed too.
Yes, I forgot to mention that. However, you can see that my problem was
not logging in but updating.
Someone must know how to get around this ... anyone?
Personally, I just did a fresh checkout.
Curt.
--
Curtis Olson
Curtis L. Olson wrote:
Julian Foad writes:
Alex Perry wrote:
The username changed too.
Yes, I forgot to mention that. However, you can see that my problem was
not logging in but updating.
Someone must know how to get around this ... anyone?
Personally, I just did a fresh checkout.
I am working on interfacing an external flight model to FlightGear via
the network. This particular code reports an altitude of zero/0.0f
when the wheels are resting at sea level.
The c172 3d model is drawn so that it's center of gravity is at the
reported altitude. Also the pilot view point
Julian Foad writes:
Curtis L. Olson wrote:
Julian Foad writes:
Alex Perry wrote:
The username changed too.
Yes, I forgot to mention that. However, you can see that my problem was
not logging in but updating.
Someone must know how to get around this ... anyone?
Personally, I just did a fresh checkout.
D'oh.
Depending on how aggrivating this all is/has been you guys might
consider a pitch-in-and-buy-curt-a-cvs-book fund. :-)
What make you think, that we think, that you'd take the time to read it ?
8-)
Alex Perry wrote:
Pitot source errors occur mostly
1. In slips, especially in full forward slips
2. At unusual angles of attack, especially no-flap slow flight
IIRC, I read that the EuroFighter uses a system which selects the best source
of data for this stuff taking into account the last
Alex Perry writes:
Personally, I just did a fresh checkout.
D'oh.
Depending on how aggrivating this all is/has been you guys might
consider a pitch-in-and-buy-curt-a-cvs-book fund. :-)
What make you think, that we think, that you'd take the time to read it ?
8-)
That's fair :-)
Page 46 of the PDF describes the pressure defect, with example values.
Whether we can adapt this to be a useful lookup table is another matter.
They also have nice equations, later on, converting test data into a model
that predicts errors. However, the conversion implies having raw data.
Maybe
Curtis L. Olson
I actually have a rcs/sccs book sitting on my shelf (good thing I
proofread my messages ... I originally wrote sitting on myself which
is close, but doesn't quite convey the same thing.) I bought it
because it advertised a cvs section, but the cvs info turned out to be
Norman Vine writes:
I am still not convinced that your tile is actually loaded though
and don't really know the 'best' way to check for that given the
'lazy' loader.
I can think of two options:
1. we can attach a separate deferred model queue to each deferred
tile, so that the queue
Curtis L. Olson writes:
The airspeed indicator is still working for me, even when the static
system not servicable.
I haven't done an ASI yet -- I need to model the pitot system for that.
If you want to parameterize your turn-coordinator modeling code, In
the C172S (serial #'s 172S8704
There is a slightly more complex model for vacuum in Steam.
I suggest you snag it and then delete it from Steam.
Just out of curiosity, do you know if it's common for twins to have a
separate vacuum pump attached to each engine in case of failure in IFR?
I have no idea; I'm not AMEL
Curtis L. Olson writes:
I am working on interfacing an external flight model to FlightGear via
the network. This particular code reports an altitude of zero/0.0f
when the wheels are resting at sea level.
The c172 3d model is drawn so that it's center of gravity is at the
reported
In src/Main/viewmgr.cxx I found:
setPilotXOffset_m(fgGetDouble(/sim/current-view/x-offset-m));
setPilotYOffset_m(fgGetDouble(/sim/current-view/y-offset-m));
setPilotZOffset_m(fgGetDouble(/sim/current-view/z-offset-m));
This looks like it needs to be set in the global preferences file
Curtis L. Olson writes:
In src/Main/viewmgr.cxx I found:
setPilotXOffset_m(fgGetDouble(/sim/current-view/x-offset-m));
setPilotYOffset_m(fgGetDouble(/sim/current-view/y-offset-m));
setPilotZOffset_m(fgGetDouble(/sim/current-view/z-offset-m));
This looks like it needs to be set in
On Fri, 2002-09-27 at 17:26, Alex Perry wrote:
Page 46 of the PDF describes the pressure defect, with example values.
Whether we can adapt this to be a useful lookup table is another matter.
They also have nice equations, later on, converting test data into a model
that predicts errors.
Curtis L. Olson [EMAIL PROTECTED] said:
In src/Main/viewmgr.cxx I found:
setPilotXOffset_m(fgGetDouble(/sim/current-view/x-offset-m));
setPilotYOffset_m(fgGetDouble(/sim/current-view/y-offset-m));
setPilotZOffset_m(fgGetDouble(/sim/current-view/z-offset-m));
This looks like it
44 matches
Mail list logo
