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
Curtis L. Olson wrote:
Yes, in my most recent reply to this company, I asked specifically about
FG support (and support for operating systems not owned and operated by
MS.) It's not necessarily clear from their web page exactly how their
products interface with the computer and how they work
Boris Koenig wrote:
Getting even more extreme, one might ponder about offering that said
company to integrate their webpage address or even company logo directly
into some of the future official FlightGear releases.
No, No No. Never.
This is not going to happen.
Erik
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
Should probably end this thread now, the topic is wondering from being in
the slightest flightgear related.
Bad form to reply to my own post.
I have decided not to go with an nvidia based system because the performance
seems that much worse compared to the 9700 based ati graphics in some
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:
Boris Koenig wrote:
Getting even more extreme, one might ponder about offering that said
company to integrate their webpage address or even company logo directly
into some of the future official FlightGear releases.
No, No No. Never.
This is not going to happen.
lol, didn't
Would these messages be removed before the release ?
WARNING: ssgLoad3ds: Texture coords missing.
WARNING: ssgLoad3ds: Texture coords missing.
WARNING: ssgLoad3ds: Texture coords missing.
WARNING: ssgSGIHeader::: Failed to open
'i:/flightgear/cvs/fgfsbase/Aircraft/MD11/Models/cowlings/SLEEVE.RGB'
Boris Koenig wrote:
SO, instead of taking my mail apart and telling me what's NOT going
to happen it might be more helpful for the final outcome to make
new suggestions
Not really. If you have spent the amount of money on FlightGear as I
have done then you may make any suggestion you like. Until
Frederic Bouvier wrote:
Would these messages be removed before the release ?
WARNING: ssgLoad3ds: Texture coords missing.
WARNING: ssgLoad3ds: Texture coords missing.
WARNING: ssgLoad3ds: Texture coords missing.
WARNING: ssgSGIHeader::: Failed to open
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
Erik Hofman wrote:
Boris Koenig wrote:
SO, instead of taking my mail apart and telling me what's NOT going
to happen it might be more helpful for the final outcome to make
new suggestions
Not really. If you have spent the amount of money on FlightGear as I
have done then you may make any
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
Boris Koenig wrote:
Erik Hofman wrote:
instead of some bozo who just noticed the existence of our
project
This is really getting funny - I didn't expect to have that much
fun here...
(No I'm not referring to you in this case).
Thanks, that's really nice :-)
In case you didn't notice it, I
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
Erik Hofman wrote:
Somebody who types faster than he reads wrote:
Thanks, that's really nice :-)
In case you didn't notice it, I really wasn't referring to you.
Well, thanks for the explanation - but I guess I understood you
correctly :-)
The only problem I have with you, is that you say too much
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
Boris Koenig writes:
Ya, I see - and somehow even gotta agree ... having meanwhile tried to
summarize the Nasal extensions that I would *minimally* need,
Hey I've got an idea !
Why don't you commission one of the FlightGear developers to write
the extensions you seem to *need* and pay for
Norman Vine wrote:
Boris Koenig writes:
Ya, I see - and somehow even gotta agree ... having meanwhile tried to
summarize the Nasal extensions that I would *minimally* need,
Hey I've got an idea !
I am listening ;-)
Why don't you commission one of the FlightGear developers to write
the
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
Boris Koenig writes:
Boris Koenig writes:
Ya, I see - and somehow even gotta agree ... having meanwhile tried to
summarize the Nasal extensions thatsee I would *minimally* need,
_I_ don't *need* a certain extension,
so which is it see quote above
but rather would like to be
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
Actually, fine tuning the AI traffic systems should be high on our priority
list before the next version comes out. Even when the AI is disabled by
default in the new version, as Curt suggested, we should still make a
minimal effort to ensure it's working reasonably well when a user decides
http://www.cs.yorku.ca/~cs233144/MD11.zip
Regards,
Ampere
On July 17, 2004 09:23 am, Frederic Bouvier wrote:
Would these messages be removed before the release ?
WARNING: ssgLoad3ds: Texture coords missing.
WARNING: ssgLoad3ds: Texture coords missing.
WARNING: ssgLoad3ds: Texture coords
The MD-11 has 4 different level of details for parts that have a high
concentration of polygons (engines). I plan to expand it to the entire
aircraft in the future. I am confident that the amount of triangles is small
enough for the traffic manager.
Regards,
Ampere
On July 17, 2004 09:40
Load the aircraft, then zoom in on it in tower view mode. You will see the
lowest level of details.
Regards,
Ampere
On July 17, 2004 11:48 am, Durk Talsma wrote:
Option #2 is my least favorite, even though I'm beginning to agree with
Erik that the current MD11 model is quite heavy in terms
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
System spec:
CPU: Intel(R) Pentium(R) 4 CPU 1.70 GHz
Memory: 512MB
Graphic card: Intel Corp. 82845G/GL[Brookdale-G]/GE Chipset Integrated
Graphics Device (rev01)(prog-if 00 [VGA])
Sound card: Multimedia audio controller: Intel Corp. 82801DB (ICH4) AC'97
Audio Controller (rev 01)
Operating
Hi Ampere,
I'm sorry if I did't explain carefully enough what I wanted to say.
Personally, I haven't had any problems running FlightGear using the MD11,
either as the main aircraft, or as an AI traffic object. I've actually seen
the LOD mechanism work, so that's not the problem. And finally, I
Oh, I forgot to mention:
Durk, this particular version doesn't have the six flight displays that you
put on.
On the subject of flightdisplays, I am still hoping that the MD11 can have a
set of its own.
Regards,
Ampere
On July 17, 2004 01:24 pm, Ampere K. Hardraade wrote:
Is this issue caused by the complexity of the LODs.
How do we speed up the loading process?
Regards,
Ampere
On July 17, 2004 02:23 pm, Durk Talsma wrote:
However, there is also the loading time factor. This is getting quite high,
and especially when done during the simulation, this can cause
Boris Koenig wrote:
But on the other hand I followed the whole discussion about FlightGear
financing and had to notice that most people simply tend to object
against any suggestions that are being made, INSTEAD of making
better suggestions themselves.
I might have missed a message, but I do not
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.
Ampere K. Hardraade wrote:
System spec:
CPU: Intel(R) Pentium(R) 4 CPU 1.70 GHz
Memory: 512MB
Graphic card: Intel Corp. 82845G/GL[Brookdale-G]/GE Chipset Integrated
Graphics Device (rev01)(prog-if 00 [VGA])
Sound card: Multimedia audio controller: Intel Corp. 82801DB (ICH4) AC'97
Audio
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
From: Ampere K. Hardraade [EMAIL PROTECTED]
System spec:
CPU: Intel(R) Pentium(R) 4 CPU 1.70 GHz
Memory: 512MB
Graphic card: Intel Corp. 82845G/GL[Brookdale-G]/GE Chipset Integrated
Graphics Device (rev01)(prog-if 00 [VGA])
Sound card: Multimedia audio controller: Intel Corp. 82801DB
Jacek wrote:
I don't understand morse code so can't compare anything.
Regards
Jacek
S = ...
F = ..-.
O =---
:-)
But regarding that matter, I had to notice that the speed of the morse
code has somehow changed, also it's being played permanently it my
cvs built during startup.
Trying to
There seem to be some issues regarding the XML file processing
and FlightGear's stability:
# Nasal parse error: empty subexpression in command, line 3
# Failed to execute command nasal
# Segmentation fault
One problem seems to be related to using combo boxes with insufficient
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
On July 17, 2004 03:04 pm, Alex Perry wrote:
I'm running AMD64, ATI, Via, Debian, Testing, KDE.
I don't observe your problem #1 so I suspect some other interaction.
LOL... now I can't even run FlightGear. =(
Curt: Is the version of openal in Debian's unstable finally new enough ?
I guess I
Boris Koenig wrote:
Jacek wrote:
I don't understand morse code so can't compare anything.
Regards
Jacek
S =...
F =..-.
O =---
:-)
Do you really distinguish those ... and ---? ;-)
But regarding that matter, I had to notice that the speed of the morse
code has somehow changed, also
Boris Koenig wrote:
There seem to be some issues regarding the XML file processing
and FlightGear's stability:
# Nasal parse error: empty subexpression in command, line 3
# Failed to execute command nasal
# Segmentation fault
One problem seems to be related to using combo boxes with
On Sat, 17 Jul 2004 15:40:45 +0200
Erik Hofman [EMAIL PROTECTED] wrote:
Now that we can specify the texture path of a given model I guess we can
move the 747 and 737 of the static Objects directory into the Models
directory and use that for static models, AIModels and AirTraffic.
Yeah.
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.
Ampere K. Hardraade wrote:
The MD-11 has 4 different level of details for parts that have a high
concentration of polygons (engines). I plan to expand it to the entire
aircraft in the future. I am confident that the amount of triangles is small
enough for the traffic manager.
In the end, or
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
Problem #1 -- fixed after getting the latest OpenAL CVS.
Problem #2 -- fixed after disabling sound in KDE.
Problem #3
On July 17, 2004 05:28 pm, Jacek wrote:
Do you really distinguish those ... and ---? ;-)
Yes. For those who knows morse code, they can tell the difference.
On July 17, 2004
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
Curt: Please add to the Events page. It is not yet clear _when_
the FGFS talk and demo will occur during the three day conference.
Leeds, England
August 6 thru August 8, 2004.
http://www.ukuug.org/events/linux2004/programme/abstract-APerry-2.shtml
Linux 2004
A wide
Alex,
Thanks for your efforts, I've added this to the events page.
Curt.
Alex Perry wrote:
Curt: Please add to the Events page. It is not yet clear _when_
the FGFS talk and demo will occur during the three day conference.
Leeds, England
August 6 thru August 8, 2004.
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
Hi, John:
This is a question for the FlightGear mailing list. I will forward this there.
Jon
-Original Message-
From: [mailto:[EMAIL PROTECTED]
Sent: Friday, July 16, 2004 9:50 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Help 3D model about FlightGear.
Dear Sir:
Hello John,
It will help if you tell us what error message you saw when FlightGear stops.
Chances are that the animation script file couldn't find the object it was
looking for in your mesh file. But like I've said, it will help if we know
what the error is.
Regards,
Ampere
On July 17,
Today's CVS checkout of: OpenAL, PLIB, SimGear, FlightGear and Base package.
On my usual laptop, everything works fine as normal in both configurations:
Config 1= fglrx driver for ATI9600, Kernel 2.4, Debian Testing, 32 bit x86
Config 2= xfree86 unaccelerated, Kernel 2.6, Debian Unstable, pure 64
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.
From: Ampere K. Hardraade [EMAIL PROTECTED]
Please tell me that you don't play FlightGear in wireframe mode. =P
76 matches
Mail list logo
