David Megginson wrote:
> Erik Hofman writes:
>
> > I think we should define a fixed value for each flap position, otherwise
> > every module looking at the value has to support (>0 && <0.32 or >0.34
> > && <0.66 or >0.66 && <1.0)!
>
> How are you trying to use the information? There might
Jim Wilson writes:
> Does anyone know
>how I might be able to scale the cockpit to about 99.9% of its
>current size
>and maintain the same origin, etc? Using ac3D. I know you
>can resize with a
>mouse but I'd rather have something more precise. Of course
>I'm also thinking
>that I could m
Well I've been working on an interior for the U3-A for a while and have gotten
to the point where it isn't too embarassing to reveal what it looks like.
http://www.spiderbark.com/fgfs/c310-cockpit-1.png
http://www.spiderbark.com/fgfs/c310-cockpit-2.png
The cockpit was made by cutting a section
What version of Plib I have to use to compile FG and Simgear?
Marcio Shimoda
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
>On Behalf Of Cameron Moore
> What exactly do we want 1.0 to be? Here are some things I'd like to see
> in 1.0:
>
> - Runway lighting
> - Sane gear model in JSBSim
In work, as we "speak". Of course, this has been "in work" for months, and
is likely to continue to be for at least days if not wee
* [EMAIL PROTECTED] (Curtis L. Olson) [2002.04.19 21:24]:
> Anyone up for a 0.7.10 release sometime soon? If anyone wants a real
> time wasting discussion, what do people think about switching from
> 0.7.10, 0.7.11, 0.7.12, etc. to going 0.8, 0.9, 1.0, 1.1, 1.2, 1.3,
> that way it looks like our
Gents,
When making the latest CVS FGFS on Cygwin/Win2k, the following link error
occurs:
rc/WeatherCM/libWeatherCM.a
../../src/Input/libInput.a -lsgroute -lsgsk
y -lsgephem -lsgtiming -lsgio -lsgscreen-lsgmath -lsgbucket -lsgdebu
g -l
sgmagvar -lsgmisc -lsgxml -lsgserial
What this code says is "ignore anything after a hash ... unless we're compiling with
Microsoft C, in which case only ignore lines which start with a hash". Surely this
isn't intended. Curt checked in the change last May, but almost certainly didn't
invent it.
My tentative guess would be that
On Friday 19 April 2002 01:56 pm, you wrote:
> Erik Hofman wrote:
> > "FlightGear" flight simulator software for Linux and Windows
> > presented by: Andy Ross of the FlightGear project
>
> I'd just like to point out that this is all Alex's fault. I didn't
> have anything to do with it (other th
On Friday 19 April 2002 04:34 am, you wrote:
> Jim Wilson wrote:
> > As for the numbering, how about jumping to 0.8 and then continuing on as
> > we have? This will look like a pretty major update with the new models
> > and 3d internal view.
>
> I would think 0.8.0 is reserved for a *stable* rel
On Fri, 19 Apr 2002 12:44:14 -0400,
"Norman Vine" <[EMAIL PROTECTED]> wrote in message
<000701c1e7c1$712a8180$a300a8c0@nhv>:
> im Wilson writes:
> >
> >Norman Vine <[EMAIL PROTECTED]> said:
> >
> >> >That would do the trick. We'd need that anyway if we wanted to do
> >> >an approximate model of
On 19 Apr 2002 05:25:24 -0700,
Tony Peden <[EMAIL PROTECTED]> wrote in message
<1019219125.18988.16.camel@raptor>:
> On Thu, 2002-04-18 at 17:57, John Wojnaroski wrote:
> >
> > - Original Message -
> > From: John Wojnaroski
> > To: [EMAIL PROTECTED]
> > Sent: Thursday, April 18, 2002 3
Erik Hofman writes:
> I think we should define a fixed value for each flap position, otherwise
> every module looking at the value has to support (>0 && <0.32 or >0.34
> && <0.66 or >0.66 && <1.0)!
How are you trying to use the information? There might be an easier
approach.
All the best
Alex Romosan wrote:
>
> Julian Foad <[EMAIL PROTECTED]> writes:
>
> > Doesn't everyone have the same problem that I have: that after
> > re-building plib and/or SimGear, even after a one-file change, the
> > "make install" copies all of the header files to the install
> > directory, putting the
--- Erik Hofman <[EMAIL PROTECTED]> wrote:
> Andy Ross wrote:
> > Erik Hofman wrote:
> > > Well It's making it slightly difficult for the
> sound code. But I saw
> > > YASim does the same.
> >
> > These numbers are actually generated by the panel
> code, not the FDM.
> > Both FDMs just seek t
Julian Foad writes:
> "Curtis L. Olson" wrote:
> >
> > These are actually harmless error messages for lines that aren't even
> > executed by your version of automake, but the error checker isn't as
> > smart as it could be and doesn't know about automake conditionals.
>
> Are you referring to th
Alexander Kappes wrote:
>
> Thanks for the information Julian. Yes, I removed the old config.cache
> file.
>
> Did I get this right, the only way to make it work again is reverting to
> the old version?
The old version of the auto-tools will probably work, but I don't know for sure. And
I don
"Curtis L. Olson" wrote:
>
> These are actually harmless error messages for lines that aren't even
> executed by your version of automake, but the error checker isn't as
> smart as it could be and doesn't know about automake conditionals.
Are you referring to this message (running automake):
Marcel Wittebrood wrote:
...
> I installed cygwin, plib, simgear and flightgear.
...
> Something missing in this pdf is that one has to install
> Xfree86
> Metakit
You installed CygWin so you must be using MS Windows. The OpenGL components of MS
Windows and CygWin are enough; you do not need to
Alexander,
It's ok to be seeing this error messages about = vs +=. They are
annoying, but harmless.
Curt.
Alexander Kappes writes:
>
> Thanks for the information Julian. Yes, I removed the old config.cache
> file.
>
> Did I get this right, the only way to make it work again is reverting to
Erik Hofman wrote:
> "FlightGear" flight simulator software for Linux and Windows
> presented by: Andy Ross of the FlightGear project
I'd just like to point out that this is all Alex's fault. I didn't
have anything to do with it (other than saying "uh, ok", that is).
I haven't done much plann
Erik Hofman wrote:
> I think we should define a fixed value for each flap position,
> otherwise every module looking at the value has to support (>0 &&
> <0.32 or >0.34 && <0.66 or >0.66 && <1.0)!
They do anyway. Many aircraft don't even have fixed flap stations; a
common homebuilt mechanism
FYI.
The Linux Users' Group of Davis (LUGOD), will be holding a meeting on:
Tuesday
May 7th, 2002
6:30pm - 9:30pm
(Doors open at 6:00pm; please try to arrive on-time!)
The meeting will be held at:
Z-World, Inc.
2900 Spafford Street
Davis, CA 95616
(Near Sacramento)
Thanks; I think I'll do that.
- Julian
David Megginson wrote:
>
> Julian Foad writes:
>
> > Doesn't everyone have the same problem that I have: that after
> > re-building plib and/or SimGear, even after a one-file change, the
> > "make install" copies all of the header files to the install
Andy Ross wrote:
> Erik Hofman wrote:
> > Well It's making it slightly difficult for the sound code. But I saw
> > YASim does the same.
>
> These numbers are actually generated by the panel code, not the FDM.
> Both FDMs just seek the position to the specified control input. In
> this case, t
Julian Foad <[EMAIL PROTECTED]> writes:
> Doesn't everyone have the same problem that I have: that after
> re-building plib and/or SimGear, even after a one-file change, the
> "make install" copies all of the header files to the install
> directory, putting the current date stamp on them, even th
im Wilson writes:
>
>Norman Vine <[EMAIL PROTECTED]> said:
>
>> >That would do the trick. We'd need that anyway if we wanted to do an
>> >approximate model of a GPS some day.
>>
>> I don't understand what you mean by model a GPS
>> Are you are using 'GPS' to mean a 'muti-function' GPS receiver ?
Erik Hofman wrote:
> Well It's making it slightly difficult for the sound code. But I saw
> YASim does the same.
These numbers are actually generated by the panel code, not the FDM.
Both FDMs just seek the position to the specified control input. In
this case, the panel code adds or subtracts
Ok, I installed now the old version of automake (v 2.4) but I have still
problems running autogen
---
ltkappes/home/kappes/ltka/fgfs/SimGear> autogen.sh
Host info: Linux i686
automake: 1.4-p5 (14)
Running aclocal
Running autoheader
autoheader: simgear/simgear_config.h.i
> I used getstarted.pdf to learn to compile flightgear.
This is very nice to hear, so we know there really _are_ people reding our
manual ;-)
> Something missing in this pdf is that one has to install
> Xfree86
> Metakit
Hmmm, I believe it is _really_ obvious that yoy need X11 for FlightGear
> Anyone up for a 0.7.10 release sometime soon?
I wouldn't object a 0.7.10 release as long as where were at least two or
three weeks for fixing obvious known bugs that prevent users from using
functionality that is _supposed_ to be usuable right now (see my posting on
the Beech99).
In the meantim
Norman Vine <[EMAIL PROTECTED]> said:
> >That would do the trick. We'd need that anyway if we wanted to do an
> >approximate model of a GPS some day.
>
> I don't understand what you mean by model a GPS
> Are you are using 'GPS' to mean a 'muti-function' GPS receiver ?
>
Support for a "NRST" a
Hi,
> > > Bottom line question for the FDM' rs: Would you take a few moments
> > > to comment/explain how your models handle the various airspeeds.
> >
Just a quick thank you for the info put.
To make the FG/OpenGC interface effective will require a little handshaking
on both ends to sync up.
Jim Wilson writes:
>
>Norman Vine <[EMAIL PROTECTED]> said:
>
>> Perhaps tie'ing it to the current waypoint makes sense .. hmmm
>>
>
>Yes, but I'd probably want to wait until I was within a few
>kilometers of the "current" waypoint before switching.
or perhaps when the 'current waypoint' i
Tony Peden wrote:
> That's normal from JSBSim.
>
> Is it causing you some difficulty?
Well It's making it slightly difficult for the sound code.
But I saw YASim does the same.
I seem to remember this was {0.0 0.32 0.66 1.0} for both up and down.
Anyhow, I'll adjust the sound files for this.
E
Thanks for the information Julian. Yes, I removed the old config.cache
file.
Did I get this right, the only way to make it work again is reverting to
the old version?
Cheers Alexander
On Fri, 19 Apr 2002, Julian Foad wrote:
> configure.in includes a fix to make it work with both versions of t
Hello alltogether,
would you mind changing this back to the previous behaviour which means not
to crash if there's no model description. Unfortunalety I've been off scene
for a few days so it's not quite clear to me when the change happened.
I was trying the Beech99 in the hope to see a working g
That's normal from JSBSim.
Is it causing you some difficulty?
--- Erik Hofman <[EMAIL PROTECTED]> wrote:
>
>
> Hi,
>
> When checking the flap postions I notices they
> return to another
> postition then they came from:
>
> down: 0.0 --> 0.34 --> 0.68 --> 1.0
> up: 1.0 --> 0.66 --> 0.32
Hi,
When checking the flap postions I notices they return to another
postition then they came from:
down: 0.0 --> 0.34 --> 0.68 --> 1.0
up: 1.0 --> 0.66 --> 0.32 --> 0.0
Is this the default for the c172?
Erik
___
Flightgear-devel mailing lis
Norman Vine <[EMAIL PROTECTED]> said:
> Perhaps tie'ing it to the current waypoint makes sense .. hmmm
>
Yes, but I'd probably want to wait until I was within a few kilometers of the
"current" waypoint before switching.
> Also The tile_cache mechanism could be extended to keep a list of
>
Curtis L. Olson writes:
>
>Jim Wilson writes:
> Possibly we can move the tower during teleports though...hmmm.
+10
>If we came up with some code to find the closest airport to a lat/lon,
>then we could write a function to move the tower view to the closest
>airport, and bind a key to it. Or p
Dear developers,
I am still in the process of becoming a developer. I installed cygwin,
plib, simgear and flightgear.
I used getstarted.pdf to learn to compile flightgear.
Something missing in this pdf is that one has to install
Xfree86
Metakit
For simgear one has to install the latest versi
"Curtis L. Olson" <[EMAIL PROTECTED]> said:
> If we came up with some code to find the closest airport to a lat/lon,
> then we could write a function to move the tower view to the closest
> airport, and bind a key to it. Or perhaps allow the user to specify
> which airport to move the tower too
Jim Wilson writes:
> Yes, thats right, its looking at KABE directly. You will also note that the
> tower view stays where it was even if you fly far away. Currently the tower
> location is just an arbitrary setting the is based on the starting location,
> until we have some real tower locations
Yes, thats right, its looking at KABE directly. You will also note that the
tower view stays where it was even if you fly far away. Currently the tower
location is just an arbitrary setting the is based on the starting location,
until we have some real tower locations in there. Possibly we can
Hello,
Just got current CVS of all packages around 07:30 4/19 EDT and compiled
without errors. Starting the default model, I am sitting at KSFO in the
dark (as expected). Change environment airport to KABE and have a sunny
day with proper hills in the distance. External chase view also cor
Hello,
Just got current CVS of all packages around 07:30 4/19 EDT and compiled
without errors. Starting the default model, I am sitting at KSFO in the
dark (as expected). Change environment airport to KALE and have a sunny
day with proper hills in the distance. External chase view also
On Thu, 2002-04-18 at 21:02, John Wojnaroski wrote:
> Hi,
>
> > The FDM interface treats CAS and IAS identically -- the calibration
> > error, as you point out, is poorly defined and will vary between
> > installations. All FDMs simply report a single "calibrated airspeed"
> > value; if other co
On Thu, 2002-04-18 at 18:23, Andy Ross wrote:
> John Wojnaroski wrote:
> > Indicated Airspeed (IAS)
> > Calibrated Airspeed (CAS)
> > Next comes Equivalent Airspeed (EAS)
> > Finally TAS
> >
> > Bottom line question for the FDM' rs: Would you take a few moments
> > to comment/explain how yo
On Thu, 2002-04-18 at 17:57, John Wojnaroski wrote:
>
> - Original Message -
> From: John Wojnaroski
> To: [EMAIL PROTECTED]
> Sent: Thursday, April 18, 2002 3:02 PM
> Subject: Airspeeds?
>
>
> Hi,
>
> On the subject of airspeeds:
>
> Indicated Airspeed (IAS) is calculated based on th
David Megginson <[EMAIL PROTECTED]> said:
> Curtis L. Olson writes:
>
> > Anyone up for a 0.7.10 release sometime soon?
>
> Yes, now (or as soon as practicable). While there will always be new
> features to add, I think it's starting to get silly that we're not at
> 1.0 yet (or soon) -- the p
Curtis L. Olson writes:
> Anyone up for a 0.7.10 release sometime soon?
Yes, now (or as soon as practicable). While there will always be new
features to add, I think it's starting to get silly that we're not at
1.0 yet (or soon) -- the program, as-is, is already very suitable for
VFR training,
Curtis L. Olson wrote:
> This is off the top of my head with a healthy mix of speculation.
> But, I believe you can override the 'install' command in the
> Makefiles. Often it is just "cp" or the is often an actual "install"
> program or similar "install.sh" script. This means that in theory,
>
Jim Wilson wrote:
> As for the numbering, how about jumping to 0.8 and then continuing on as we
> have? This will look like a pretty major update with the new models and 3d
> internal view.
I would think 0.8.0 is reserved for a *stable* release. Although much
has changed in the recent past, ch
54 matches
Mail list logo
