...code last weekend, and did this:
http://www.cs.yorku.ca/~cs233144/PROTOTYPE.jpg
this:
http://www.cs.yorku.ca/~cs233144/FINNAIR.jpg
and this:
http://www.cs.yorku.ca/~cs233144/KLM.jpg
I am happy to report that the multiple-livery system works great and didn't
give me any trouble. However, I do
Curtis L. Olson wrote:
If we put banner adds on our web site, and one of our visiters clicks
through and buys something from this company (being referred from our
site) then we would get a 10% commission from the sale.
I don't have any objections agains this idea. I just a bit unsure if
Curt wrote
Sent: 16 July 2004 16:34
To: FlightGear developers discussions
Subject: [Flightgear-devel] Next release of FlightGear
I've started doing some of the pre-release work for FlightGear-0.9.5
(which is the next release.) That means I'd like to do our official
next release in the
Vivian Meazza wrote:
The Cygwin build of FGFS-cvs appears still to have a problem with the
scenery path.
I've downloaded 0.9.5 scenery via Terrasync into /FlightGear/scenery
This works:
--fg-scenery=/FlightGear/scenery
as does this:
--fg-scenery=/FlightGear/data/scenery
this
Frederic Bouvier wrote :
Durk Talsma wrote:
The new scenery (the 0.9.5 release, downloaded using terrasync)
Cheers,
Durk
On Sunday 18 July 2004 23:08, Frederic Bouvier wrote:
Durk Talsma wrote:
Ehm, to both of you, was this using the real-weather option turned
on
or
Fred wrote
Sent: 19 July 2004 10:20
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Next release of FlightGear
Vivian Meazza wrote:
The Cygwin build of FGFS-cvs appears still to have a problem with the
scenery path.
I've downloaded 0.9.5 scenery via
I updated plib/simgear/flightgear/base from CVS. Built plib and simgear. Checked the
dates
on the libs - they're all current. The sources were updated from CVS. I tried building
FlightGear and got this:
...
checking for simgear/version.h... yes
checking for simgear 0.3.6 or newer... 0.3.6 or
Hi
While trying to correctly tweak the FDM and PID controllers for the L1011-500,
i though it would be really nice to have some sort of standalone app running
on a remote machine, plotting selected property(es) oscilloscope style (in
my case, i'd like to make it run in my old P133).
There
Jon Berndt wrote:
I updated plib/simgear/flightgear/base from CVS. Built plib and simgear. Checked the
dates
on the libs - they're all current. The sources were updated from CVS. I tried
building
FlightGear and got this:
...
checking for simgear/version.h... yes
checking for simgear
What is the content of /usr/local/include/simgear/version.h ? ( or wherever you
installed SimGear ? )
-Fred
The version looks right, I think (but the $Id date is way off):
// $Id: version.h.in,v 1.1.1.1 2002/09/07 02:58:19 curt Exp $
#ifndef _SIMGEAR_VERSION_H
#define
Jon Berndt wrote:
What is the content of /usr/local/include/simgear/version.h ? ( or wherever you
installed SimGear ? )
-Fred
The version looks right, I think (but the $Id date is way off):
// $Id: version.h.in,v 1.1.1.1 2002/09/07 02:58:19 curt Exp $
Don't llok at the $Id, it is
The version looks right, I think (but the $Id date is way off):
// $Id: version.h.in,v 1.1.1.1 2002/09/07 02:58:19 curt Exp $
Don't llok at the $Id, it is the Id of version.h.in that is an old template but
version.h is generated every time you run configure.
Correct. I was just
#ifndef _SIMGEAR_VERSION_H
#define _SIMGEAR_VERSION_H
#define SIMGEAR_VERSION 0.3.6-pre1
...
It seems as though, then, that my installation of FlightGear is not looking for
the
correct pre-release version of simgear, but I don't know why. I've updated it
from CVS.
How do I insert a disturbance through a command
line call. I'd like to test my adaptive autopilot, and its
robustness, by inserting some wind/disturbance at a specified time.
Should this be done through the command line?
thanks
___
Jon Berndt wrote:
Sent: 19 July 2004 15:32
To: FlightGear developers discussions
Subject: RE: [Flightgear-devel] Difficulty with building under Cygwin
The version looks right, I think (but the $Id date is way off):
// $Id: version.h.in,v 1.1.1.1 2002/09/07 02:58:19 curt Exp $
Try including the command: --with-simgear=PATH, whne you are
using ./configure. PATH is the location of SimGear.
Regards,
Ampere
On July 19, 2004 09:49 am, Jon Berndt wrote:
It seems as though, then, that my installation of FlightGear is not looking
for the correct pre-release version of
Ampere K. Hardraade wrote:
Try including the command: --with-simgear=PATH, whne you are
using ./configure. PATH is the location of SimGear.
Regards,
Ampere
On July 19, 2004 09:49 am, Jon Berndt wrote:
It seems as though, then, that my installation of FlightGear is not looking
for the correct
Speaking of controls, do they currently support key stroke inputs?
Regards,
Ampere
On July 18, 2004 04:02 pm, Remy Villeneuve wrote:
so that within 10 pixels it is incremented by 1, but if you go away from
that, at a 110 pixels it would be incremented by 10 for each cycles, and
at a maximum
On Mon, 19 Jul 2004 03:45:43 -0400
Ampere K. Hardraade [EMAIL PROTECTED] wrote:
...code last weekend, and did this:
http://www.cs.yorku.ca/~cs233144/PROTOTYPE.jpg
this:
http://www.cs.yorku.ca/~cs233144/FINNAIR.jpg
and this:
http://www.cs.yorku.ca/~cs233144/KLM.jpg
Cool.
I have what's
How do I insert a disturbance through a command line call. I'd like to
test my adaptive autopilot, and its robustness, by inserting some
wind/disturbance at a specified time. Should this be done through the
command line? thanks
You can open up a dialog using menu items: Weather |
how about through a command line?
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Jon Berndt wrote
Sent: 19 July 2004 15:32
To: FlightGear developers discussions
Subject: RE: [Flightgear-devel] Difficulty with building under Cygwin
The version looks right, I think (but the $Id date is way off):
// $Id: version.h.in,v 1.1.1.1 2002/09/07 02:58:19 curt Exp $
On Mon, 19 Jul 2004 18:07:43 +0100
Vivian Meazza [EMAIL PROTECTED] wrote:
I've just downloaded the current cvs version of SimGear and
FlightGear. They both compile under Cygwin straight out of the box.
I would suppose that you have a problem with your path.
Possibly, but I am using the same
Well, as you have pointed out, there is the issue of ease-of-maintenance.
Having part of the fuselage in texture A, part of it in texture B, and the
rest of it in texture C won't make the life of the textuer any easier. For
me, there is also the issue of ease-of-creation: arranging components
sonny hammaker wrote:
how about through a command line?
start fgfs with the telnet daemon, that way it should be possible to
easily access most of its internal properties via a simple telnet
client - so you could then easily:
cd environment/turbulence
at set the corresponding values there.
sonny hammaker wrote:
how about through a command line?
--turbulence=value
--wind=wind-desc-with-gust
--random-wind
see fgfs --help --verbose
-Fred
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
Frederic Bouvier wrote:
sonny hammaker wrote:
how about through a command line?
--turbulence=value
--wind=wind-desc-with-gust
--random-wind
see fgfs --help --verbose
but these aren't meant for runtime control of the environment, are they ?
Or is there some kind of IPC between running
Boris Koenig wrote:
Frederic Bouvier wrote:
sonny hammaker wrote:
how about through a command line?
--turbulence=value
--wind=wind-desc-with-gust
--random-wind
see fgfs --help --verbose
but these aren't meant for runtime control of the environment, are they ?
Or is there some kind of IPC
Nice!
I just downloaded your update and modified the model files to include the 747
CRT displays to the cockpit. I've also changed my KLM traffic patterns to use
the new livery instead.
Cheers,
Durk
___
Flightgear-devel mailing list
[EMAIL
Sorry for joining this thread lately...
As suggested by serveral people if only GPS data are available (ie:
Lat/Long, Ground Speed, Ground Track and rough altitdue.)
For pitch restitution :
With two dated altitude data, we can compute vertical speed.
From vertical speed and ground speed, we can
This is pretty:
http://www.boeing.com/news/releases/2004/photorelease/q3/pr_040719g.html
Might be nice to see this on some of the FlightGear Boeing planes (the test ones ;^)
Jon
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
Is there a scenery diff somewhere from 0.9.4 to 0.9.5-pre1,
I don't really want to download the whole 80+Mb package again...
Birger
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
This is a case where you really should go look at the end of the config.log
file to see *exactly* why the version check is failing.
Curt.
What should one look for in config.log? There appears to be several problems. The
following shows what the worst problem is, however (but I'm not sure how
My SimGear build was not completing. I think it has something to do with the move to
OpenAL. As I was building simgear I got this:
...
checking for library containing alGenBuffers... -lopenal32
checking for library containing alutInit... no
...
Later on, I get this:
g++ -D_REENTRANT
34 matches
Mail list logo
