[Flightgear-devel] Re: unhandled write
* Wendell Turner -- Wednesday 16 November 2005 04:16: > However, with this evening's CVS, with that argument, I > get this: > WARNING: Network: 17: unhandled write > Bus error > and fgfs halts. [...] > plib, simgear, fgfs, data: cvs updated as of 15.nov.05 10pm ET plib CVS/HEAD has broken networking code. Revert the last changes in net/netSocket.h and net/netSocket.cxx and try again! m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] impending v0.9.9 release
Hi, On Mittwoch 16 November 2005 04:12, Ampere K. Hardraade wrote: > On November 15, 2005 12:39 pm, Curtis L. Olson wrote: > > However, I would like to give everyone the opportunity to mention any > > show stopping bugs that we should be concerned about. > > For some reasons, the logic between line 1832 and 1858 in RenderTexture.cpp > is causing X to throw GLXUnsupportedPrivateRequest for those who are using > r200 driver. The problem would be gone if one were to make an early exist > by adding "return false;" before line 1832. Well, that will in effect turn off everything using the rendertexture code. I would vote against that ... Would it be possible not to initialize the rendetexture code if we don't need it, e.g. we have not 3d clouds enabled? Does somebody have objections? Greetings Mathias -- Mathias Fröhlich, email: [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] thermals gone ?
Hi ! I've just tried the 0.9.9-pre3 Very nice 3d clouds indeed ! ( fliing around with the ufo is great :) but, what has happened to the thermal scenario ? i tried to fly the sgs233, but this leads to : 'terminate called after throwing an instance of 'sg_io_exception'' any ideas ? thanks -- Patrice Poly Attention! Il y a des gens derrière les ordinateurs! ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] unhandled write
Monday's CVS seemed to work fine. If the command line included the argument --telnet=8898 fgfs ran ok. However, with this evening's CVS, with that argument, I get this: WARNING: Network: 17: unhandled write Bus error and fgfs halts. I don't mean to whine about bugs; I realize that everyone is working hard on getting v0.9.9 out. I'll try to look into this, but others may know more about this than myself. Wendell os: Fedora 4 hw: AMD64 plib, simgear, fgfs, data: cvs updated as of 15.nov.05 10pm ET ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] impending v0.9.9 release
On November 15, 2005 12:39 pm, Curtis L. Olson wrote: > However, I would like to give everyone the opportunity to mention any > show stopping bugs that we should be concerned about. For some reasons, the logic between line 1832 and 1858 in RenderTexture.cpp is causing X to throw GLXUnsupportedPrivateRequest for those who are using r200 driver. The problem would be gone if one were to make an early exist by adding "return false;" before line 1832. Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: [BUG] environemnt_ctrl.cxx: exception triggers SGThread assert()
* Melchior FRANZ -- Monday 14 November 2005 22:29: > The strange thing is, that the return value that triggers assert() > is 35, or EAGAIN (Linux). This makes no sense. It's neither described > on the pthread_join manpage, nor is it used in any implementation that > I found on the net. BS! I've no idea where I looked that up. 35 is EDEADLK (deadlock: "Resource deadlock would occur"). Reason according to "man pthread_join": EDEADLK The th argument refers to the calling thread. So this code is trying to join itself? m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] impending v0.9.9 release
Curtis L. Olson a écrit : Christian Mayer wrote: Great! Will there be a Windows binary prerelease to test it? Fred is the windows build guru. I believe he posts his latest builds someplace, although I haven't tracked the url lately. Might be able to find it if you search the archives, or maybe Fred will be willing to remind us again if he's still awake. ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/fgfs-0.9.9-pre3-win32.zip -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] local time?
Question: I see that simgear has functions to return current time (GMT). I see that the simgear sg_time.cxx keeps track of a local timezone offset in seconds. Is there any easy way to get the 'local' time split out into HH MM SS. Are these already tucked away in our property system some place? Thanks, Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Problems in the latest CVS version
On Tuesday 15 November 2005 15:02, Dai Qiang wrote: > I actually did nothing but started with the following > commmand: fgfs > --fg-root=/home/azuron/Project/CVS/FG/data > --aircraft=hunter --carrier=Nimitz > The situation was like what I just decribed from the > beginning. I just tried that myself - SG and FG from late last night; the Hunter seemed to stay in the one place as it should with the brakes on... > I have tried Shift + b and it was the same. It's > especially weired that when I pressed P to pause the > simulation, Hunter started to move forward according > to the carrier. I am really confused. :-/ I do know that the carrier is not really compatible with pausing the sim (at least that was the case a month or two ago; I've been working on other stuff recently and not testing the carrier much. I'd be suspicious that you haven't got a clean cvs tree there and still have some old stuff hanging around. You did remember to "make install" didn't you? I know I've forgotten at times in the past... Cheers, AJ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] impending v0.9.9 release
Christian Mayer wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Curtis L. Olson schrieb: Hi all, I would really like to get v0.9.9 out the door this week ... Great! Will there be a Windows binary prerelease to test it? Geoff has put a binary here : http://geoffmclane.com/fg/fgfs-018.htm Harald. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] impending v0.9.9 release
Vassilii Khachaturov wrote: I'm very much concerned about the buggy exception throwing pattern that flightgear and simgear have (ab)used, and have circa 100 throws to verify and modify their vicinity in some cases. I have not started this work yet, so if somebody wants to do it before Friday night, go ahead. Furthermore, I can not commit at anything right now, because things happen outside of flightgear (e.g., 15 minutes ago my 3-year-old daughter turned out to have fever, and this may steal whatever free time I have planned for the next week altogether). Hi Vassilii, I do share your concern, however, our exception throwing implimentation is not anything new. If we do have something messed up, it's been that way for several releases. So let's get this next release out and then attack this problem before the following release. Thanks, Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] impending v0.9.9 release
> I would really like to get v0.9.9 out the door this week ... maybe > committing to the final source code version on thursday or friday. The earliest time slot I might possibly have at serious hacking of fgfs is this Friday night. > However, I would like to give everyone the opportunity to mention any > show stopping bugs that we should be concerned about. It's ok to report > bugs, but at this point we really need people reporting *fixes*. The > magic source code gods have this week off so we are going to have to fix > all the bugs ourselves. :-) I'm very much concerned about the buggy exception throwing pattern that flightgear and simgear have (ab)used, and have circa 100 throws to verify and modify their vicinity in some cases. I have not started this work yet, so if somebody wants to do it before Friday night, go ahead. Furthermore, I can not commit at anything right now, because things happen outside of flightgear (e.g., 15 minutes ago my 3-year-old daughter turned out to have fever, and this may steal whatever free time I have planned for the next week altogether). V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] The right way to use the property manager?
Kitts wrote:
Hi all,
I have been doing some coding and using the property manager in flightgear
but i want to know what is the right way to do it.
I use the method "fgGetNode("/path/to/property", true)" to get an existing
property or create one if not there. There are a few things i want to know
that i list below:
1) A node that is used in the flight system also results in the method
"isTied" failing and the It does allow me to tie this already existing
property to a variable?!? Is this the expected behavior? Isn't the property
supposed to be tied to a variable somewhere already?
No, properties are not stored by default in the program 'variables',
that's why they are not tied.
In practice however there is a lot of properties wich have some get/set
code associated with
them, and very few wich are directly tied to a variable.
2) When a property did not previously exist, is it necessary to create a
variable and tie the node to that variable? I find the system to be working
either ways. If i do not tie it, the property is displayed as "double" in
the property browser else it displays the data type that it has been tied
to.
If it's tied to a variable then the property will allways be of the
right type. Else it will has the type
you gave it when you created it / accessed it the first time. Even if
you write something in another
type it will keep it's creation type. The props functions are doing all
the casting for you.
3) When the property has been explicitly tied, no matter what the value is
initialized to using the "setDoubleValue" method the property browser shows
the value as zero. This display of zero does not happen when the property
is not tied explicitly.
Perhaps are you overwriting the value in your code (and why would you
use setdoublevalue in your
own code when you can directly write in the container variable ?). Look
at the AIBase class,
they use tied properties and you can check the values in the property
browser. Btw, for properties tied
or having a setter function, the property browser *won't* update the
value displayed when the
property change. You must close/open the property browser to see the change.
4) I would also like to add a change listener to the class that i have
written so that the class is informed as and when a variable being watched
has changed value. I believe the way to do this is to use the
"SGPropertyChangeListener" class as a base class and implement the
"valueChanged" method to do the job. Is this correct?
I think, never done it myself. Note that if you own the property you can
also use a set function
to update its value, and then you allways know when the property has
changed.
So now, back to my question. What is the right way to use the property
manager? Which are the right methods that are to be used and in what
sequence?
If you own the property and you manage it I think the usual way is to
use the C++ style, ie you use a get and a set function to access the
member, so you can use fgTie(propertyname, this, get_function,
set_function).
If it's not your property then you use fgGetXXX.
Harald.
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] impending v0.9.9 release
Christian Mayer wrote: Great! Will there be a Windows binary prerelease to test it? Fred is the windows build guru. I believe he posts his latest builds someplace, although I haven't tracked the url lately. Might be able to find it if you search the archives, or maybe Fred will be willing to remind us again if he's still awake. Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] impending v0.9.9 release
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Curtis L. Olson schrieb: > Hi all, > > I would really like to get v0.9.9 out the door this week ... Great! Will there be a Windows binary prerelease to test it? CU, Christian -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) iD8DBQFDejaVlhWtxOxWNFcRAoOYAKCY+EQIEVYLxGe119ZR5vd97fMuNgCfe1rv T0a1k27gnv51OUiCanbFKxg= =l+7o -END PGP SIGNATURE- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] impending v0.9.9 release
Curtis L. Olson wrote: Hi all, I would really like to get v0.9.9 out the door this week ... maybe committing to the final source code version on thursday or friday. I agree, it really is time to get it out. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] impending v0.9.9 release
Hello Curt, "Curtis L. Olson" wrote: > I really really want to get v0.9.9 done this week. It might be very helpful if add your weight to the idea to get a _functional_ PLIB release to base on. To my memory the current PLIB CVS is pretty good in shape, except one network patch that should be backed out (spotted by Melchior), Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Conflicting clouds
Hello, I see a strange effect that is related to 3D-clouds. I am starting FG from EGPH with 'simple' clouds by setting "--enable-clouds" on the commandline. Current METAR is: EGPH 151720Z 25006KT FEW030 05/01 Q1008 and FG translates this into a "few" cloud layer at 3135 ft having a thickness of 65 ft. That's o.k. for me as the clouds look nice :-) Now I enable 3D-clouds at runtime via the menu and all clouds disappear, even the "few" layer. Does anyone have an explanation for this ? These days I experienced a similar effect when _two_ cloud layers were present. After enabling 3D-clouns the upper of the two seemed to disappeare, the lower still was there. Unfortunately I can't tell if there actually were 3D-clouds. Regards, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] The right way to use the property manager?
Hi all,
I have been doing some coding and using the property manager in flightgear
but i want to know what is the right way to do it.
I use the method "fgGetNode("/path/to/property", true)" to get an existing
property or create one if not there. There are a few things i want to know
that i list below:
1) A node that is used in the flight system also results in the method
"isTied" failing and the It does allow me to tie this already existing
property to a variable?!? Is this the expected behavior? Isn't the property
supposed to be tied to a variable somewhere already?
2) When a property did not previously exist, is it necessary to create a
variable and tie the node to that variable? I find the system to be working
either ways. If i do not tie it, the property is displayed as "double" in
the property browser else it displays the data type that it has been tied
to.
3) When the property has been explicitly tied, no matter what the value is
initialized to using the "setDoubleValue" method the property browser shows
the value as zero. This display of zero does not happen when the property
is not tied explicitly.
4) I would also like to add a change listener to the class that i have
written so that the class is informed as and when a variable being watched
has changed value. I believe the way to do this is to use the
"SGPropertyChangeListener" class as a base class and implement the
"valueChanged" method to do the job. Is this correct?
So now, back to my question. What is the right way to use the property
manager? Which are the right methods that are to be used and in what
sequence?
--
Cheers!
Kitts
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] impending v0.9.9 release
Quoting "Curtis L. Olson" : > Hi all, > > I would really like to get v0.9.9 out the door this week ... maybe > committing to the final source code version on thursday or friday. > However, I would like to give everyone the opportunity to mention any > show stopping bugs that we should be concerned about. It's ok to report > bugs, but at this point we really need people reporting *fixes*. The > magic source code gods have this week off so we are going to have to fix > all the bugs ourselves. :-) It is not a bug but I am trying to put the "Objects/Terrain" stuff in fgadmin. -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] impending v0.9.9 release
Hi all, I would really like to get v0.9.9 out the door this week ... maybe committing to the final source code version on thursday or friday. However, I would like to give everyone the opportunity to mention any show stopping bugs that we should be concerned about. It's ok to report bugs, but at this point we really need people reporting *fixes*. The magic source code gods have this week off so we are going to have to fix all the bugs ourselves. :-) At this time I'm not referring to missing features, and I'm probably not interested in discussing long standing limitations. Right now we need to find any recently introduced, or big show stopping problems and fix them in the next day or two. I really really want to get v0.9.9 done this week. If we wait until next week we run into the Thanksgiving holiday here in the USA. And if we put things off another week after that, who knows what my schedule will be like. I really want to get this out this week! And barring something really awful, I plan to do the official v0.9.9 release thursday or friday. So that will be the cutoff and we will take whatever we have in cvs as of then. Thanks, Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Problems in the latest CVS version
AJ > On Tuesday 15 November 2005 13:18, Dai Qiang wrote: > > I am using the latest CVS version of SimGear, > > FlightGear data and source. After I enabled the Nimitz > > demo, I found the Hunter plane moved backward slowly > > when it's landed on the Nimitz, because Nimitz was > > moving forward, and Hunter remained at its original > > position. > > Just checking the obvious - you have engaged the parking brake, haven't > you? > (Shift - b) > > Likewise, on land, if the 747 is sitting on a sloping runway without the > brakes on, it will naturally roll downhill. > Hunter starts with the brakes on by default. It works here with cvs as of this morning. V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Problems in the latest CVS version
Hi AJ, Thanks for the quick reply. I actually did nothing but started with the following commmand: fgfs --fg-root=/home/azuron/Project/CVS/FG/data --aircraft=hunter --carrier=Nimitz The situation was like what I just decribed from the beginning. I have tried Shift + b and it was the same. It's especially weired that when I pressed P to pause the simulation, Hunter started to move forward according to the carrier. I am really confused. :-/ --- AJ MacLeod <[EMAIL PROTECTED]>写道: > On Tuesday 15 November 2005 13:18, Dai Qiang wrote: > > I am using the latest CVS version of SimGear, > > FlightGear data and source. After I enabled the > Nimitz > > demo, I found the Hunter plane moved backward > slowly > > when it's landed on the Nimitz, because Nimitz was > > moving forward, and Hunter remained at its > original > > position. > > Just checking the obvious - you have engaged the > parking brake, haven't you? > (Shift - b) > > Likewise, on land, if the 747 is sitting on a > sloping runway without the > brakes on, it will naturally roll downhill. > > Cheers, > > AJ > > ___ > Flightgear-devel mailing list > Flightgear-devel@flightgear.org > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > ___ 雅虎免费G邮箱－中国第一绝无垃圾邮件骚扰超大邮箱 http://cn.mail.yahoo.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Problems in the latest CVS version
On Tuesday 15 November 2005 13:18, Dai Qiang wrote: > I am using the latest CVS version of SimGear, > FlightGear data and source. After I enabled the Nimitz > demo, I found the Hunter plane moved backward slowly > when it's landed on the Nimitz, because Nimitz was > moving forward, and Hunter remained at its original > position. Just checking the obvious - you have engaged the parking brake, haven't you? (Shift - b) Likewise, on land, if the 747 is sitting on a sloping runway without the brakes on, it will naturally roll downhill. Cheers, AJ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Problems in the latest CVS version
Hi guys, I got some problems when compiling the latest CVS version of FG. I don't know if other people have similar problems. I am using the latest CVS version of SimGear, FlightGear data and source. After I enabled the Nimitz demo, I found the Hunter plane moved backward slowly when it's landed on the Nimitz, because Nimitz was moving forward, and Hunter remained at its original position. I didnot have that problem with Cessna and B1ooD in the default airport. But the situation was similar to Hunter on Nimitz when I started with a 747 in the default airport. Vivian told me it's an old bug that has been fixed long time ago, but I am actually using the latest version of everything. Any kinds of help would be appreciated, thanks in advance. - Qiang ___ 无限容量雅虎相册，原图等大下载，超快速度，赶快抢注！ http://cn.photos.yahoo.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Missing Data/ directory in pre3 base package
Curtis L. Olson wrote: Argh! Can we pick a different more intuitive name for this directory. It got created because the old 3d clouds demo needed it's stuff there, but we really need a more intuitive name beyond data/Data ... ! Yes, but not before 0.9.9 has been released. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Missing Data/ directory in pre3 base package
Pigeon wrote: Hi all, It seems the Data/ directory is missing in the pre3 package, which basically contains only Data/AI/ at the moment, and hence explains a few people not able to use the nimitz carrier (Data/AI/nimitz_demo.xml), and fgfs will simply terminate with a very vague message saying "terminate called after throwing an instance of 'sg_io_exception'" (reported by azuron on IRC). Argh! Can we pick a different more intuitive name for this directory. It got created because the old 3d clouds demo needed it's stuff there, but we really need a more intuitive name beyond data/Data ... ! Thanks, Curt -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: freeglut on SuSE 10
On Tuesday 15 November 2005 03:13, Steve Knoblock wrote: > I've got Flight Gear 0.9.8 running. I will try installing the CVS > version soon or the prerelease. Good stuff - as far as I can think, you ought to have a fairly straightforward time building either now that you have the glut problem sorted out. > I may show up on IRC in time. I don't frequent any other IRC channels, but #flightgear is generally quite a pleasant place, and great for getting quick answers to wee questions that you might not want to bother a mailing list with... Cheers, AJ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: [BUG] environemnt_ctrl.cxx: exception triggers SGThread assert()
Erik Hofman wrote: Next stop: IRIX. Same problem. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: [BUG] environemnt_ctrl.cxx: exception triggers SGThread assert()
Melchior FRANZ wrote: Error fetching live weather data: More than 10 stale METAR messages in a row. Stop fetching data permanently. fgfs: /usr/local/include/simgear/threads/SGThread.hxx:150: void \ SGThread::join(): Assertion `status == 0' failed. /home/m/bin/fgfs: line 239: 18187 Aborted (core dumped) Same for me on Linux. Next stop: IRIX. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
