Why add auto-generated files to the CVS repository?
I think it is generally considered (by other open source projects
anyway) a bad idea to include auto-generated files in CVS. Sometimes,
people will regenerate these files using their local tools, and then
they'll have 'cvs diff' produce crap. De
Phew! :-)
Did we get anywhere with adding cvs diff output to the cvslogs messages,
as per SourceForge? That would have made it a bit more obvious.
--
Ross
On Tue, 2001-12-11 at 21:43, Curtis L. Olson wrote:
> Ross,
>
> I believe what David was doing was adding the autogenerated files to
> the
Ross Golder writes:
> Did we get anywhere with adding cvs diff output to the cvslogs messages,
> as per SourceForge? That would have made it a bit more obvious.
I think I'm losing email over the side of the bucket ... can someone
send a proper script to me directly?
Thanks,
Curt.
--
Curtis Ols
On Thu, 2001-12-13 at 03:48, David Megginson wrote:
>
> Date: Wednesday December 12, 19101 @ 21:48
> Author: david
>
Wow! What're things like in the year 19101, David? Has FlightGear 1.0
been release yet :o) ?
--
Ross
___
Flightgear-devel ma
Ok, thanks, this should now be installed for FlightGear and SimGear.
I'll work on TerraGear at some future time when I get a chance.
Curt.
Ross Golder writes:
> This is how it appears to be set up for me:
>
> In CVSROOT/loginfo, add the line :
>
> DEFAULT $CVSROOT/CVSROOT/syncmail %{sVv}
> [E
David,
This is going to mess up rendering of distant mountains for people
with voodoo cards (i.e. 16 bit buffers).
Depth buffer precision is *very* sensitive to the near clip plane
distance:
http://www.sjbaker.org/steve/omniv/love_your_z_buffer.html
I'm really nervous about forcing this do
> David Megginson writes:
> > Changed the near clip plane to 0.1f regardless. Previously, it jumped
> > to 10m after takeoff, but that doesn't really make sense any more,
> > especially if models are going to have interior views. Is there any
> > real saving in pushing the near plane out anyway?
Alex Perry writes:
> Putting the clip plane at 0.1 is an easy way to stop me doing demos of FGFS.
> I don't _have_ a machine with better than 16 bit depth buffering, and the
> notebook that I do most of the demos with cannot of course be upgraded.
I understand. How does everything look with
> Or just turn the depth buffer off for the cockpit and sort the
> geometry; for most cockpit layouts, this should be pretty feasible.
> It won't work if the cockpit has moving parts (yokes or whatnot) that
> obscure other pieces.
Even if they obscure, it is only a problem if they swap places so
David Luff writes:
> Alex Perry writes:
> > and for the latter you're in ground haze in any case.
> You Californians speak for yourselves!
> [EMAIL PROTECTED]
Ya see, here the temperature is _above_ freezing and _not_ raining
at the same time 8-). I'll take poor visibility over days of drizzle.
> You likely don't notice any of this if you
> are running a card with a 32bit depth buffer (i.e. geforce.)
Don't worry Curt, leave the change in, I don't see the problem on 16 bit ...
Loading tile /usr/local/lib/FlightGear/Scenery/w120n30/w118n32/1023667
ESC[1mESC[4mJSBSim Flight Dynamics
On Tue, 2002-03-05 at 18:16, Alex Perry wrote:
> David Luff writes:
> > Alex Perry writes:
> > > and for the latter you're in ground haze in any case.
> > You Californians speak for yourselves!
> > [EMAIL PROTECTED]
>
> Ya see, here the temperature is _above_ freezing and _not_ raining
> at the
Alex,
Try doing a make clean inside JSBSim and then rebuild everything.
Curt.
Alex Perry writes:
> > You likely don't notice any of this if you
> > are running a card with a 32bit depth buffer (i.e. geforce.)
>
> Don't worry Curt, leave the change in, I don't see the problem on 16 bit ...
>
> > You likely don't notice any of this if you
> > are running a card with a 32bit depth buffer (i.e. geforce.)
>
> Don't worry Curt, leave the change in, I don't see the problem on 16 bit
...
>
>
> Loading tile /usr/local/lib/FlightGear/Scenery/w120n30/w118n32/1023667
> ESC[1mESC[4mJSBSim Fl
> > 13971 Segmentation fault
> [you *are* joking, aren't you?!?!]
Err, no. Sorry. Curt suggest I recompile ... in progress ...
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
> > > 13971 Segmentation fault
> > [you *are* joking, aren't you?!?!]
> Err, no. Sorry. Curt suggest I recompile ... in progress ...
Ok, that fixed it (dunno what it was).
I'm getting zbuffer fighting in the distance a little bit, but it's minor
compared to the junk you get when cloud layers
Bernie Bright wrote:
> "Curtis L. Olson" wrote:
>
>>Update of /var/cvs/FlightGear-0.7/FlightGear/src/Cockpit
>>In directory seneca:/tmp/cvs-serv20681
>>
>>Modified Files:
>>panel_io.cxx
>>Log Message:
>>Sgi doesn't define the != operator for string != char[] so we need to cast
>>the char
> Modified Files:
> fg_props.cxx
> Log Message:
> More work on saving and restoring flights.
> Restoring a flight is not
> working in a running FlightGear session because of
> JSBSim trim-routine
> problems,
What is it doing (or not, as the case may be)?
* [EMAIL PROTECTED] (Curtis L. Olson) [2002.03.21 08:58]:
> Index: panel_io.cxx
> ===
> RCS file: /var/cvs/FlightGear-0.7/FlightGear/src/Cockpit/panel_io.cxx,v
> retrieving revision 1.36
> retrieving revision 1.37
> diff -C2 -r1.36 -r
Are you using scenery_center or next_scenery_center? It's been so
long I don't recall all the resoning, but next_scenery_center was made
available to the view manager so it can get the view position correct
even when we cross a tile boundary and the offsets change.
Regards,
Curt.
Jim Wilson wr
Hmmm, The bigger airports tend to use the same frequency for each end
of their runways. So this change will probably break half the
approaches at the major airports (KLAX, KMSP, KORD, KDFW, etc.)
I made a change to return the matching station that points most
directly at us. This should be the
* [EMAIL PROTECTED] (Curtis L. Olson) [2002.05.16 23:06]:
> Update of /var/cvs/FlightGear-0.7/FlightGear/src/Main
> In directory seneca:/tmp/cvs-serv26528/src/Main
>
> Modified Files:
> options.cxx
> Log Message:
> Bernie Bright:
> To make MSVC happy it appears we need backslashes on strin
"Curtis L. Olson" <[EMAIL PROTECTED]> writes:
> Originally this was changed to something like:
>
>cout << "usage:
>
> Nicely formatted text
>that will look
> exactly like it is entered
> here when
>
>it is displayed by the program.
> This is very 'pretty' to be able
> to do
[EMAIL PROTECTED] wrote:
>
> This can be done portably using the standard "string concatenation" feature of
> the language. The above would look like the following and likely work with
> any reasonably modern compiler (this string concatenation feature did not
> exist in K&R C but did beginning
Christian Mayer wrote:
>
> Note: You 2nd version does *not* use the string concatenation.
>
> The 2nd version boils down to the very C++ dependant
>
> operator<<(operator<<(operator<<(cout, "usage"),endl),...);
>
Yes, it does. What point are you trying to make by saying "very C++ dependant"?
Julian Foad wrote:
>
> Christian Mayer wrote:
> >
> > Note: You 2nd version does *not* use the string concatenation.
> >
> > The 2nd version boils down to the very C++ dependant
> >
> > operator<<(operator<<(operator<<(cout, "usage"),endl),...);
> >
>
> Yes, it does. What point are you trying t
Christian Mayer wrote:
>
> I wanted to point out the very big (internal) differnce of the ANSI C
> style
>
> "string1" "string2"
>
> THat ends up as "string1string2" in a normal array of char
>
> vs.
>
> The C++ way:
>
> cout << "string1" << "string2"
>
> wich uses the operator<<() method.
> So in the end, I'm not sure which is better. They each have their
> pluses ...
Lets move it over to an XML file ...
Erik
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Was this a mistake?
Best,
Jim
[EMAIL PROTECTED] said:
> Date: Tue Jun 11 13:06:29 EDT 2002
> Author: cvsroot
>
> Update of /home/cvsroot/FlightGear/FlightGear/Aircraft
> In directory bitless:/tmp/cvslck/cvs-serv8782/Aircraft
>
> Modified Files:
> X15-set.xml
> Log Message:
> Command l
On Tuesday 11 June 2002 1:24 pm, Jim Wilson wrote:
> Was this a mistake?
Yes, I committed it accidentally while trying to get options.xml committed.
Can you back it out for me? Gotta run
>
> Best,
>
> Jim
>
> [EMAIL PROTECTED] said:
> > Date: Tue Jun 11 13:06:29 EDT 2002
> > Author: cvsroot
> >
David,
It looks like this may have helped crosswind handling on the ground
considerably. The relatively small amount of testing I've done shows
that the c172 will sit still in up to a 15 knot crosswind and turn very
slowly in 20 knots.
Let us know what you think.
On Tue, 2002-09-17 at 16:05,
On Wed, 2002-09-18 at 17:48, Jon Berndt wrote:
> > Is there some reasoning behind setting the steering gains according to
> > the brake selection? This makes no sense to me. It looks to me like
> > their needs to be a separate steering selection (or just specify the
> > gain in the config file).
"Curtis L. Olson" wrote:
> Update of /var/cvs/FlightGear-0.9/releases
> In directory baron:/tmp/cvs-serv18174
> Added Files:
> FlightGear-0.9.6.tar.gz
> Log Message:
> Official source release for v0.9.6
I'm asking just to find out: Do we all agree that it makes much sense
to build the up
Erik Hofman wrote:
> Sent: 12 October 2004 18:42
> To: FlightGear developers discussions
> Subject: Re: [Flightgear-devel] Re: [Flightgear-cvslogs] CVS:releases
> FlightGear-0.9.6.tar.gz, NONE,
>
> Martin Spott wrote:
> > "Curtis L. Olson" wrote:
> &g
Vivian Meazza wrote :
Hmmm ... last time I tried Plib cvs (last week) there seemed to be some
problem with joystick axes under Cygwin. I reverted to 1.8.3, no problem.
Lack of time has precluded further investigation.
I already posted on that subject on the plib list but without any response.
The
Frederic Bouvier wrote:
> Sent: 12 October 2004 20:36
> To: FlightGear developers discussions
> Subject: Re: [Flightgear-devel] Re:[Flightgear-cvslogs] CVS:releases
> FlightGear-0.9.6.tar.gz, NONE,
>
> Vivian Meazza wrote :
>
> >Hmmm ... last time I tried Plib cvs
Frederic Bouvier wrote:
> Sent: 12 October 2004 18:12
> To: FlightGear developers discussions
> Subject: Re: [Flightgear-devel] Re: [Flightgear-cvslogs] CVS:
> releasesFlightGear-0.9.6.tar.gz, NONE,
>
> Martin Spott wrote:
>
> > "Curtis L. Olson" wrote:
&g
Vivian Meazza wrote:
> Frederic Bouvier wrote:
>
> > Sent: 12 October 2004 18:12
> > To: FlightGear developers discussions
> > Subject: Re: [Flightgear-devel] Re: [Flightgear-cvslogs] CVS:
> > releasesFlightGear-0.9.6.tar.gz, NONE,
> >
> > Martin Spot
Jon Berndt wrote:
Erik Hofman wrote:
Add a protocol for the ACMS protocol which seems to be used as an
output format for black-box data flight data. This configuration
does not work directly since there is no FDM available that reads
the accelerations from the property tree and translates them int
Erik Hofman writes:
> Jon Berndt wrote:
> >>Erik Hofman wrote:
> >>
> >>
> >>>Add a protocol for the ACMS protocol which seems to be used as an
> >>>output format for black-box data flight data. This configuration
> >>>does not work directly since there is no FDM available that reads
> >>>the accel
* Vivian Meazza -- Tuesday 16 November 2004 18:06:
> Melchior FRANZ wrote:
> > OBJECT_SHARED Models/Geometry/Nimitz/nimitz.ac -122.590 37.76 -7.0 90
>
> It should work just with the ... stuff in my earlier post.
Yes. Changed that now.
> Mathias has put all the necessary stuff here:
>
> ftp:/
Melchior FRANZ wrote
> > Mathias has put all the necessary stuff here:
> >
> > ftp://ftp.uni-duisburg.de/FlightGear/Misc_maf/carrier/
> >
> > The code that he sent me works well, but I haven't tried it from that
> > location yet.
>
> I applied all the stuff and it worked very well. My first car
* Mathias Fröhlich -- Wednesday 17 November 2004 21:42:
> On Mittwoch 17 November 2004 11:29, Melchior FRANZ wrote:
> > * I observed one segfault that I hadn't seen before. The bt, however,
> > didn't look like it had anything to do with the new code. I haven't saved
> > the core file but will do s
On Tue, 30 Nov 2004 14:55:29 + (UTC), Martin Spott
<[EMAIL PROTECTED]>
> Hm ? I thought Curt just made it working with stock PLIB - is it still
> broken ?
It uses the AC3D crease directive, which stock plib doesn't support.
More importantly, FlightGear still tries to load the Nimitz even whe
David Megginson wrote:
On Tue, 30 Nov 2004 14:55:29 + (UTC), Martin Spott
<[EMAIL PROTECTED]>
Hm ? I thought Curt just made it working with stock PLIB - is it still
broken ?
It uses the AC3D crease directive, which stock plib doesn't support.
At 03:47 today.
Modified Files:
nimitz.ac
Log
Erik Hofman wrote:
> Update of /var/cvs/FlightGear-0.9/data/Models/Weather
> In directory baron:/tmp/cvs-serv28318/Models/Weather
>
> Added Files:
> rain.ac rain.rgb rain.xml
> Log Message:
> Add a basic model for rain. Test w. the pc-7
This looks quite interesting but I realize that this
Erik Hofman wrote:
> Update of /var/cvs/FlightGear-0.9/data/Models/Weather
> In directory baron:/tmp/cvs-serv5714
>
> Modified Files:
> rain.ac rain.xml
> Log Message:
> Model changes and add some select's.
Great idea, especially because there's no 'cigar' around the cockpit
anymore ;-)
Martin Spott wrote:
The model looks very nice and the handling feels pretty easy. It's only
Thanks.
that I'm missing the cabin door being coupled to the parking brake as
it was in your first version ;-)
No, it's not ...
:-)
Erik
___
Flightgear-devel mail
"Curtis L. Olson" wrote:
> Update of /var/cvs/FlightGear-0.9/source/src/Network
> In directory baron:/tmp/cvs-serv347
>
> Modified Files:
> net_ctrls.hxx net_fdm.hxx
> Log Message:
> 32 bit integers are somewhat magical and handled pretty well across platforms
> in terms of predictable pack
Martin Spott wrote:
Modified Files:
AIAircraft.cxx
Log Message:
Solaris fixes
^^
+ #elif defined(sun) || defined(sgi)
+ # include ^^^
Hehe ;-)
Thanks for applying these fixes !
So far for my hope to sneak it in ;-)
Erik
___
Flightgear-d
Melchior Franz wrote:
> Update of /var/cvs/FlightGear-0.9/data/Models/Airport
> In directory baron:/tmp/cvs-serv27845
> Modified Files:
> beacon.xml beacon.ac
Jon, are you going to update the respective entry in our database ?
Martin.
--
Unix _IS_ user friendly - it's just selective abo
* Jon Stockill -- Sunday 29 May 2005 20:38:
> Martin Spott wrote:
> > Melchior Franz wrote:
> > > Modified Files:
> > > beacon.xml beacon.ac
> >
> > Jon, are you going to update the respective entry in our database ?
>
> [...] there are database entries for the objects in the base package just
* Jon Stockill -- Sunday 29 May 2005 21:02:
> Melchior FRANZ wrote:
> > With these changes most of the 950 faces are invisible to the ground cache.
> > There's only a simple invisible pyramid instead for intersection tests.
> Is this something that people should consider for any high poly
> struc
* Frederic Bouvier -- Sunday 29 May 2005 21:32:
> Melchior FRANZ a écrit :
>
> >In less verbosity: this technique does only make sense for objects with high
> >face
> >*density*, not high face *number*.
> >
> The beacon has a lot of vertical, or near vertical, faces.
I saw them when I edited i
* Melchior FRANZ -- Sunday 29 May 2005 21:23:
> * Jon Stockill -- Sunday 29 May 2005 21:02:
> > Melchior FRANZ wrote:
> > > With these changes most of the 950 faces are invisible to the ground
> > > cache.
> > > There's only a simple invisible pyramid instead for intersection tests.
>
> > Is this
Erik Hofman wrote:
> Update of /var/cvs/FlightGear-0.9/FlightGear/src/FDM
> In directory baron:/tmp/cvs-serv27859/FDM
>
> Modified Files:
> groundcache.cxx
> Log Message:
> Mathias Fröhlich:
>
> this is basically the past patch I sent to the list and which should now
> really (...!?!?) fi
* Martin Spott -- Thursday 02 June 2005 13:35:
> > Mathias Fröhlich:
> >
> > this is basically the past patch I sent to the list and which should now
> > really (...!?!?) fix the no ground below aircraft problem.
>
> Unfortunately the 'quick hack' was a better solution for my setup.
> Could you
Martin Spott wrote:
> Update of /var/cvs/FlightGear-0.9/docs/getstart/pdf
> In directory baron:/tmp/cvs-serv13049/pdf
> Modified Files:
> FGShortRef.pdf getstart.pdf
> Log Message:
>
> Forgot an update, build with newer pdfTeX.
BTW, did we have a consensus on the use of EMAil addresses in
"Curtis L. Olson" wrote:
> Update of /var/cvs/FlightGear-0.9/source/utils/GPSsmooth
> In directory baron:/tmp/cvs-serv15890
>
> Modified Files:
> Makefile.am
> Log Message:
> Attempt to add -lwinmm for windows builds (untested.)
I'd like to suggest another fix, as the IRIX build lacks "-lm
Martin Spott wrote:
Erik Hofman wrote:
Update of /var/cvs/FlightGear-0.9/FlightGear/utils/GPSsmooth
In directory baron:/tmp/cvs-serv8203
Modified Files:
Makefile.am
Log Message:
IRIX fixes.
Thanks - works,
'course it works, it's tested on IRIX :-)
Erik
Martin Spott wrote:
Solaris needs '$(X_EXTRA_LIBS)' as well to resolve dependencies that
are introduced by '-lplibnet',
Does $(opengl_LIBS) work as well?
Erik
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.
Melchior Franz wrote:
> Update of /var/cvs/FlightGear-0.9/data/gui
> In directory baron:/tmp/cvs-serv29971
Ich seh' schon, waehrend die Mehrheit in Urlaub faehrt, baust Du in der
Zwischenzeit den halben FlightGear um :-)
Tschuess,
Martin.
--
Unix _IS_ user friendly - it's just selectiv
* Martin Spott -- Saturday 09 July 2005 11:51:
> Ich seh' schon, waehrend die Mehrheit in Urlaub faehrt, baust Du in der
> Zwischenzeit den halben FlightGear um :-)
No, I'm not going to rewrite fgfs while the others are on vacation. :-)
Although these changes look extensive, they aren't really.
"Curtis L. Olson" wrote:
> Update of /var/cvs/FlightGear-0.9/data/Aircraft/BAC-TSR2/Models
> In directory baron:/tmp/cvs-serv26968/Models
> Modified Files:
> BAC-TSR2-model.xml
[...]
I really like this aircraft - it spreads some sort of 'charisma', very
much like the Concorde !
Thanks,
Martin Spott wrote:
Hello Erik,
Erik Hofman wrote:
Update of /var/cvs/FlightGear-0.9/FlightGear
In directory baron:/tmp/cvs-serv29428
Modified Files:
configure.ac
Log Message:
Prepare for OpenAL 1.1 and a separate alut lubrary.
Did you actually manage to compile current OpenAL CVS on IR
Erik Hofman wrote:
> Update of /var/cvs/FlightGear-0.9/data/Aircraft/c150/Models/Vintage
> In directory baron:/tmp/cvs-serv14308/Models/Vintage
>
> Added Files:
> README.TXT c150-01.rgb c150-02.rgb c150-int.rgb c150-int2.rgb
> Log Message:
> Add Mark Miller's c150 vintage look livery.
> (Se
> Modified Files:
> obj.cxx
> Log Message:
> Have DummyBSphereEntity inherit from ssgBranch instead of ssgEntity,
> to allow building with the latest plib CVS.
Uh, I appreciate this one _very_ much because it enables me to follow the
current development.
Thanks,
Martin.
--
Unix _
Chrisitan,
> Well, I think even addresses like
>
> something @ something.com
>
> aren't save against spammers.
I guessed it.
> So far the best recepie is to convert the address to little pixel
> graphics and to include the images on the page.
...which 100 or so graphics you are going to creat
Michael Basler wrote:
>
> Chrisitan,
>
> > Well, I think even addresses like
> >
> > something @ something.com
> >
> > aren't save against spammers.
>
> I guessed it.
>
> > So far the best recepie is to convert the address to little pixel
> > graphics and to include the images on the page.
>
Christian,
> Including images in LaTeX is no problem - that just leaves us with the
> problem how we are generating the images...
Exactly. Although the HTML converter might become a bit slow with 100+ pix.
Perhaps no serious problem.
> I'm sure that one of the Unix gurus knows a fast way to do t
Michael Basler writes:
> Chrisitan,
>
> > Well, I think even addresses like
> >
> > something @ something.com
> >
> > aren't save against spammers.
>
> I guessed it.
>
> > So far the best recepie is to convert the address to little pixel
> > graphics and to include the images on the page.
>
>
Curt,
> Could you fake something as an equation:
>
> $ curt\@flightgear.org $
>
> latex2html would convert this to a graphic automatically ... although
> in equation mode you have to worry about things getting interpreted as
> equations and variables ...
Yes, latex2html does, but tex4ht which I
Michael Basler wrote:
>
> I tried this. It was still recognizable after conversion in the HTML. I
> simply searched for my address (Ctrl-GF in IE) and it was found :-( I tried
> several font changes etc. which all did not hide the address.
>
> A clever sign for/aft the @ being invisible but maski
Christian,
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Christian
> Mayer
> This gives ma an idea:
>
> Render only the @ to a picture and include this picture instead of the
> real @ sign in the address. I think this should fool enough
> address-harvesters.
Sounds like a co
Michael Basler writes:
>
> > Christian Mayer wrote:
>
> > This gives ma an idea:
> >
> > Render only the @ to a picture and include this picture instead of the
> > real @ sign in the address. I think this should fool enough
> > address-harvesters.
>
> Sounds like a cool idea as I'll only have t
Norman,
> [mailto:[EMAIL PROTECTED]]On Behalf Of Norman Vine
> Sent: Tuesday, December 17, 2002 8:09 PM
> To: [EMAIL PROTECTED]
> Why not just use ' at ' instead of '@'
>
> note spaces surrounding 'at'
>
Something similar already occured to me but I've dismissed it as being
to ugly. If those n
Norman Vine wrote:
>
> Michael Basler writes:
> >
> > > Christian Mayer wrote:
> >
> > > This gives ma an idea:
> > >
> > > Render only the @ to a picture and include this picture instead of the
> > > real @ sign in the address. I think this should fool enough
> > > address-harvesters.
> >
> > So
On 12/28/02 at 7:10 PM [EMAIL PROTECTED] wrote:
>Date: Sat Dec 28 14:10:41 EST 2002
>Author: cvsroot
>
>Update of /home/cvsroot/FlightGear/FlightGear/Aircraft/Instruments
>In directory bitless:/tmp/cvs-serv31667/Instruments
>
>Modified Files:
> single-magneto-switch.xml
>Log Message:
>Chang
On 1/2/03 at 11:52 AM Curtis L. Olson wrote:
>David,
>
>Another feature request would be to create a volume and on/off switch
>property and honor them. Volume could go from 0.0 - 1.0 scaled
>appropriately, and on/off is pretty self explanitory. It would also
>be nice to have a "servicable" prope
On 1/2/03 at 11:52 AM Curtis L. Olson wrote:
>Another feature request would be to create a volume and on/off switch
>property and honor them. Volume could go from 0.0 - 1.0 scaled
BTW, can you hear the audio ATIS OK on your Linux box? There have been a
few problems reported with it over Christm
David Luff writes:
> On 1/2/03 at 11:52 AM Curtis L. Olson wrote:
>
> >Another feature request would be to create a volume and on/off switch
> >property and honor them. Volume could go from 0.0 - 1.0 scaled
>
> BTW, can you hear the audio ATIS OK on your Linux box? There have been a
> few probl
Does this mean, the document is also part of cvs?
Can anyone give me a hand on how to continue writing using cvs?
Where do I have to send or put new chapters?
Thanks,
Carsten
Michael Basler schrieb:
>
> > Log Message:
> > Add Carsten Hoefer's excellent flight tutorial to help
> system
>
> Tha
Carsten,
> Does this mean, the document is also part of cvs?
Luckily, indeed. Plus, it certainly will become part of the next official
release (if you don't object, of course).
> Can anyone give me a hand on how to continue writing using cvs?
> Where do I have to send or put new chapters?
Instr
[EMAIL PROTECTED] wrote:
> Modified Files:
> f16.xml
> Log Message:
> improved f-16 from Erik Hofman
Oh, _very_ nice, but eerm, did anyone manage to get the beast off the
runway without crashing _before_ take-off ? Is it possible ?
Martin.
--
Unix _IS_ user friendly - it's just s
On Tuesday 25 February 2003 2:22 pm, Martin Spott wrote:
> [EMAIL PROTECTED] wrote:
> > Modified Files:
> > f16.xml
> > Log Message:
> > improved f-16 from Erik Hofman
>
> Oh, _very_ nice, but eerm, did anyone manage to get the beast off
> the runway without crashing _before_ take-off ?
John Check writes:
> On Tuesday 25 February 2003 2:22 pm, Martin Spott wrote:
> > [EMAIL PROTECTED] wrote:
> > > Modified Files:
> > > f16.xml
> > > Log Message:
> > > improved f-16 from Erik Hofman
> >
> > Oh, _very_ nice, but eerm, did anyone manage to get the beast off
> > the runway wi
On Tuesday 25 February 2003 3:40 pm, Curtis L. Olson wrote:
> John Check writes:
> > On Tuesday 25 February 2003 2:22 pm, Martin Spott wrote:
> > > [EMAIL PROTECTED] wrote:
> > > > Modified Files:
> > > > f16.xml
> > > > Log Message:
> > > > improved f-16 from Erik Hofman
> > >
> > > Oh, _v
> [EMAIL PROTECTED] wrote:
>
> > New hi-res irregular crop texture.
>
> For eye-candy fetischitsts (is this an english word?)
> http://www.a1.nl/~ehofman/fgfs/download/irrcrop.jpg
Damn, that's cool.
g.
___
Flightgear-devel mailing list
[EMAIL PROTECT
On Wed, 5 Mar 2003, Gene Buckle wrote:
> > [EMAIL PROTECTED] wrote:
> >
> > > New hi-res irregular crop texture.
> >
> > For eye-candy fetischitsts (is this an english word?)
> > http://www.a1.nl/~ehofman/fgfs/download/irrcrop.jpg
>
> Damn, that's cool.
yeah, VERY nice
--
Jon Stockill
[EMAIL PR
Jon Stockill writes:
> On Wed, 5 Mar 2003, Gene Buckle wrote:
>
> > > [EMAIL PROTECTED] wrote:
> > >
> > > > New hi-res irregular crop texture.
> > >
> > > For eye-candy fetischitsts (is this an english word?)
> > > http://www.a1.nl/~ehofman/fgfs/download/irrcrop.jpg
> >
> > Damn, that's cool.
>
On Wed, 5 Mar 2003 17:19:30 -0600
"Curtis L. Olson" <[EMAIL PROTECTED]> wrote:
http://www.flightgear.org/images/crop-variety.jpg
Wow. Now that looks like the areas surrounding Mpls.
Jon
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mai
Erik Hofman <[EMAIL PROTECTED]> wrote:
> Update of /var/cvs/FlightGear-0.9/FlightGear/src/Main
> In directory seneca:/tmp/cvs-serv12094/src/Main
> Modified Files:
> main.cxx
> Log Message:
> Andy wrote:
> This is just a port of an old 3D HUD patch to the new view code.
Oh yeah, this looks
Curtis L. Olson wrote:
Update of /var/cvs/FlightGear-0.9/FlightGear/src/Main
In directory seneca:/tmp/cvs-serv13494
Modified Files:
fg_commands.cxx
Log Message:
Don't start paused for in air starts.
Do you think this is a good idea?
Wouldn't it be better to sepecify this in the command line?
Erik
[Originally sent to [EMAIL PROTECTED] by mistake.]
Curtis L. Olson writes:
> With these changes, the GS will bring you in precisely to the
> touchdown point as defined in the default.ils.gz file (it wouldn't
> before.) The only issue that remains is that it will bring you in
> to the elevati
Curtis L. Olson writes:
> You bastards! Writing property names to char arrays that are too short for
> the data you are putting in it. :-( Fixed ...
> for (index = 0; index < MAX_ENGINES; index++) {
> ! char name[32];
> sprintf(name, "/controls/engines/engine[%d]/throttle", i
David Megginson writes:
> Curtis L. Olson writes:
>
> > Modified Files:
> >default.ils.gz
> > Log Message:
> > Align all the approaches I could automatically match up to runways.
>
> Where we have exact data on the lat/lon of the localizer and GS, we
> should use it, and fix our airport
Curtis L. Olson writes:
> The problem is that I have two data sets both providing "exact"
> locations for the localizer and both disagreeing significantly on the
> position and orientation. :-(
We have to decide on the authority of each data point individually.
Anything that we get from the DA
David Megginson writes:
> We have to decide on the authority of each data point individually.
> Anything that we get from the DAFIF or FAA data should stand as-is,
> for example. For Robin Peel's data, we should fix things only when
> there is a known problem.
The problem is that in my spot check
Curtis L. Olson writes:
> I don't know if either DAFIF or FAA could be considered
> "authoritative".
I'd consider FAA authoritative for U.S. airports, and DAFIF for other
countries, again, until proven otherwise.
> I'm guessing that when an ILS is installed, someone goes out and
> stands at
Jim Wilson writes:
> Sigh... can't we just leave this the way it was for now and tell people that
> we recommend a 3 axis stick??? :-/ If not we need time to check the joystick
> configs (and I don't have time to do the two I have today). I'd much rather
> see this patch added right after releas
301 - 400 of 776 matches
Mail list logo