I'll wrap up the new traffic files tonight. I the mean time, I've add small
tar file containing the necessary traffic files. Should work, but haven't had
much chance of testing it.
Cheers,
Durk
On Friday 23 July 2004 07:21, Frederic Bouvier wrote:
Jonathan Polley wrote:
I just updated
Jonathan Polley wrote:
I just updated tonight and FlightGear no longer runs on the Mac. As of
last night, everything ran just file, but after updating everything
(SimGear, FlightGear, and base packages) I get an abort.
Oops, sorry all. This is caused by me not including a bunch of
Erik Hofman
Sent: 23 July 2004 08:52
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Latest CVS Aborts
Jonathan Polley wrote:
I just updated tonight and FlightGear no longer runs on the Mac. As of
last night, everything ran just file, but after updating
Vivian Meazza wrote:
Erik Hofman
Sent: 23 July 2004 08:52
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Latest CVS Aborts
Jonathan Polley wrote:
I just updated tonight and FlightGear no longer runs on the Mac. As of
last night, everything ran just file
Frederic Bouvier asked
Sent: 23 July 2004 11:14
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Latest CVS Aborts
Vivian Meazza wrote:
Erik Hofman
Sent: 23 July 2004 08:52
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Latest CVS
I wrote
Sent: 23 July 2004 11:49
To: 'FlightGear developers discussions'
Subject: RE: [Flightgear-devel] Latest CVS Aborts
Frederic Bouvier asked
Sent: 23 July 2004 11:14
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Latest CVS Aborts
Vivian
Vivian Meazza wrote:
I've re-downloaded the current cvs. Here's the backtrace
...
Can't say that it means anything to me! Is it any good to you, or can I do
something else?
It looks like useless garbage, sorry. Do you run fg with --log-level=bulk
or whatever is the most verbose ( I don't
Frederic Bouvier wrote:
Vivian Meazza wrote:
I've re-downloaded the current cvs. Here's the backtrace
...
Can't say that it means anything to me! Is it any good to you, or can I do
something else?
It looks like useless garbage, sorry. Do you run fg with --log-level=bulk
or
Curtis L. Olson writes:
You have to compile with -g to include debugging symbols so that the
back trace makes sense. That said, the very few times I've tried to run
gdb with flightgear on windows, I was never very successful.
GDB might have some problems on 95,98 and WinMe, but runs fine
Norman Vine wrote
Sent: 23 July 2004 14:15
To: FlightGear developers discussions
Subject: RE: [Flightgear-devel] Latest CVS Aborts
Curtis L. Olson writes:
You have to compile with -g to include debugging symbols so that the
back trace makes sense. That said, the very few times I've
Frederic Bouvier asked
Sent: 23 July 2004 13:51
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Latest CVS Aborts
Vivian Meazza wrote:
I've re-downloaded the current cvs. Here's the backtrace
...
Can't say that it means anything to me! Is it any good to you
I wrote
Sent: 23 July 2004 14:39
To: 'FlightGear developers discussions'
Subject: RE: [Flightgear-devel] Latest CVS Aborts
Frederic Bouvier asked
Sent: 23 July 2004 13:51
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Latest CVS Aborts
Vivian Meazza
I just updated tonight and FlightGear no longer runs on the Mac. As of
last night, everything ran just file, but after updating everything
(SimGear, FlightGear, and base packages) I get an abort. The gdb
backtrace is:
Using Mac OS X hack for initializing C++ stdio...
Failed to find runway
Jonathan Polley wrote:
I just updated tonight and FlightGear no longer runs on the Mac. As of
last night, everything ran just file, but after updating everything
(SimGear, FlightGear, and base packages) I get an abort. The gdb
backtrace is:
...
It is the same for everybody until some
Hi,
I have just tried a cvs update and the compile of flightgear results in an
error. I also did a cvs update and compile of plib and simgear without
error. The error recieved is as follows:
++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src
-I/scratch/simgear//include
I might have an idea to what is causing my error. A cvs update -d -P is
not updating my files in /Main. I have modified them and it is not
merging my version with the cvs. My globals.hxx is version $Id:
globals.hxx,v 1.26 2003/11/25 21:08:37 curt Exp $ while the latest
globals.hxx is $Id:
John Barrett wrote:
just tried building latest cvs and got the following error:
make[3]: Entering directory `/cygdrive/c/Documents and
Settings/jbarrett/Desktop/FlightSim/Devel/cvsroot/source/src/Cockpit'
if
++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/usr/X
11R6/include
On Friday 28 November 2003 10:13, Erik Hofman wrote:
John Barrett wrote:
just tried building latest cvs and got the following error:
make[3]: Entering directory `/cygdrive/c/Documents and
Settings/jbarrett/Desktop/FlightSim/Devel/cvsroot/source/src/Cockpit'
if
++ -DHAVE_CONFIG_H -I.
[EMAIL PROTECTED] wrote:
anyone else getting this one ??
No problem here. Maybe this is a classic case of mixed version?
Erik
Doesn't make and cvs solve that automatically?
Or in another words, what is the best way to upgrade your personal cvs
directory with the new one and recompile it?
On Friday 28 November 2003 15:22, Erik Hofman wrote:
It is. Except in this case (it turns out this adTask is a SimGear
function so you need to update and install SimGear also).
Erik
Thanks for answering.
BTW is there a way to know when i need (or don't need) to upgrade
SimGear or Plib when
[EMAIL PROTECTED] wrote:
No problem here. Maybe this is a classic case of mixed version?
Erik
Doesn't make and cvs solve that automatically?
Or in another words, what is the best way to upgrade your personal cvs
directory with the new one and recompile it?
Why is
$ cvs update
$
John Barrett writes:
just tried building latest cvs and got the following error:
make[3]: Entering directory `/cygdrive/c/Documents and
Settings/jbarrett/Desktop/FlightSim/Devel/cvsroot/source/src/Cockpit'
if
++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/usr/X
John Barrett wrote:
radiostack.cxx: In member function `virtual void FGRadioStack::init()':
radiostack.cxx:81: error: `addTask' undeclared (first use this function)
You need to update your SimGear. The SGEventManager API changed a
little bit recently, and radiostack.cxx was updated along with
- Original Message -
From: Andy Ross [EMAIL PROTECTED]
To: FlightGear developers discussions [EMAIL PROTECTED]
Sent: Friday, November 28, 2003 12:09 PM
Subject: Re: [Flightgear-devel] Latest cvs build error ??
John Barrett wrote:
radiostack.cxx: In member function `virtual void
just tried building latest cvs and got the following error:
make[3]: Entering directory `/cygdrive/c/Documents and
Settings/jbarrett/Desktop/FlightSim/Devel/cvsroot/source/src/Cockpit'
if
++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/usr/X
11R6/include -g -O2 -MT
Eric,
With the latest CVS changes I getting a compile error:
Making all in Main
make[2]: Entering directory `/home/curt/projects/FlightGear-0.9/source/src/Main'
source='globals.cxx' object='globals.o' libtool=no \
depfile='.deps/globals.Po' tmpdepfile='.deps/globals.TPo' \
depmode=gcc3 /bin/sh
Curtis L. Olson wrote:
Eric,
With the latest CVS changes I getting a compile error:
Making all in Main
make[2]: Entering directory `/home/curt/projects/FlightGear-0.9/source/src/Main'
source='globals.cxx' object='globals.o' libtool=no \
depfile='.deps/globals.Po' tmpdepfile='.deps/globals.TPo' \
Erik Hofman wrote:
Curtis L. Olson wrote:
Erik,
With the latest CVS changes I getting a compile error:
Any ideas?
It looks like the compiler is mixing up two function calls with
different parameters because one is defined with the template.
This should be fixed now.
Unfortunately this required
Just to double check, David made a change to SimGear and to the some
of the aircraft config files yesterday. Without the change to
simgear, flightgear will crash on startup.
If that's not it, then we'll have to take a closer look, although your
line numbers don't make sense in your back trace
Curt,
I updated plib, SimGear, and FlightGear before rebuilding. I cleaned
everything on Windows because there were some changes to plib headers
(MSVC isn't always smart enough to properly handle header changes if
they are not in YOUR project). I haven't cleaned the MacOS build
because gcc
Jonathan Polley writes:
I updated plib, SimGear, and FlightGear before rebuilding. I cleaned
everything on Windows because there were some changes to plib headers
(MSVC isn't always smart enough to properly handle header changes if
they are not in YOUR project). I haven't
Jonathan Polley wrote:
I updated plib, SimGear, and FlightGear before rebuilding. I cleaned
everything on Windows because there were some changes to plib headers
(MSVC isn't always smart enough to properly handle header changes if
they are not in YOUR project). I haven't cleaned the MacOS
Andy,
That fixed the problem. Thanks!
Jonathan Polley
On Tuesday, November 12, 2002, at 03:21 PM, Andy Ross wrote:
Jonathan Polley wrote:
I updated plib, SimGear, and FlightGear before rebuilding. I cleaned
everything on Windows because there were some changes to plib headers
(MSVC
I just updated from CVS for both the Mac and Windows and got the same
error when I tried to run. The Mac traceback is as follows:
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x0006
Thread 0 Crashed:
#0 0x000525f8 in ssgContext::forceBasicState()
after the merge of the cube sides in the attitude ball i now have one
huge ball sitting in the middle of the panel. you can find a picture
at http://caliban.lbl.gov/fgfs-screen-002.ppm.
also, i looked at pictures of the a4 panel and i didn't see such an
instrument.
--alex--
--
| I believe the
Alex Romosan wrote:
after the merge of the cube sides in the attitude ball i now have one
huge ball sitting in the middle of the panel. you can find a picture
at http://caliban.lbl.gov/fgfs-screen-002.ppm.
I goofed the radius, sorry. It's currently a 7cm wide ball, which is
too small, but
On Sun, 19 May 2002 15:34:52 -0300 (ART),
Flavio Villanustre [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]:
On Sun, 19 May 2002, Alex Perry wrote:
Xlib: extension GLXUnsupportedPrivateRequest missing on
display :0.0. GLUT: Fatal Error in fgfs: visual with necessary
FYI
I run RH 7.3, plib cvs, simgear cvs, fgfs cvs and base cvs, and use NVidia
drivers and don't experience any of these problems. I suspect that your
solutions are not entirely necessary, maybe when you upgraded you might have
forgot that the XFree devel rpm probably sticks in a new libGL
I've just updated my Simgear, Flightgear, fgfsbase trees from CVS and
compiled them. But when I try to run fgfs it exits with next error:
Processing command line arguments
Finished command line arguments
Opening a window: 1024x768
game mode params = width=1024 height=768 bpp=16
Xlib:
Flavio Villanustre writes:
I've just updated my Simgear, Flightgear, fgfsbase trees from CVS and
compiled them. But when I try to run fgfs it exits with next error:
Processing command line arguments
Finished command line arguments
Opening a window: 1024x768
game mode params =
Xlib: extension GLXUnsupportedPrivateRequest missing on display :0.0.
GLUT: Fatal Error in fgfs: visual with necessary capabilities not found.
Hah! Try running something that uses full texturing such as gloss;
the differences in private requests between GL implementations generally
appear
On Sun, 19 May 2002, Alex Perry wrote:
Xlib: extension GLXUnsupportedPrivateRequest missing on display :0.0.
GLUT: Fatal Error in fgfs: visual with necessary capabilities not found.
Hah! Try running something that uses full texturing such as gloss;
the differences in private requests
Flavio Villanustre writes:
I've just updated my Simgear, Flightgear, fgfsbase trees from CVS and
compiled them. But when I try to run fgfs it exits with next error:
Processing command line arguments
Finished command line arguments
Opening a window: 1024x768
game mode params = width=1024
On Sun, 19 May 2002, Norman Vine wrote:
Try running FGFS with no commandline parameters
or simply --geometry=1024x768
Your problem may be related to requesting gamemode
and/or bpp=16
Norman, tried both with no success. Now I'm looking at a libGL.a that
XFree86-devel rpm from RedHat 7.3
On Sun, 19 May 2002, Flavio Villanustre wrote:
Norman, tried both with no success. Now I'm looking at a libGL.a that
XFree86-devel rpm from RedHat 7.3 has dropped into /usr/X11R6/lib.
As soon as I have a clue I'll let you know to warn other people migrating
to RedHat 7.3.
I've finally
Anyone up for a 0.7.10 release sometime soon?
I wouldn't object a 0.7.10 release as long as where were at least two or
three weeks for fixing obvious known bugs that prevent users from using
functionality that is _supposed_ to be usuable right now (see my posting on
the Beech99).
In the
On Friday 19 April 2002 04:34 am, you wrote:
Jim Wilson wrote:
As for the numbering, how about jumping to 0.8 and then continuing on as
we have? This will look like a pretty major update with the new models
and 3d internal view.
I would think 0.8.0 is reserved for a *stable* release.
* [EMAIL PROTECTED] (Curtis L. Olson) [2002.04.19 21:24]:
Anyone up for a 0.7.10 release sometime soon? If anyone wants a real
time wasting discussion, what do people think about switching from
0.7.10, 0.7.11, 0.7.12, etc. to going 0.8, 0.9, 1.0, 1.1, 1.2, 1.3,
that way it looks like our
On Behalf Of Cameron Moore
What exactly do we want 1.0 to be? Here are some things I'd like to see
in 1.0:
- Runway lighting
- Sane gear model in JSBSim
In work, as we speak. Of course, this has been in work for months, and
is likely to continue to be for at least days if not weeks.
-
A fair amount has changed in cvs today. If you are tracking cvs, make
sure you update both your FlightGear cvs tree and your base package
cvs tree ... otherwise you will have problems.
The view manager code is really shaping up, David made some nice
changes to the C172 3d model, I fixed a crash
Curtis L. Olson [EMAIL PROTECTED] said:
Anyone up for a 0.7.10 release sometime soon? If anyone wants a real
time wasting discussion, what do people think about switching from
0.7.10, 0.7.11, 0.7.12, etc. to going 0.8, 0.9, 1.0, 1.1, 1.2, 1.3,
that way it looks like our development is
Jim Wilson writes:
Curtis L. Olson [EMAIL PROTECTED] said:
Anyone up for a 0.7.10 release sometime soon? If anyone wants a real
time wasting discussion, what do people think about switching from
0.7.10, 0.7.11, 0.7.12, etc. to going 0.8, 0.9, 1.0, 1.1, 1.2, 1.3,
that way it looks
Hi,
the latest version (updated everything, incl. base) doesn't run for me
(MSVC as usual) as it's hooked up in an endless loop in cloud.cxx again.
I thought we had that fixed already :( Can anybody remember the patch?
CU,
Christian
--
The idea is to die young as late as possible.--
?
-Fred
- Original Message -
From: Christian Mayer [EMAIL PROTECTED]
To: FGFS [EMAIL PROTECTED]
Sent: Tuesday, February 12, 2002 3:30 PM
Subject: [Flightgear-devel] Latest CVS doesn't run
Hi,
the latest version (updated everything, incl. base) doesn't run for me
(MSVC as usual
Tony Peden writes:
On Tuesday 04 December 2001 03:54 pm, you wrote:
Just downloaded latest FG CVS and base package @ 5:20 PST
Downloaded both c172 model and c310 model from JSB sourceforge;
c172 comes up just fine
c310 bombs :
Reading thruster from file:
Mmmm... I can reproduce the first freeze I was refering to, almost 100% of
the times...
Do this,
start from KSFO, normal heading, start engine with throttle set to MAX and
pull the joystick to force the plane raise ASAP... with some luck you'll
get FGFS frozen in 15 to 20 seconds (just a few
Curt,
maybe you were right and the sound system is responsible for the
freezes... I got it to hang again while debugging and I saw this from a
backtrace in gdb:
(gdb) backtrace
#0 slSamplePlayer::skip (this=0x9499798, nframes=1024) at sl.h:260
#1 0x08308cc1 in slPlayer::preempt
no terrain intersection
no terrain intersection
load() base = /usr/local/lib/FlightGear/Scenery
Loading tile
/usr/local/lib/FlightGear/Scenery/w180n1879048190/w180n1879048191/5712
This is (most likely) caused by the current lack of crash protection in
JSBSim. What's happening here
Flavio Villanustre writes:
I saw a different kind of crash (literally)... After crashing against a
mountain, everything became unresponsive and the engines suddenly stopped.
I couldn't turn the engine back on and the pannel looked funny, with
missing needles, instruments, etc. (I regret
Jon S. Berndt writes:
I am trying to add some logic in there that freezes the model when
a crash occurs. The problem is coming up with a set of cases that
works for crash detection. This is hard to do accurately without a
surface normal and knowing which triangle a contact point is on.
60 matches
Mail list logo
