Curt wrote
Sent: 16 July 2004 16:34
To: FlightGear developers discussions
Subject: [Flightgear-devel] Next release of FlightGear
I've started doing some of the pre-release work for FlightGear-0.9.5
(which is the next release.) That means I'd like to do our official
next release in the
Vivian Meazza wrote:
The Cygwin build of FGFS-cvs appears still to have a problem with the
scenery path.
I've downloaded 0.9.5 scenery via Terrasync into /FlightGear/scenery
This works:
--fg-scenery=/FlightGear/scenery
as does this:
--fg-scenery=/FlightGear/data/scenery
this
Fred wrote
Sent: 19 July 2004 10:20
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Next release of FlightGear
Vivian Meazza wrote:
The Cygwin build of FGFS-cvs appears still to have a problem with the
scenery path.
I've downloaded 0.9.5 scenery via
Frederic Bouvier writes
Norman Vine wrote:
Frederic Bouvier writes:
FG is not using the latest features new cards are offering and the
'old'
features are pretty maxed out now. This is not an explanation for
worst performance but just for lack of improvement. In the meantime,
you
Ampere K. Hardraade wrote:
Please tell me that you don't play FlightGear in wireframe mode. =P
Neh, my O2 does support filled triangles.
Just kidding.
Oh. ;-)
Erik
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
Innis Cunningham wrote:
It is quite possible that the new graphics card/system is not set up for
FG.I will have a play with it and see if I can improve the situation.I
think
anisotropic filtering is on.
The point I was trying to make is people trying FG for the first time will
be dissuaded from
Erik Hofman wrote:
Innis Cunningham wrote:
It is quite possible that the new graphics card/system is not set up for
FG.I will have a play with it and see if I can improve the situation.I
think
anisotropic filtering is on.
The point I was trying to make is people trying FG for the first time
will
Richard Harke wrote:
On Saturday 17 July 2004 07:08 am, Innis Cunningham wrote:
I had a GeForce 2 Titanium with a PIII Xeon at 550MHz getting about 15 fps
over SF Video card crapped out (even has a red LED come on to tell you
it has crapped out) so I bought a Geforce FX 5200 Frame rate dropped to
Erik Hofman wrote:
This is the penalty for those who want eye-candy. If specular
highlighting is supported it will be enabled an make FlightGear slower.
I noticed some enhancements in the new rendering dialog, and would like
to ask how feasible it would be to integrate even more
Boris Koenig wrote:
Erik Hofman wrote:
Well, if we turn all that off, people start to complain that
FlightGear looks like crap and will search for something else. At
least now they start asking questions ...
Then how about optionally offering to disable such things in the
(advanced) rendering
Jonathan Polley wrote:
Fred,
It turns out that the problem should exist on every FlightGear
system, not just the Mac. On exit(), fgExitCleanup() is called which
deletes the globals class and then calls fgOSExit(). The only thing
that fgOSExit() does is turn around and call
Frederic Bouvier wrote:
What about calling SDL_Quit in a function installed by 'atexit', remove
fgOSExit and only rely on exit in all the program ?
The problem is that plib has taken the liberty to call exit() whenever
they feel like it
Erik
___
I wrote
Sent: 17 July 2004 15:22
To: 'FlightGear developers discussions'
Subject: RE: [Flightgear-devel] Next release of FlightGear
Erik Hofman wrote
Sent: 17 July 2004 14:51
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Next release of FlightGear
Vivian
[EMAIL PROTECTED] wrote:
Erik Hofman wrote:
IRIX and Solaris binaries also include it by default.
I'm not sure about other distributions, but I would
encourage them to include it with the distribution.
I include it with the slackware package too.
Is there likely to be a new release of fgrun
On Friday 16 July 2004 17:34, Curtis L. Olson wrote:
I've started doing some of the pre-release work for FlightGear-0.9.5
(which is the next release.) That means I'd like to do our official
next release in the next week or two. Please take a few minutes to
download the tar balls and test
Yep, I just got the same error. I had hoped that rerunning ./autgen.sh would
fix the problem but it appears not to.
Cheers,
Durk
On Saturday 17 July 2004 06:32, Ampere K. Hardraade wrote:
I've got an error during compiliation:
-DPKGLIBDIR=\/usr/share/FlightGear/share/FlightGear\ -g -O2
Indeed, the package only contains fg_os_sdl.cxx. I think it reflects
the packager's ( Curt ) own build option. And the package doesn't include
Network/jpg-httpd.* .
May I suggest to include all the files that are in conditional statement in
Makefile.am to be include inconditionally in an
Curtis L. Olson wrote:
I've started doing some of the pre-release work for FlightGear-0.9.5
(which is the next release.) That means I'd like to do our official
next release in the next week or two. Please take a few minutes to
download the tar balls and test this pre1 release. Please!
I wrote:
Curtis L. Olson wrote:
I've started doing some of the pre-release work for FlightGear-0.9.5
(which is the next release.) That means I'd like to do our official
next release in the next week or two. Please take a few minutes to
download the tar balls and test this pre1
Ampere K. Hardraade wrote:
make[2]: *** No rule to make target `fg_os.cxx', needed by `fg_os.o'.
Good catch. There was a mistake in the build system. This should be
solved in the FlightGear-0.9.5-pre2. (In the mean time you could just
copy the fg_os* files from CVS)
Erik
Frederic Bouvier wrote:
Indeed, the package only contains fg_os_sdl.cxx. I think it reflects
the packager's ( Curt ) own build option. And the package doesn't include
Network/jpg-httpd.* .
May I suggest to include all the files that are in conditional statement in
Makefile.am to be include
Curt wrote
Sent: 16 July 2004 16:34
To: FlightGear developers discussions
Subject: [Flightgear-devel] Next release of FlightGear
I've started doing some of the pre-release work for FlightGear-0.9.5
(which is the next release.) That means I'd like to do our official
next release in the
Vivian Meazza wrote:
SimGear-0.3.6-pre1 will not compile under Cygwin. It fails in
[openal-test1.exe]: cannot find -lalut.
This is using Norman's prebuild libraries, isn't it?
Norman has integrated the alut library and the openal library so the
reference should then be removed in the
Erik Hofman wrote:
Vivian Meazza wrote:
SimGear-0.3.6-pre1 will not compile under Cygwin. It fails in
[openal-test1.exe]: cannot find -lalut.
This is using Norman's prebuild libraries, isn't it?
Norman has integrated the alut library and the openal library so the
reference should then
Frederic Bouvier wrote:
Erik Hofman wrote:
Vivian Meazza wrote:
SimGear-0.3.6-pre1 will not compile under Cygwin. It fails in
[openal-test1.exe]: cannot find -lalut.
This is using Norman's prebuild libraries, isn't it?
Norman has integrated the alut library and the openal library so the
Ampere K. Hardraade wrote:
I've got an error during compiliation:
-DPKGLIBDIR=\/usr/share/FlightGear/share/FlightGear\ -g -O2 -D_REENTRANT -c
-o viewer.o `test -f viewer.cxx || echo './'`viewer.cxx
source='viewmgr.cxx' object='viewmgr.o' libtool=no \
depfile='.deps/viewmgr.Po'
Since there is a new release coming, I decided to bring the Mac version
back up to date (I've been busy otherwise). When I exit FlightGear, I
get the following errors (and crash).
*** malloc[8626]: Deallocation of a pointer not malloced: 0x18bef000;
This could be a double free(), or free()
Erik Hofman wrote
Sent: 17 July 2004 10:27
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Next release of FlightGear
Vivian Meazza wrote:
SimGear-0.3.6-pre1 will not compile under Cygwin. It fails in
[openal-test1.exe]: cannot find -lalut.
This is using
Line 92 of globals.cxx seems ok. subsystem_mgr was allocated with a
new operator in line 45. Could you put a breakpoint at line 92 to see
if on your system, the destructor is not called twice ?
-Fred
Jonathan Polley wrote:
Since there is a new release coming, I decided to bring the Mac
Vivian Meazza wrote:
Once the offending entries are removed from simgear/sound, simgear compiles
correctly, but Norman's pre-built libraries were still present. I'll remove
those and try again.
Nono, that's not what I meant.
Norman once build a separate library for alut and openal, but in the end
Hi Curt
I downloaded the windows binaries last night for
9.4 and the problem of the drop down menu's
locking the sim up still seem to exist.Even if you
go to exit FG and then select cancel the sim locks up.
The reason that I downloaded the binaries was that I
have just built a new box,that I am
Erik Hofman wrote
Sent: 17 July 2004 14:51
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Next release of FlightGear
Vivian Meazza wrote:
Once the offending entries are removed from simgear/sound, simgear
compiles
correctly, but Norman's pre-built libraries
Vivian Meazza wrote:
I'm a bit confused now!
There is really no need to be confused.
Norman's last version put all the stuff into openal
Good. That part is fixed in CVS no.w
Unless test1 and test2 do something useful they can be easily removed from
simgear/sound/makefile.am
We sometimes include
On Sat, 17 Jul 2004 09:34:24 +0200, Frederic wrote in message
[EMAIL PROTECTED]:
I wrote:
Curtis L. Olson wrote:
I've started doing some of the pre-release work for
FlightGear-0.9.5(which is the next release.) That means I'd like
to do our official next release in the next week
Innis Cunningham wrote:
Hi Curt
I downloaded the windows binaries last night for
9.4 and the problem of the drop down menu's
locking the sim up still seem to exist.Even if you
go to exit FG and then select cancel the sim locks up.
Hey Innis,
you just downloaded the release that is 3
I was too quick to press the reply button. I now see your
motivations, so receive all my apologies.
Frederic Bouvier wrote:
Innis Cunningham wrote:
Hi Curt
I downloaded the windows binaries last night for
9.4 and the problem of the drop down menu's
locking the sim up still seem to
Frederic Bouvier writes:
Also I noticed that in the 9.4 base the runfgfs bat file has been
removed.
Was there a reason for this.
It has been supercede by fgrun that is much user frendly.
Until fgrun is distributed with FGFS I 'vote' for the batch file being
reinstalled in the
Norman Vine wrote:
Frederic Bouvier writes:
Also I noticed that in the 9.4 base the runfgfs bat file has been
removed.
Was there a reason for this.
It has been supercede by fgrun that is much user frendly.
Until fgrun is distributed with FGFS I 'vote' for the batch file
Scrubbing FlightGear because of framerates was excatly what a friend of mine
did. I agree with Innis that someone should fix this problem.
Regards,
Ampere
On July 17, 2004 10:08 am, Innis Cunningham wrote:
The following tests were done using windows 98SE
The old box was a 850meg duron with
Frederic Bouvier writes:
Norman Vine wrote:
Frederic Bouvier writes:
Also I noticed that in the 9.4 base the runfgfs bat file has been
removed.
Was there a reason for this.
It has been supercede by fgrun that is much user frendly.
Until fgrun is distributed with
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Frederic
Bouvier
Sent: Saturday, July 17, 2004 12:20 PM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Next release of FlightGear
I was too quick to press the reply button. I
Frederic Bouvier writes:
FG is not using the latest features new cards are offering and the 'old'
features are pretty maxed out now. This is not an explanation for
worst performance but just for lack of improvement. In the meantime,
you probably switched to another setup/resolution that can
Norman Vine wrote:
Frederic Bouvier writes:
Norman Vine wrote:
Frederic Bouvier writes:
Also I noticed that in the 9.4 base the runfgfs bat file has
been
removed.
Was there a reason for this.
It has been supercede by fgrun that is much user frendly.
Frederic Bouvier wrote:
Norman Vine wrote:
Perhaps merntion of this should be made as a 'dependenciy'
then on http://www.flightgear.org/Downloads/source.html
Sorry Norman, but I don't understand. FlightGear does not depend on fgrun.
It is just in the Win32 binary package since 0.9.3 and probably
Norman Vine wrote:
Frederic Bouvier writes:
FG is not using the latest features new cards are offering and the 'old'
features are pretty maxed out now. This is not an explanation for
worst performance but just for lack of improvement. In the meantime,
you probably switched to another
Fred,
It turns out that the problem should exist on every FlightGear
system, not just the Mac. On exit(), fgExitCleanup() is called which
deletes the globals class and then calls fgOSExit(). The only thing
that fgOSExit() does is turn around and call exit(), which repeats the
process.
Norman Vine wrote:
Frederic Bouvier writes:
fgrun is installed by fgsetup. It is launched when you double-click on
the FG icon.
Cool,
Perhaps merntion of this should be made as a 'dependenciy'
then on http://www.flightgear.org/Downloads/source.html
IRIX and Solaris binaries also include it
Ampere K. Hardraade wrote:
Scrubbing FlightGear because of framerates was excatly what a friend of mine
did. I agree with Innis that someone should fix this problem.
The following tests were done using windows 98SE
The old box was a 850meg duron with 256 meg ram and
a GF4-MX-440 64meg graphics
Please tell me that you don't play FlightGear in wireframe mode. =P
Just kidding.
Regards,
Ampere
On July 17, 2004 04:54 pm, Erik Hofman wrote:
This is the penalty for those who want eye-candy. If specular
highlighting is supported it will be enabled an make FlightGear slower.
Erik
Frederic Bouvier wrote:
Just a thought :
Maybe it would be wise to have a TerraGear release that match released
SimGear as well ? That would avoid question about compatibility issues
that are only resolved in CVS.
Yes, I'm planning to do that soon, time permitting ...
Curt.
--
Curtis Olson
Erik Hofman wrote:
IRIX and Solaris binaries also include it by default. I'm not sure about
other distributions, but I would encourage them to include it with the
distribution.
I include it with the slackware package too.
Is there likely to be a new release of fgrun before the release of 0.9.5
Erik Hofman wrote:
IRIX and Solaris binaries also include it by default.
I'm not sure about other distributions, but I would
encourage them to include it with the distribution.
I include it with the slackware package too.
Is there likely to be a new release of fgrun before the
The file or
folder /site/ftp.flightgear.org/flightgear-ftp/Source/FlightGear-0.9.5-pre1.tar.gz
does not exist.
Did anyone encounter this problem?
Regards,
Ampere
On July 16, 2004 11:34 am, Curtis L. Olson wrote:
I've started doing some of the pre-release work for FlightGear-0.9.5
(which is
Ampere K. Hardraade wrote:
The file or
folder /site/ftp.flightgear.org/flightgear-ftp/Source/FlightGear-0.9.5-pre1.tar.gz
does not exist.
Did anyone encounter this problem?
Most likely sunsite hasn't sync'd it's mirror yet. You can always go
direct to ftp://ftp.flightgear.org
Regards,
Curt and others,
Just a quick question: Does this mean, we're entering a feature-freeze period
now? The reason I'm asking is that I have some upates for the traffic manager
that I was planning to clean-up a bit and submit by the end of the weekend.
This new code, while humble in size, is going
Ampere K. Hardraade wrote:
The file or
folder /site/ftp.flightgear.org/flightgear-ftp/Source/FlightGear-0.9.5-pre1.tar.gz
^^
does not exist.
Simply put a de. in there,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
Durk Talsma wrote:
Curt and others,
Just a quick question: Does this mean, we're entering a feature-freeze period
now?
Yes, I apologize for not being 100% clear ... I'm juggling way too many
things this summer, but I'm still trying to get a release out.
The reason I'm asking is that I have
I've got an error during compiliation:
-DPKGLIBDIR=\/usr/share/FlightGear/share/FlightGear\ -g -O2 -D_REENTRANT -c
-o viewer.o `test -f viewer.cxx || echo './'`viewer.cxx
source='viewmgr.cxx' object='viewmgr.o' libtool=no \
depfile='.deps/viewmgr.Po' tmpdepfile='.deps/viewmgr.TPo' \
depmode=gcc3
Oh, I forgot to mention, I installed simgear in /usr/share/simgear and tried
to do the same with FlightGear in /usr/share/FlightGear.
I used the following commands when I was compiling FlightGear:
./configure --prefix=/usr/share/FlightGear --with-simgear=/usr/share/simgear
make (with the error
Correction:
Not only is fgfs missing, but so are metar, terrasync, and (est-epsilon?).
Regards,
Ampere
On July 17, 2004 12:42 am, Ampere K. Hardraade wrote:
Oh, I forgot to mention, I installed simgear in /usr/share/simgear and
tried to do the same with FlightGear in /usr/share/FlightGear.
I
60 matches
Mail list logo
