-Original Message-
From: Mally [mailto:[EMAIL PROTECTED]
Sent: 13 February 2004 7:12 pm
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] XML SCripting
You may not be a patent lawyer, but that's a convincing
sounding explanation
of
the legal position.
Richard Bytheway wrote:
There was a comment on the /. discussion on this subject that the examiners have a quota of patents applications to process each week, so there is little incentive to dig too deep. I hope this is not the case, but it might be.
Ok. But since the patent request was filed
* Frederic Bouvier -- Monday 16 February 2004 05:53:
You must have screwed memory and map pointers with your mods. Let's wait
Melchior and its Valgrind analysis to see if it's not already a problem
in FG.
Valgrind has'n found anything. No reads from uninitialized memory, no
writes to
Richard
Thanks for that. (Puts a new twist on the phrase patently obvious) :-(
Mally
- Original Message -
From: Richard Bytheway [EMAIL PROTECTED]
To: FlightGear developers discussions [EMAIL PROTECTED]
Sent: Monday, February 16, 2004 9:11 AM
Subject: Patents [OT] (Was: RE:
Valgrind has'n found anything. No reads from uninitialized memory, no
writes to unallocated memory etc. (But I should really have a major
valgrind session again. There are a couple of little problems at other
places that crept in after the last one.)
m.
Just a prob with .Net 2003 ?? Sigh...Does
Jon Berndt [EMAIL PROTECTED] wrote:
Adopted to the current case this means: The longest distance from
whichever CG you take to the edges of the aircraft is _always_ smaller
than the longest distance from the nose to arbitrary edges. This
results in smaller relative 'errors' in case some
Frederic Bouvier wrote:
Could someone with CVS write access add the -kb sticky tag to these files :
data/Aircraft/Instruments-3d/adf/adf.rgb
data/Aircraft/Instruments-3d/ai/ai.rgb
data/Aircraft/Instruments-3d/alt/alt.rgb
data/Aircraft/Instruments-3d/asi/asi.rgb
I know that the recent long debates on issues like the Visual Reference
Point for outside views have been driving many people crazy, and have caused
some tempers to flare, but there's also a positive side: FlightGear now has
enough developers who know the code that we *can* have long debates
Martin Spott wrote:
When you take the 'philosophical' route, I agree - in almost _every_
situation it's a big fault to delete detail/resolution from your raw
data.
On the other hand: 8 kHz, 8 bit is not that bad. German ISDN telephony
has this resolution and to my impression the audible quality
Erik Hofman [EMAIL PROTECTED] wrote:
Martin Spott wrote:
On the other hand: 8 kHz, 8 bit is not that bad. German ISDN telephony
has this resolution and to my impression the audible quality is far
better than usual radio in an aircraft ;-)
ISDN uses the uLaw compression which means,
Hi,
After reading that OpenGL would be optimized on IRIX when using display
lists I decided to do some trial runs with FlightGear. Unfortunately the
exact same thing that happened to VBO's (odd colors when using VBO's)
also happens to DList (at least on my O2).
Does anyone have a formula handy for calculating the flight path of an
aircraft in true degrees (direction of travel as opposed to the airframe
heading)? My guess is that it'd be a matter of doing something with the
lon/lat from the previous frame. Maybe there's something simpler with the
--- Jim Wilson [EMAIL PROTECTED] wrote:
Does anyone have a formula handy for calculating the flight path of
an
aircraft in true degrees (direction of travel as opposed to the
airframe
heading)? My guess is that it'd be a matter of doing something with
the
lon/lat from the previous frame.
Jim Wilson wrote:
Does anyone have a formula handy for calculating the flight path of an
aircraft in true degrees (direction of travel as opposed to the airframe
heading)? My guess is that it'd be a matter of doing something with the
lon/lat from the previous frame. Maybe there's something
On Mon, 16 Feb 2004 19:57:37 +0100,
Erik Hofman [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]:
Hi,
After reading that OpenGL would be optimized on IRIX when using
display lists I decided to do some trial runs with FlightGear.
Unfortunately the exact same thing that happened to
On Mon, 16 Feb 2004 20:28:49 -, Jim Wilson [EMAIL PROTECTED] wrote:
Does anyone have a formula handy for calculating the flight path of an
aircraft in true degrees (direction of travel as opposed to the airframe
heading)? My guess is that it'd be a matter of doing something with the
lon/lat
Vivian Meazza wrote:
I've just done some proof-of-principle work on drop tanks with
YASim. I set up some weight elements for the pylons and for the dry
weight of the tanks, and some fuel tanks to match.
[...]
However, the bad news is that I can't set _one_ of the drop tank
weights to zero
Vivian Meazza [EMAIL PROTECTED] writes:
In which case we could standardise, if standardise we must for minor
controls, on j/J/CTRL J for jettison, and k/K for spoilers. We will
soon run out of keys unless we are careful.
any capital letter requires both hands so it makes it hard to use it
* Vivian Meazza -- Tuesday 17 February 2004 00:11:
In which case we could standardise, if standardise we must for minor
controls, on j/J/CTRL J for jettison, and k/K for spoilers. We will soon run
out of keys unless we are careful.
spoiler bindings are now (AFAIK) only used by UIUC aircrafts.
Roy Vegard Ovesen wrote:
The GPS instrument does this in the same way as you suggest (as do most
real gps devices), take a look at the gps.cxx source file to see the
details. I believe the actual formula can be found someplace in SimGear.
But if you are just looking for the true flight path
Melchior FRANZ [EMAIL PROTECTED] writes:
spoiler bindings are now (AFAIK) only used by UIUC aircrafts.
There's also Ctrl-B for speed brake bindings. They seem to be used
for one and the same thing on airliners, which is, again, a bad
thing.
spoilers are devices designed to reduce lift and
Alex Romosan wrote:
Vivian Meazza [EMAIL PROTECTED] writes:
In which case we could standardise, if standardise we must for minor
controls, on j/J/CTRL J for jettison, and k/K for spoilers. We will
soon run out of keys unless we are careful.
any capital letter requires both hands so it
On Monday 16 February 2004 22:12, Martin Spott wrote:
Vivian Meazza [EMAIL PROTECTED] wrote:
However, the bad news is that I can't set _one_ of the drop tank weights
to zero (odd that), and none of the tank fuel contents. I was planning to
use keys j/J/CTRLJ for jettison inner/outer/all.
On Monday 16 February 2004 23:28, Alex Romosan wrote:
Vivian Meazza [EMAIL PROTECTED] writes:
In which case we could standardise, if standardise we must for minor
controls, on j/J/CTRL J for jettison, and k/K for spoilers. We will
soon run out of keys unless we are careful.
any capital
On Tuesday 17 February 2004 00:25, Alex Romosan wrote:
Melchior FRANZ [EMAIL PROTECTED] writes:
spoiler bindings are now (AFAIK) only used by UIUC aircrafts.
There's also Ctrl-B for speed brake bindings. They seem to be used
for one and the same thing on airliners, which is, again, a bad
David Megginson said:
Roy Vegard Ovesen wrote:
The GPS instrument does this in the same way as you suggest (as do most
real gps devices), take a look at the gps.cxx source file to see the
details. I believe the actual formula can be found someplace in SimGear.
But if you are just
On Monday 16 February 2004 23:46, Melchior FRANZ wrote:
And it's far easier to
remember that g is for gear up and G for gear down etc. than
to use two completely unrelated keys.
One question, why don't we use lower case g key for gear up and for gear
down?
Why do we also need the upper G
Jim Wilson wrote:
Any objection to my putting that on the bus in generic-electrical.xml?
Go nuts (that's Canadian for go right ahead).
All the best,
David
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
Norman Vine wrote:
I hope that you take into consideration that that is a *very* expensive
function to call !
I think it's on a 1 hz update, but I'd have to go back into the code.
All the best,
David
___
Flightgear-devel mailing list
[EMAIL
Jim Wilson writes:
David Megginson said:
Roy Vegard Ovesen wrote:
The GPS instrument does this in the same way as you suggest (as do most
real gps devices), take a look at the gps.cxx source file to see the
details. I believe the actual formula can be found someplace in
30 matches
Mail list logo
