Jon S. Berndt
Sent: 10 December 2007 01:28
To: Flightgear-Devel
Subject: [Flightgear-devel] Building FlightGear, once again
For the first time in a very long time, I have a system on
which I should be able to build and run FlightGear. I had a
script some time ago that handled updating
Hi All,
Two small Chat Menu related patches:
1) The chat menu will now select the runway closest to the aircraft when the
aircraft is on the ground, or very low ( 100ft). This handles the case where
the
user has selected a runway explicitly, e.g. 01R for KSFO take-offs for noise
abatement. My
On sam 8 décembre 2007, Melchior FRANZ wrote:
* Durk Talsma -- Saturday 08 December 2007:
Based on all the input sofar, I'd like to propose the following list of
aircraft for inclusion in the next release:
Looks good. Not trying to say anything particular -- just FYI:
20M 787
20M
--- Stuart Buchanan wrote:
Hi All,
Two small Chat Menu related patches:
1) The chat menu will now select the runway closest to the aircraft when the
aircraft is on the ground, or very low ( 100ft). This handles the case where
the
user has selected a runway explicitly, e.g. 01R for KSFO
On Mon, 10 Dec 2007 07:26:30 +0100
Tim Moore wrote:
In any event, this should be fixed now.
Yup, appears fixed. Thanks.
-c
--
Chris Metzler [EMAIL PROTECTED]
(remove snip-me. to email)
As a child I understood how to give; I have forgotten this grace since
Hi,
I made a patch to fix the segfault in exiting fgfs on 0.9.11-pre2.
This segfault happens by releasing uninitialized instance variables in
FGGlobals::~FGGlobals()
Durk, or Melchior, appply this patch before the release, please.
Thank you.
Tat
On Dec 8, 2007, at 10:43 PM, Tatsuhiro
Hi again,
By the way, this patch can be and should be applied to CVS/head too
since I also have exactly the same segfault with cvs/head on Mac OS X.
Best,
Tat
On Dec 11, 2007, at 12:37 AM, Tatsuhiro Nishioka wrote:
Hi,
I made a patch to fix the segfault in exiting fgfs on 0.9.11-pre2.
I'm getting a 404 not found error on the link.
On Monday 10 December 2007 07:32:59 am Stuart Buchanan wrote:
--- Stuart Buchanan wrote:
Hi All,
Two small Chat Menu related patches:
1) The chat menu will now select the runway closest to the aircraft when
the aircraft is on the
--- Robert Black wrote:
... and as my mail client insists on wrapping lines with CRLF, I've
uploaded a diff file to http://www.nanjika.co.uk/flightgear.chat-menu.diff
-Stuart
I'm getting a 404 not found error on the link.
Should be http://www.nanjika.co.uk/flightgear/chat-menu.diff
* Melchior FRANZ -- Sunday 09 December 2007:
* Melchior FRANZ -- Sunday 09 December 2007:
BTW: in my tests yesterday I noticed that the unload part was
never called, and so the loop is never stopped.
Just for the record: yes, that's not done ATM. Will fix tomorrow.
Which is now done. It
* Tatsuhiro Nishioka -- Monday 10 December 2007:
this patch can be and should be applied to CVS/head too
Done, thanks.
m.
-
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place
Hi Melchior,
Melchior FRANZ schrieb am 10.12.2007 19:32:
Note that loops/listeners that were started in nasalload have
to be stopped/removed in nasalunload! Otherwise they will keep
running (which is a feature), and you might accumulate them over
time. The bo105 does that correctly, the v22
I think I finally found out why the b1900d is still running at startup...
The condition lever is set to 1 in the TurbineEngine.cpp file , so it appears
to override anything in the set file. Ive forced it to 0 in the system.nas file
during fdm initialization , but then you hear the engines
On mar 11 décembre 2007, SydSandy wrote:
I think I finally found out why the b1900d is still running at startup...
The condition lever is set to 1 in the TurbineEngine.cpp file , so it
appears to override anything in the set file. Ive forced it to 0 in the
system.nas file during fdm
On Monday 10 December 2007 07:44:27 pm SydSandy wrote:
I think I finally found out why the b1900d is still running at startup...
The condition lever is set to 1 in the TurbineEngine.cpp file , so it
appears to override anything in the set file. Ive forced it to 0 in the
system.nas file during
On Mon, 10 Dec 2007 23:01:39 -0600
Robert Black [EMAIL PROTECTED] wrote:
On Monday 10 December 2007 07:44:27 pm SydSandy wrote:
I think I finally found out why the b1900d is still running at startup...
The condition lever is set to 1 in the TurbineEngine.cpp file , so it
appears to
On Monday 10 December 2007 04:26, Curtis Olson wrote:
Durk is planning to roll up the official source/data tar balls for the next
release sometime this week.
As it looks right now, either tonight, or Thursday evening will be my two
windows of opportunity this week. As a matter of fact, I just
Hi,
there are two What's New lists in the wiki:
http://wiki.flightgear.org/flightgear_wiki/index.php?title=Changes_since_0.9.10
and
http://wiki.flightgear.org/flightgear_wiki/index.php?title=FlightGear_pre-release_changelog_summary
Which one will be used as the official What's new list?
I would
On Tuesday 11 December 2007 08:19, Maik Justus wrote:
Hi,
there are two What's New lists in the wiki:
http://wiki.flightgear.org/flightgear_wiki/index.php?title=Changes_since_0.
9.10 and
http://wiki.flightgear.org/flightgear_wiki/index.php?title=FlightGear_pre-r
elease_changelog_summary
19 matches
Mail list logo
