This story will warm your heart ;-)
"A DC-3 flies the northern skies"
http://msnbc.msn.com/id/3660452/
Jon
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
* Curtis L. Olson -- Saturday 13 December 2003 01:38:
> Strange, someone suggested this as a fix.
This "someone" obviously worked on a server. The following patch
should fix client mode. (Works for me. I didn't test server mode.)
m.
Index: sg_socket.cxx
===
* Curtis L. Olson -- Saturday 13 December 2003 01:38:
> Strange, someone suggested this as a fix. Note that previously,
> read() and readline() were not consistant.
Aah yes. But this client thing is only necessary for server mode,
where there's more than one connection required at the same time.
On Friday 12 December 2003 21:30, [EMAIL PROTECTED] wrote:
> Hello,
>
> today i tested all 45 aircrafts that are available in flightgear
> and wrote down all things i noticed that were missing, wrong or not
functional
> for each aircraft.
>
> The result is this aircraft TODO list, i suggest add
* Norman Vine -- Saturday 13 December 2003 01:29:
> The client is constructed in pol() at the end of the file
Yepp, but in SGSocket::poll():
if (result > 0 && is_server && client == 0)
{
[...]
client = new netSocket();
client->setHandle( new_fd );
return 0
Melchior FRANZ writes:
> BTW: reverting the last patch and going back to revision 1.2 fixes
> the bug. But it does still not explain the "client" zombie.
Strange, someone suggested this as a fix. Note that previously,
read() and readline() were not consistant. the patch made them
consistant. Th
* Melchior FRANZ -- Saturday 13 December 2003 00:48:
> As "client" is "delete"d in line 279, I assume that a
> "client = new netSocket" was forgotten somewhere. But where?
No wait. The client variable =is= set in some circumstances. Just
not in my case. Have yet to find out more ...
m.
Melchior FRANZ writes:
>
> BTW: reverting the last patch and going back to revision 1.2 fixes
> the bug. But it does still not explain the "client" zombie.
The client is constructed in pol() at the end of the file
___
Flightgear-devel mailing list
[E
BTW: reverting the last patch and going back to revision 1.2 fixes
the bug. But it does still not explain the "client" zombie.
m.
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
I don't know how this code is supposed to work, but I know what a
segfault is. There's a funny netSocket pointer "client" that is
only once instantiated with 0 in the constructor (line 42) and
in every read operation (tcp) happily null-pointer-dereferenced
(line 223) --> BOOM!
As "client" is "d
* Andy Ross -- Friday 12 December 2003 23:25:
> There actually is *lots* of documentation out
> there, as you point out the difficulty is getting someone to do the
> work to compile and index it. While you're working on it (heh), I
> wrote a "manual" for the A-4 that should probably go in:
> http:
Brandon Craig Rhodes wrote:
> I also think the FAQ needs to include instructions for how to take
> off in all of the more difficult planes (like the B-52 and P-51);
This is a good idea. There actually is *lots* of documentation out
there, as you point out the difficulty is getting someone to do t
I flew back to Ottawa (CYOW) from Philadelphia (KPHL) today, against a
strong heading (ground speed was 95-105 kt for a true airspeed of about 126
kt). I climbed up to 10,000 ft to stay above all the lake-effect weather in
Upstate NY, and ended up with a nice, sunny, 3.5-hour flight home.
To k
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> today i tested all 45 aircrafts that are available in flightgear and
> wrote down all things i noticed that were missing, wrong or not
> functional for each aircraft.
These are among the dozens of things I would like to see added to the
FAQ, havin
Oliver C. wrote:
> today i tested all 45 aircrafts that are available in flightgear and
> wrote down all things i noticed that were missing, wrong or not
> functional for each aircraft.
Wow, good work. I honestly had no idea we had so many; it's been a
while since I counted. :)
> harrier
> - h
[EMAIL PROTECTED] wrote:
The result is this aircraft TODO list, i suggest adding this file to cvs
in the data/Aircraft directory, so that new entrys or old entrys can easily
be removed in this file when an aircraft gets upgraded.
Thank you, but instead of adding this to the CVS (so that you always
Hello,
today i tested all 45 aircrafts that are available in flightgear
and wrote down all things i noticed that were missing, wrong or not functional
for each aircraft.
The result is this aircraft TODO list, i suggest adding this file to cvs
in the data/Aircraft directory, so that new entrys or
Thinking of the X-15 and its flight profile: does FlightGear do any
sky darkening as the aircraft flies up past 100,000 feet altitude? It
doesn't seem to me that it would be that hard to do.
Jon
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
htt
- Original Message -
From: Augusto
To: [EMAIL PROTECTED]
Sent: Friday, December 12, 2003 2:56 PM
Subject: ok it is compiled...now problems with 3d pannelled
aircrafts..
I'm wondering what's up with aircraft with 3d panel
(c310u3a, c182) and the new version 0.9.3.
At run time i
19 matches
Mail list logo
