Lee Elliott wrote:
"lowest I dared stall"? Like he had a choice?
Josh
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
On Tue, 6 Jun 2006 15:17:44 +0200, Arnt wrote in message
<[EMAIL PROTECTED]>:
> On Tue, 06 Jun 2006 11:57:43 +0200, Ralf wrote in message
> <[EMAIL PROTECTED]>:
>
> > Hi Arnt,
> >
> > Arnt Karlsen schrieb:
> > > ..in precisely that process, building a new GVAC Cape Verde out of
> > >
> > > yo
On Tuesday 06 June 2006 21:40, dene maxwell wrote:
> >Hi Dene,
> >
> >Just as well I said I would check :)
> >
> >Here are the _correct_ figures for the Comper Swift fitted
> > with the Pobjoy R seven cylinder radial engine (as modelled)
> >
> >Cruise: 120 mph (104.2 kt)
> >Max: 140 mph (121.6 kt
On Tuesday 06 June 2006 17:52, Curtis L. Olson wrote:
> Here's a question for all you amateur lawyers and GPL experts
> out there.
>
> Let's say that someone wants to create a proprietary aircraft
> within the FlightGear system, and then distribute a larger
> "system" that includes FlightGear + tha
Thank you Durk that would be much appreciated I haven't really
investigated the traffic manager system so know very little about(read
nothing) about it. I have plenty left to do with regard way points and xml
wrappers for the models, plus scenery work... great opportunity to learn
more
>Hi Dene,
>
>Just as well I said I would check :)
>
>Here are the _correct_ figures for the Comper Swift fitted with
>the Pobjoy R seven cylinder radial engine (as modelled)
>
>Cruise: 120 mph (104.2 kt)
>Max: 140 mph (121.6 kt)
>Landing/Stall 40 mph (34 kt)
>
>Not sure exactly what is meant by t
On Tuesday 06 June 2006 01:44, dene maxwell wrote:
> >On Sunday 04 June 2006 09:46, dene maxwell wrote:
> > > Hi Lee,
> > > I have some questions regarding the ComperSwift;
> > >
> > > I would like to use it in the FGLive-KOSH CD being put
> > > together by Arnt... i know under GPL I don't have to
Am Freitag, den 26.05.2006, 11:03 -0500 schrieb Curtis L. Olson:
> Martin Doege wrote:
>
> > However, calculating the tide for a given coordinate is probably the
> > lesser problem here (one can use xtide's output for reference, etc.)
> > My main issue is whether the visualization of the tidal
On Tue, 06 Jun 2006 11:52:27 -0500, Curtis wrote in message
<[EMAIL PROTECTED]>:
> Here's a question for all you amateur lawyers and GPL experts out
> there.
..also ask this at Groklaw, or shall I?
> Let's say that someone wants to create a proprietary aircraft within
> the FlightGear system,
Am Sonntag, den 28.05.2006, 14:42 +0200 schrieb Martin Doege:
> And since one of the major selling points of "Flight Simulator X" will
> be, at least according to the screenshots and trailers, the more
> realistic depiction of water in all its pixel shader-rendered glory,
> it would be great if the
Have to check the gpl.
Most address the issue of expansion of the code.
On Tue, 6 Jun 2006 2:02 pm, Curtis L. Olson wrote:
> Here's a question for all you amateur lawyers and GPL experts out
> there.
>
> Let's say that someone wants to create a proprietary aircraft within
> the
> FlightGear syst
AJ MacLeod wrote:
> On Monday 05 June 2006 20:25, Jakub Skibiński wrote:
>
>>I am newbie, so excuse my ignorance :)
>
> We are all ignorant about something. Some of us are very ignorant about most
> things :-)
>
>
>>Then I export my object to an '.ac' file and copy it into proper FG
>>scene
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oliver schrieb:
> Am Dienstag, den 06.06.2006, 19:48 +0200 schrieb Christian Mayer:
>
>> (*) I'm assuming that the proprietary aircraft doesn't derive of any
>> preexisting material (like textures) in FGFS.
>> This might become complex
>> with the cof
> In my view, the FlightGear GPL license covers our source
> code, but not content created with or used by that code
> (except for things like the base package which is explicitely
> licensed as GPL.)
In my mind, that is one reason why the approach taken by FlightGear and
associated projects lk
Am Dienstag, den 06.06.2006, 19:48 +0200 schrieb Christian Mayer:
> (*) I'm assuming that the proprietary aircraft doesn't derive of any
> preexisting material (like textures) in FGFS.
> This might become complex
> with the cofiguration XML files as they must be written from scratch
> IMHO.
But
On Tuesday 06 June 2006 18:52, Curtis L. Olson wrote:
> Here's a question for all you amateur lawyers and GPL experts out there.
>
> Let's say that someone wants to create a proprietary aircraft within the
> FlightGear system, and then distribute a larger "system" that includes
> FlightGear + that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Curtis L. Olson schrieb:
> Here's a question for all you amateur lawyers and GPL experts out there.
INAL but your case looks to me like that that person wants to use FGFS
just as an (complex) viewer/interpreter program for his proprietary
content(*).
* Melchior FRANZ -- Tuesday 06 June 2006 19:20:
> $ fgfs --aircraft=Citation-II \
> --prop:/sim/gui/style[1]/colors/splash-screen/{red,green}=0 \
^^^
I just changed the splash screen back to always use the color/font
values from style[0]. Making that styl
I've now converted all font-using parts in fgfs to use the
font-cache. And while I was at it, I also made some fonts
configurable:
panel
-
Here only fonts "typewriter" and "led" could be used in the
past. Now all texture fonts ($FG_ROOT/Fonts/*.txf) can be used.
This may lead to wrong alignmen
Here's a question for all you amateur lawyers and GPL experts out there.
Let's say that someone wants to create a proprietary aircraft within the
FlightGear system, and then distribute a larger "system" that includes
FlightGear + that aircraft.
In my view, the FlightGear GPL license covers our
* Martin Spott -- Tuesday 06 June 2006 15:26:
> Melchior FRANZ wrote:
> > I noticed that I don't/didn't have commit permission for that module.
> Why don't you say a single word ? People are standing on your feet to
> get their patches committed to main CVS, why don't you simply play the
> same g
Melchior FRANZ wrote:
> That's not necessarily the reason why contributions are sparse: last
> time I wanted to commit a minor documentation fix, I noticed that I
> don't/didn't have commit permission for that module. I lost interest
> after that and document my stuff in $FG_ROOT/Docs/.
Why don't
On Tue, 06 Jun 2006 11:57:43 +0200, Ralf wrote in message
<[EMAIL PROTECTED]>:
> Hi Arnt,
>
> Arnt Karlsen schrieb:
> > ..in precisely that process, building a new GVAC Cape Verde out of
> > your VMap1 data and then KOSH, I am trying to get TerraGear built:
> > http://80.239.32.252/terrorgear.c
* Martin Spott -- Monday 05 June 2006 23:58:
> Indeed, documentation is a weak point in the history of FlightGear
> development. Guess why ? Because writing documentation that you can
> rely on and which comes in a presentable outfit is unpleasant work,
That's not necessarily the reason why contri
Hi Dene,
It sounds like this would be a job for the traffic manager system, which
has more or less all the capabilities you describe (arrival, taxiway
following, wait until next flight, etc etc). I'll put some documentation
regarding the design of trafficmanager scripts once I'm back home (in
Hi all,
Problem: I have about 7 AI aircraft arriving at an airport at staggered
times... I want them to taxi off the runway - park and hold until all
aircraft haved handed and taxi-ed-. landing, taxi-ing, parking I think I
have sorted... any suggestions on how to make them hold?
Previous atte
Hi Arnt,
Arnt Karlsen schrieb:
> ..in precisely that process, building a new GVAC Cape Verde out of
> your VMap1 data and then KOSH, I am trying to get TerraGear built:
> http://80.239.32.252/terrorgear.configure.fails , and post with
> message-id: <[EMAIL PROTECTED]>.
I'll try to have a look
27 matches
Mail list logo
