Sorry to muck people (esp David, by the sound of it) around, but I have
'live' DAFIFT importing working in my local tree (for about 3 weeks
now), I've just been holding off submitting while I did more testing.
I've had to extend the Nav types and APIs slightly, to cope with
multiple fixes / int
Michael
Ok thanks, I have been using the one form wolframs page, but was
wondering about the gpl deal. Also thanks for the links, I think a t38
model is in the works at flight gear, as well as f16.
Paul
___
Flightgear-devel mailing list
[EMAIL PROTECT
At 2/21/03, Paul D. wrote:
Michael
I was interested in finding one for the twin-otter, just curious how you
went about finding these?
A Twin Otter model is here:
http://home.t-online.de/home/Wolfram.Kuss/FGFS1/FGFS1.htm
This is the one we use w/ our icing work.
To find potential GNU GPL models
Michael
I was interested in finding one for the twin-otter, just curious how you went about
finding these?
Paul
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
In the last few months, several people have given FlightGear permission to
use their external models under the GNU GPL (i.e. they can ultimately be
included w/ the fgfs base package). For those interested, I've collected
these and posted them here:
http://www.aae.uiuc.edu/m-selig/apasim/fgfs-mo
As some people know, we're using FlightGear in our Smart Icing System
research. Two recent papers (Aug 2002 and Jan 2003) on the subject
have been posted here: http://www.aae.uiuc.edu/m-selig/apasim.html
Regards,
Michael
**
Prof. Michael S. Selig
This could have application to aeroelastic effects?
http://www.gamespy.com/fargo/january02/jiggle/
Dave Culp
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
David Megginson writes:
> Different intersections and fixes server different purposes: the ones
> around KSFO are probably parts of various instrument approaches, and
> we would need most or all of them to simulate ATC or an
> approach-certified GPS. Just around Ottawa TCA, we have quite a few
> i
David Megginson writes:
> Sure -- I just dumped them there for now. Someone suggested earlier
> that we should modify FlightGear to read the DAFIFT format directly,
> and I think that's a good idea; at that point, the scripts would be
> obsolete.
I think this is a great idea ... that makes it eas
Here's a STAR into KSFO from the west, with lots of waypoints for
anyone who'd like to try out the new options and the new fix database:
http://edj.net/cgi-bin/echoplate.pl/echoplate.pl?Arrivals/MODESTO%20TWO.GIF
All of the five-letter names like "FAITH" and "GROAN" represent
waypoints that you
I've added four new command-line options to FlightGear:
--vor=ID
--ndb=ID
--fix=ID
--turbulence=NORM
The first three allow you to choose a reference point other than a
lat/lon or an airport for setting your starting position. For
example, to start 40 miles from the ART VOR on a heading o
Curtis L. Olson writes:
> I should also say this really cool to be able to incorporate this data
> directly. In terms of fixes though 72000 is an insane amount. For
> anyone wanting to actaully draw these on a map, there is going to have
> to be some sort of data reduction strategy. Does th
Curtis L. Olson writes:
> In the spirit of keeping code separate from data, would it make sense
> to put the scripts somewhere in the source tree? Maybe scripts/ or
> src/Navaids/?
Sure -- I just dumped them there for now. Someone suggested earlier
that we should modify FlightGear to read th
On Thu, 2003-02-20 at 06:34, Curtis L. Olson wrote:
> Tony Peden writes:
> > Huh!?! Except at high power settings and low speed in a twin,
> > engine failure should not cause a big upset. Even then, if you're
> > fairly quick to get on the rudder, it's generally very controllable
> > (or should b
Curtis L. Olson writes:
> David,
>
> In the spirit of keeping code separate from data, would it make sense
> to put the scripts somewhere in the source tree? Maybe scripts/ or
> src/Navaids/?
I should also say this really cool to be able to incorporate this data
directly. In terms of fixes thou
David,
In the spirit of keeping code separate from data, would it make sense
to put the scripts somewhere in the source tree? Maybe scripts/ or
src/Navaids/?
Curt.
David Megginson writes:
> I'm currently checking new files Navaids/default.nav.gz and
> Navaids/default.fix.gz into the base packa
I'm currently checking new files Navaids/default.nav.gz and
Navaids/default.fix.gz into the base package. These are generated
directly from DAFIF files (I've checked in my Perl scripts as well),
so they will be easy to keep up to date. The navaids file is a
moderate improvement, adding a couple o
Jim Wilson writes:
> Keep in mind I don't know how to fly, so get out your grains of salt :-)
>
> It seems to me I read somewhere that if you have any altitude at all (>1000ft)
> the thing to do is move all the levers up to full throttle. Cut the throttle
> on the engine you think is out, becaus
David Megginson <[EMAIL PROTECTED]> said:
> It's not mainly torque effects but the yawing moment that you have to
> worry about. Unless the plane is a centreline thrust, the good engine
> will be off to one side pulling that side forward and starting a
> yaw-induced roll (and if the bad one is no
* Richard Bytheway -- Thursday 20 February 2003 16:13:
> Once it has created the CVS directory in the root of the local copy,
> you can use the regular update command "cvs -z3 up -dP" to carry on
> getting more.
You do not really use "cvs -z3 up -dP" every time, do you? cvs has a
configuration fil
Curtis L. Olson writes:
If things turn u
> [1] Blue line is the speed below which the rudder cannot overcome
> the torque effects of a single engine and you can no longer have
> directional control.
I think that blue line is a bit higher than Vmc -- it's a speed where
a typical pilot (rather
> From: Danie Heath [mailto:[EMAIL PROTECTED]]
> Sent: 20 February 2003 2:26 pm
> To: [EMAIL PROTECTED]
> Subject: [Flightgear-devel] Re : More on CVS
>
>
> Hi all,
>
> I have some more questions on CVS. If I have the version 0.9.0 base
> package, and I run :
>
> cvs -z3 -d :pserver:[EMAIL PRO
Martin Spott wrote:
Erik Hofman <[EMAIL PROTECTED]> wrote:
The Seahawk does have textures, A-10 does not,
I did see (a white) A-10 in the past ...
Erik
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinf
Martin Spott writes:
> "Curtis L. Olson" <[EMAIL PROTECTED]> wrote:
>
> > Question, if you hack up the FG code to yank out all joystick support,
> > can you then get to the end and get a working FG build?
>
> I'll try my best as time permits. I spent quite a couple of hours compiling
> and testin
Erik Hofman <[EMAIL PROTECTED]> wrote:
> I was wondering, do any of you (using the latest plib CVS version) still
> see the A-10 aircraft model?
Yes, I do - but only on Linux. On IRIX I never saw any aircraft designed by
Lee Elliot, neither TSR.2, A-10 not B-52 or Seahawk.
> At first I tought t
"Curtis L. Olson" <[EMAIL PROTECTED]> wrote:
> Question, if you hack up the FG code to yank out all joystick support,
> can you then get to the end and get a working FG build?
I'll try my best as time permits. I spent quite a couple of hours compiling
and testing FlightGear, DRI, FreeTDS and othe
Hi,
I was wondering, do any of you (using the latest plib CVS version) still
see the A-10 aircraft model?
At first I tought this was a problem with the 3ds loader, but as it
happens, I can see the seahawk (which is also a 3ds model) model without
any problem?
Erik
Danie,
> it seems it downloads the whole base package through CVS. Is there a way
> I can update only the files that have changed or are new to the
> repository. Or will it by default download the whole base package the
This works the same way as described here for the code repository
http://w
Martin,
Our assumption has been that plib supports joysticks on every
platform, or hides the fact that it doesn't from the calling
application. Apparently neither is the case, at least for
solaris. :-(
Question, if you hack up the FG code to yank out all joystick support,
can you then get to the
Danie Heath wrote:
Hi all,
I have some more questions on CVS. If I have the version 0.9.0 base
package, and I run :
cvs -z3 -d :pserver:[EMAIL PROTECTED]:/home/cvsroot co fgfsbase
it seems it downloads the whole base package through CVS. Is there a way
I can update only the files that have ch
Tony Peden writes:
> Huh!?! Except at high power settings and low speed in a twin,
> engine failure should not cause a big upset. Even then, if you're
> fairly quick to get on the rudder, it's generally very controllable
> (or should be, anyway...)
A friend of mine has a Frasca sim (cockpit encl
Hi all,
I have some more questions on CVS. If I have the version 0.9.0 base
package, and I run :
cvs -z3 -d :pserver:[EMAIL PROTECTED]:/home/cvsroot co fgfsbase
it seems it downloads the whole base package through CVS. Is there a way
I can update only the files that have changed or are new to
Hi all,
I have some more questions on CVS. If I have the version 0.9.0 base
package, and I run :
cvs -z3 -d :pserver:[EMAIL PROTECTED]:/home/cvsroot co fgfsbase
it seems it downloads the whole base package through CVS. Is there a way
I can update only the files that have changed or are new to
Martin Spott wrote:
Somehow your compiler identifies itself as being a BSD platform. Instead
it should support the SOLARIS definition.
I think it's a different issue. Taken from current 'README':
PORTABILITY and DEPENDANCIES:
[...]
JS -- Currently Linux/Windows/BSD only.
from the README in
> Somehow your compiler identifies itself as being a BSD platform. Instead
> it should support the SOLARIS definition.
I think it's a different issue. Taken from current 'README':
PORTABILITY and DEPENDANCIES:
[...]
JS -- Currently Linux/Windows/BSD only.
plib-1.4.2 detects the presence of a
Curtis L. Olson writes:
> I guess I don't really know now that I think about it, but I always
> thought of windshear more as a singular event as you pass from one
> layer of wind to another rather than continuous high turbulence.
> If I'm wrong just ignore the rest of this.
Wind shear is any
Martin Spott wrote:
This should be fixed in the CVS version of plib. I've added a jsNone.cxx
file with empty functions for IRIX, Solaris and HP-UX.
I tried yesterday without success:
/usr/local/src/plib/src/js ~> g++ [...] -c -o js.o js.cxx
In file included from js.cxx:23:
js.h:40:32: machine
> This should be fixed in the CVS version of plib. I've added a jsNone.cxx
> file with empty functions for IRIX, Solaris and HP-UX.
I tried yesterday without success:
/usr/local/src/plib/src/js ~> g++ [...] -c -o js.o js.cxx
In file included from js.cxx:23:
js.h:40:32: machine/joystick.h: No s
Martin Spott wrote:
BTW, could you try this patch?
You know I'll try _every_ patch you want me to do so ;-)
Unfortunately this one does not do the trick,
Okay, I'm pretty sure now it's OpenGL shininess related, but I can't
think of a reason why.
:-(
Erik
_
> BTW, could you try this patch?
You know I'll try _every_ patch you want me to do so ;-)
Unfortunately this one does not do the trick,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
-
Danie Heath wrote:
Hi guys ...
I've actually got some free time to contribute ... is there a tutorial
on CVS anywhere I have basically no knowledge about it ..(*blush*
been coding for years without CVS)
This might be a good start:
https://sourceforge.net/docman/display_doc.php?docid=140
Martin Spott wrote:
Hello,
at least since 1.6.0 release (or earlier) PLIB appears not to build joystick
support on Solaris (not on the two machines I use to compile miscallaneous
stuff on). But FlightGear does not build with a PLIB without joystick
support:
Do you tend to wait until PLIB has j
Title: Message
Hi guys
...
I've actually got
some free time to contribute ... is there a tutorial on CVS anywhere
I have basically no knowledge about it ..(*blush* been coding for years without
CVS)
Kind Regards
Danie Heath
Software Integrator
RisC Com cc
+27 12 654 5100
083 412
Hello,
at least since 1.6.0 release (or earlier) PLIB appears not to build joystick
support on Solaris (not on the two machines I use to compile miscallaneous
stuff on). But FlightGear does not build with a PLIB without joystick
support:
/usr/local/src/FlightGear/src/Cockpit/built_in ~> g++ [...]
Martin Spott wrote:
On Wed, Feb 19, 2003 at 11:46:49PM +0100, Felix Kühling wrote:
On Wed, 19 Feb 2003 23:06:33 +0100 Martin Spott <[EMAIL PROTECTED]> wrote:
I just found out by accident how to get correct lightning in FlightGear with
current DRI drivers _and_ HW-TCL: Just look straight out
45 matches
Mail list logo
