John Check writes:
Well, Ideally, no, but like anything else, unless we have some documentation
to work from, getting it right isn't likely. I don't know what doco is
available. My feeling is that that we should at least have the
battery and/or
alternator connected to a main buss, which is
On Tuesday 22 October 2002 06:45 pm, John Check wrote:
Is KOAK the only thing that changed in that tarball?
It should have been.
Wm
--
William L. Riley
[EMAIL PROTECTED]
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
I have a few models that run w/ the --enable-auto-coordination flag in the
startup command line. Is there a way to do this in the *-set.xml file
instead? If it is possible, I'd like to make such a change w/ my Wright
Flyer model on the cvs.
Thanks,
Michael
Michael Selig wrote:
I have a few models that run w/ the --enable-auto-coordination flag in
the startup command line. Is there a way to do this in the *-set.xml
file instead? If it is possible, I'd like to make such a change w/ my
Wright Flyer model on the cvs.
Just add:
sim
At 10/23/02, Erik Hofman wrote:
Michael Selig wrote:
I have a few models that run w/ the --enable-auto-coordination flag in
the startup command line. Is there a way to do this in the *-set.xml
file instead? If it is possible, I'd like to make such a change w/ my
Wright Flyer model on the
Andy Ross wrote:
John Check wrote:
What it is is that when electrical system modeling was added it
affected planes for which no electrical system was added.
Shouldn't the sane choice for the defaults be the opposite? The
instruments work unless the electrical system tells them that
[EMAIL PROTECTED] writes:
Agreed. Instruments that test whether they are powered should
default to powered if the aircraft does not provide a suitable
electrical system. This could translate to if the required power
bus property is not present. A simple default electrical system
that
On Wednesday 23 October 2002 8:10 am, Curtis L. Olson wrote:
John Check writes:
Well, Ideally, no, but like anything else, unless we have some
documentation to work from, getting it right isn't likely. I don't know
what doco is available. My feeling is that that we should at least have
Curt sent me a generic-electrical.xml that I'll be committing shortly.
In the interest of tidyness I'm considering adding a directory
Aircraft/Generic
to hold stuff like this. I'm not planning on moving anything
like instruments in there, but possibly things like the
mini panel. Basically, it
I am trying to compile and run the latest version of fgfs, but I have
hit a problem. When I run it I promptly get the error message
Segmentation Fault
There are no other messages.
What I have:
- Redhat 7.1
- automake 1.6.3
- autoconf 2.53
- plib 1.6.0
- yesterday's cvs of Simgear, fgfsbase,
On Wed, 2002-10-23 at 17:39, Michael Selig wrote:
I am trying to compile and run the latest version of fgfs, but I have
hit a problem. When I run it I promptly get the error message
Segmentation Fault
There are no other messages.
What I have:
- Redhat 7.1
- automake 1.6.3
- autoconf
At 10/23/02, Tony Peden wrote:
On Wed, 2002-10-23 at 17:39, Michael Selig wrote:
I am trying to compile and run the latest version of fgfs, but I have
hit a problem. When I run it I promptly get the error message
Segmentation Fault
There are no other messages.
What I have:
- Redhat 7.1
On Wed, 2002-10-23 at 19:14, Michael Selig wrote:
At 10/23/02, Tony Peden wrote:
On Wed, 2002-10-23 at 17:39, Michael Selig wrote:
I am trying to compile and run the latest version of fgfs, but I have
hit a problem. When I run it I promptly get the error message
Segmentation Fault
At 10/23/02, Tony Peden wrote:
On Wed, 2002-10-23 at 19:14, Michael Selig wrote:
At 10/23/02, Tony Peden wrote:
On Wed, 2002-10-23 at 17:39, Michael Selig wrote:
I am trying to compile and run the latest version of fgfs, but I have
hit a problem. When I run it I promptly get the error
Hi,
First things first ... very impressive work, congratulations !!!
Then ... I tried your 0.8.0 binary distribution on a AMD Athlon/1333 with
384MB RAM and GeForce2 PRO/32MB machine running Win98SE/Polish.
Here is a brief report ...
The fgfs.exe runs well (on a couple of occasions the sound
Michael Selig writes:
I am still getting the same segfault w/ this option.
It even promptly crashes w/
./fgfs --help
i.e. I don't get the option list.
Are you missing the base package some how, or pointing to the wrong
directory?
Curt.
--
Curtis Olson IVLab / HumanFIRST Program
I just ran through firing up all the non 172 planes
and there are several JSBsim planes that segfault
x24b
X15
Shuttle
On Wednesday 23 October 2002 10:30 pm, Tony Peden wrote:
On Wed, 2002-10-23 at 19:14, Michael Selig wrote:
At 10/23/02, Tony Peden wrote:
On Wed, 2002-10-23 at 17:39,
I just fixed a bug in the tile freeing code which accounted for the
very long pauses people were seeing after flying for a while.
After a while the tile cache fills up and the oldest entries need to
be purged.
The problem is that to free an entire tile takes mroe that a frame's
worth of time so
At 10/23/02, Curtis Olson wrote:
Michael Selig writes:
I am still getting the same segfault w/ this option.
It even promptly crashes w/
./fgfs --help
i.e. I don't get the option list.
Are you missing the base package some how, or pointing to the wrong
directory?
If I run my working old
At 10/23/02, John Check wrote:
I just ran through firing up all the non 172 planes
and there are several JSBsim planes that segfault
x24b
X15
Shuttle
I have been down this road before. These planes are crashing for some
reason, and the segfault is not the first thing that happens.
This
Shuttle and x24b are experimental in JSBSim. The X-15 worked fine at one
point - I believe Tony gave a full test of this as part of the testing he
did before committing the JSBSim changes involving properties. No major code
changes have occurred since then. Few *minor* changes have occurred.
Is
Can anyone offer some help, here? I do not have a recent build of FlightGear
and cannot build it at the moment for reasons I don't want to go into (that
have nothing to do with FlightGear or my computer). Can someone copy the log
output concerning JSBSim for the X-15 and post it or email to me and
I'm not coming up with any good ideas ... I *thought* that if you
didn't specify --enable-clouds3d, then none of that code was executed,
but perhaps that's not the case ... (?)
From gdb, it's dying in the 3d cloud setup/init but beyond that I'm
not sure why.
Curt.
Jon Berndt writes:
Can
I seem to recall having problems with crashes when starting up with the telnet
interface. Well, the problem really was with subsequent attempts at starting.
I'd see segfaults if the first run didn't exit normal, either through a crash
or other means. At the time I had the line for the telnet
On Wednesday 23 October 2002 11:48 pm, Curtis L. Olson wrote:
I just fixed a bug in the tile freeing code which accounted for the
very long pauses people were seeing after flying for a while.
Cool, but it breaks for gcc3.2 line 704 of tileentry.cxx needs std::cout
And it only happens with *some* *JSBSim* aircraft?
Jon
-Original Message-
From: [EMAIL PROTECTED]
[mailto:flightgear-devel-admin;flightgear.org]On Behalf Of Curtis L.
Olson
Sent: Wednesday, October 23, 2002 11:13 PM
To: [EMAIL PROTECTED]
Subject: RE: [Flightgear-devel] segfault
On Thursday 24 October 2002 12:18 am, Jon Berndt wrote:
And it only happens with *some* *JSBSim* aircraft?
Jon
Heres console output from X15
Starting and initialitoken = OBJECT name = KHAF.btg
zing JSBsim
T,p,rho: 518.67, 2116Start common FDM init
...initializing position...
At 10/23/02, Curtis Olson wrote:
I'm not coming up with any good ideas ... I *thought* that if you
didn't specify --enable-clouds3d, then none of that code was executed,
but perhaps that's not the case ... (?)
From gdb, it's dying in the 3d cloud setup/init but beyond that I'm
not sure why.
28 matches
Mail list logo
