Matthew Johnson writes (quoting an online review):
Overall the system structure and coding is poor - and reflects the
checkered and disrupted development history
That is true, unfortunately. FlightGear's code is better organized
than many open source projects (and far better than nearly all
Matthew Johnson wrote:
Major A wrote:
does the 747-yasim segfault fgfs on everyone's computer?
Yes I get a segfault too
I can't reproduce this with the command line solver (and can't run
fgfs from work). Crashes in YASim are (well, have been) almost always
in the parser, and happen due to
Andy Ross writes:
I can't reproduce this with the command line solver (and can't run
fgfs from work). Crashes in YASim are (well, have been) almost always
in the parser, and happen due to unhandled syntax errors. Are you
sure you have the proper base package and an unmodified 747.xml file?
[Sorry for the delay. This one was hard, and had to wait for the
weekend for an investigation.]
David Megginson wrote:
Andy: unfortunately, none of your suggestions helped (details
below). How are you modelling washout in YASim? From the violent
roll that comes with every stall, it looks
Curtis L. Olson [EMAIL PROTECTED] said:
Andy Ross writes:
I can't reproduce this with the command line solver (and can't run
fgfs from work). Crashes in YASim are (well, have been) almost always
in the parser, and happen due to unhandled syntax errors. Are you
sure you have the proper
On 05 Jan 2003 23:07:47 -0800,
Matthew Johnson [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]:
..I'll ask and cc here, look for
http://www.dlsproductions.com/fg/; in the Subject: header.
You're all taking this rather well, as far as I can tell...
..I've received a response
Andy Ross writes:
The real reason for washout (or at least a better physical
explanation) is this: the washout that maintains the tips below
stall AoA keeps as much of the stable derivative as possible out
on the wing tips where the moment arm is long. If the early stall
happens near
On Mon, 06 Jan 2003 11:31:46 -0800,
Andy Ross [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]:
So anyway, YASim needs to model washout. In principle, this should be
pretty easy. Each wing segment (Surface object, as currently
implemented) gets its own orientation already. We just
Arnt Karlsen wrote:
..some planes use distinctly different airfoils, leading edge cuffs,
slots etc, towash out. Some different-airfoil wings transform
gradually towards the tip, and not neccesarily in a linear fashion,
some of these can get really weird.
Actually, this is supported already,
David Megginson wrote:
I found it easier simply to picture different 2D sections of the
wing stalling at different times, but I can see how your explanation
might lead to a programmatic solution faster.
Right, but what is it about different secions of the wing stalling at
different times that
Can one of you get a stack trace in gdb to see where it's crashing?
This is the command line:
/usr/local/FlightGear/bin/fgfs --fg-root=/usr/local/FlightGear/lib/FlightGear
--aircraft=747
This is what gdb says:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384
David Megginson writes:
I found it easier simply to picture different 2D sections of the wing
stalling at different times, but I can see how your explanation might
lead to a programmatic solution faster.
Easiest way I know of to learn about airfoil stall is to stick a bunch
of yarns into an
Works fine on SuSE 8.1, after CVS update. Well apart from a blank
panel...
Matt
PS Build also went through without a hitch.
On Mon, 2003-01-06 at 15:58, Major A wrote:
Can one of you get a stack trace in gdb to see where it's crashing?
This is the command line:
Major A wrote:
#0 ssgSGIHeader::getRow() at ssgLoadSGI.cxx:211
#1 ssgSGIHeader::ssgSGIHeader(...
/usr/local/FlightGear/lib/FlightGear/Aircraft/747/Models/boeing747-400-jw-08.rgb,
...)
at ssgLoadSGI.cxx:328
This is plib crashing while trying to load a texture file. My guess
is
Andy Ross writes:
Isn't the snap roll usually uncoordinated? I've never done aerobatics
myself. If it is, then I wonder what the role of the uncoordination
is.
If there is any wing sweep or dihedral, then a non-zero yaw angle also
changes the relative AoA of the wings to produce
Norman Vine writes:
Easiest way I know of to learn about airfoil stall is to stick a bunch
of yarns into an iceboat sail and go for a ride :-)
That's a lot of work, when you can just go flying in light snow and
watch the flakes around the wings. I haven't tried that yet, though.
All the
David Megginson writes:
Norman Vine writes:
Easiest way I know of to learn about airfoil stall is to stick a bunch
of yarns into an iceboat sail and go for a ride :-)
That's a lot of work, when you can just go flying in light snow and
watch the flakes around the wings. I haven't
There might be a yaw rate effect too. When the aircraft is yawing,
the wingtip going back also sees a higher AoA and will drop if it
is
past the stall. Same deal. The snap roll needs a stalled down
wingtip to get the divergence, in any case.
That makes sense -- thanks.
There's
On Mon, 2003-01-06 at 15:26, Andy Ross wrote:
David Megginson wrote:
I found it easier simply to picture different 2D sections of the
wing stalling at different times, but I can see how your explanation
might lead to a programmatic solution faster.
Right, but what is it about different
On Mon, 2003-01-06 at 17:54, Curtis L. Olson wrote:
Jon Berndt writes:
There might be a yaw rate effect too. When the aircraft is yawing,
the wingtip going back also sees a higher AoA and will drop if it
is
past the stall. Same deal. The snap roll needs a stalled down
It seems that you guys get hundreds of build-related and/or platform
problems to diagnose, and you spend way too much time having to get
people to identify their configurations... Something I've done in the
past is to generate a string of information at compile time that
identifies when and how
I found it very helpful to capture a compile date and cvs tag into a
chip design that verification people could use to direct me to a
particular verilog code base to reproduce and debug problems.
Good idea. We sort of do this for JSBSim. Isn't there a command that you
can type to get
On Mon, 6 Jan 2003 22:55:56 -0600
Jon Berndt [EMAIL PROTECTED] wrote:
I found it very helpful to capture a compile date and cvs tag into a
chip design that verification people could use to direct me to a
particular verilog code base to reproduce and debug problems.
Good idea. We sort of
Bernie Bright wrote:
The very first thing FG displays is its version number and compiler
info:
[...]
It would be trivial to add a timestamp.
A much better idea would be to store a time in the CVS archive.
Relying on a compilation date can bite you in very strange ways. Who
knows when the
24 matches
Mail list logo
