[Flightgear-devel] Re: Re: tiled panel code
* Jim Wilson -- Wednesday 20 February 2002 00:52: Melchior FRANZ [EMAIL PROTECTED] said: No wonder, the patch was not against the latest CVS, so it removed everything that was added later! Very nasty ... :-( Sorry about that...actually I was quite current, but usually I like to cvs update one last time before posting. Never mind. Thanks for the great panel code! The panel look really great now! m. :-) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
re: [Flightgear-devel] Some YASim changes
Andy Ross writes: The bug with mis-reporting airspeed as groundspeed has been fixed. Problem is, the --wind argument doesn't seem to work anymore. :) Specifying something like --wind=270@20 definitely used to work, I remember testing against it. But now, the FDM gets zeros. I didn't investigate further. I'm going to look into this problem today. I've been building configured --with-new-environment, but I'll reconfigure without to make sure that the old code is still working. Thanks for the changes -- the new contact points are especially nice. Any suggestions about how to start or stop the piston engine based on the current RPM? All the best, David -- David Megginson [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] [OT]: Athlon MP and Flightgear
Hi guys! Could you please advice me what dual processor system should I buy Athlon MP or PentiumIII with Geforce3 or 4 what linux kernels support 760 chipset have anyone measured benchmarks with athlons and pentuimIII with nvidia drivers under linux? athlon is good but what about stability? Thanx Bye ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] [OT]: Athlon MP and Flightgear
athlon is good but what about stability? Unfortunately I never hat an Athlon SMP system in my hands to try out. Athlon UP is pretty nice and stable, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] [OT]: Athlon MP and Flightgear
On Wednesday 20 February 2002 06:09, you wrote: Hi guys! Could you please advice me what dual processor system should I buy Athlon MP or PentiumIII with Geforce3 or 4 what linux kernels support 760 chipset have anyone measured benchmarks with athlons and pentuimIII with nvidia drivers under linux? athlon is good but what about stability? Thanx Bye FWIW I am using a dual Athlon T-bird 900MHz system on the Tyan Tiger MP mainboard with no stability problems. There is a memory issue, one must append mem=nopentium to the kernel command line with linux and I believe there is a patch for Win2K. I don't have any benchmarks handy, but compilation is u FAST. :) I had never experience the tile loading pause even with a single cpu system so I can't say whether the multi-threading improves the issue. Everything seems to work great in regards to FlightGear. Good luck. Wm -- William L. Riley [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Turbine engines in FGFS?
If you filter on certain frequencies you can hear satanic messages. Even worse, if you play them backwards you hear Btitney Spears singing Oh, great. I meant B_r_itney. This was not a Freudian slip. :-) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Turbine engines in FGFS?
Gene Buckle wrote: On Wed, 06 Feb 2002 10:36:55 +0100 Erik Hofman [EMAIL PROTECTED] wrote: matthew law wrote: I can provide these as .wav, .au, or .mp3 files. MP3 would be better for me to distribute as I am only on a modem at home. Preferably not mp3. I'd rather have 22Khz than mp3 bacause it removes audio information which might be harmfull. What kind of harmful audio info is removed? MP3 filters for one playback rate only. All audio information thet can't be heard by the human ear is removed (that is, frequency bands are removed). It might be that the removed frequencies can be heard when doing pitch shifting. So you basically get a malformed audio sound then (not clear so to say). Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] [OT]: Athlon MP and Flightgear
On Wed, 20 Feb 2002, Roman Grigoriev wrote: Hi guys! Could you please advice me what dual processor system should I buy Athlon MP or PentiumIII with Geforce3 or 4 what linux kernels support 760 chipset have anyone measured benchmarks with athlons and pentuimIII with nvidia drivers under linux? Running flightgear on an ABit VP6 based system with 2 PIII 866 processors and a Creative 32MB GeForce2 MX produces *very* good frame rates, even at high resolutions. I'll get you some exact numbers later when I can test it. -- Jon StockillPublic Key: C6BD585D [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Turbine engines in FGFS?
Preferably not mp3. I'd rather have 22Khz than mp3 bacause it removes audio information which might be harmfull. What kind of harmful audio info is removed? MP3 filters for one playback rate only. All audio information thet can't be heard by the human ear is removed (that is, frequency bands are removed). It might be that the removed frequencies can be heard when doing pitch shifting. So you basically get a malformed audio sound then (not clear so to say). Ahh, ok. That makes sense. You're after a purer sound than is possible with MP3 encoding then? g. -- I'm not crazy, I'm plausibly off-nominal! http://www.f15sim.com - The only one of its kind. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Turbine engines in FGFS?
Gene Buckle wrote: Preferably not mp3. I'd rather have 22Khz than mp3 bacause it removes audio information which might be harmfull. What kind of harmful audio info is removed? MP3 filters for one playback rate only. All audio information thet can't be heard by the human ear is removed (that is, frequency bands are removed). It might be that the removed frequencies can be heard when doing pitch shifting. So you basically get a malformed audio sound then (not clear so to say). Ahh, ok. That makes sense. You're after a purer sound than is possible with MP3 encoding then? Yes. MP3 hasn't been designed to change the pitch, after all. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Turbine engines in FGFS?
MP3 filters for one playback rate only. All audio information thet can't be heard by the human ear is removed (that is, frequency bands are removed). It might be that the removed frequencies can be heard when doing pitch shifting. So you basically get a malformed audio sound then (not clear so to say). Ahh, ok. That makes sense. You're after a purer sound than is possible with MP3 encoding then? Yes. MP3 hasn't been designed to change the pitch, after all. Erik Thanks Erik! g. -- I'm not crazy, I'm plausibly off-nominal! http://www.f15sim.com - The only one of its kind. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Problem with panel code
David Megginson wrote: Jim Wilson writes: And the question that brings to mind is, how will we be able to set the z axis in a way that it can handle the panel? In other words, the scale is so large now that it'll disappear just like airplane model components do when viewed too closely. Can we have two different scales in the same tree/graph? Actually, I'm not sure -- any advice from the PLIB gurus? I have no Plib insight to offer, but the core problem isn't very difficult at all. Panel geometry is static, and can really easily (by hand in the XML, even) be sorted back to front. Just turn off z-test, set up the projection appropriately, and draw. I'm sure this must be doable in Plib somehow. So long as the graph can guarantee an order of drawing, we can write a state node to set up the matrices. Andy -- Andrew J. RossNextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com Men go crazy in conflagrations. They only get better one by one. - Sting (misquoted) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Problem with panel code
Sure. Scaling is not a problem with plib. The classes ssgTransform and ssgTexTrans are put in the scene graph to control object and texture transformations of their kids. One of the setTransform operations allows scaling. Regards. Mark K Vallevand Fat, dumb and happy. 2 out of 3 ain't bad. -Original Message- From: David Megginson [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 20, 2002 2:11 PM To: [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] Problem with panel code Jim Wilson writes: And the question that brings to mind is, how will we be able to set the z axis in a way that it can handle the panel? In other words, the scale is so large now that it'll disappear just like airplane model components do when viewed too closely. Can we have two different scales in the same tree/graph? Actually, I'm not sure -- any advice from the PLIB gurus? All the best, David -- David Megginson [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] mk4?
I'm using the cvs version flightgear. When I tried to make it says cannot find -lmk4 there aren't any mk4 lib files in /us/local/lib, but I have already installed mk4 using the cygwin install program. I haven't the foggiest clue where to get mk4. I have tried recvsing flightgear to no avail. Please help. Thanks. Keith Wiley[EMAIL PROTECTED] http://www.unm.edu/~keithw http://www.mp3.com/KeithWiley Yet mark his perfect self-contentment, and hence learn his lesson, that to be self-contented is to be vile and ignorant, and that to aspire is better than to be blindly and impotently happy. -- Edwin A. Abbott, Flatland ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Problem with panel code
David Megginson writes: Jim Wilson writes: And the question that brings to mind is, how will we be able to set the z axis in a way that it can handle the panel? In other words, the scale is so large now that it'll disappear just like airplane model components do when viewed too closely. Can we have two different scales in the same tree/graph? Actually, I'm not sure -- any advice from the PLIB gurus? I'm not sure about your definition of the z axis ... in this case your question makes sense if we define the z axis to be along the center of projection. This really is more of an opengl issue than a plib issue. Opengl defines the view volume to be a frustum (just like a pyramid with a bit of the top lopped off.) You can refer to the picture here for an example: http://www.cs.ucf.edu/~moshell/CAP5725/CAP5725.week4.html So if a portion of the scene is closer to us than the near clip plane, it will be clipped out. That is what happens when you get the external view point too close to the aircraft. Similar wierdness if you set the far clip plane too far away and then get too close to the ground. The good news is that you can reset the clip planes at any time during the rendering process meaning you can render a portion of the scene, then move one or both clip planes, and redraw another portion of the scene, continuing this as much as needed. The bad news is that certain driver optimizations can get screwed up if you move the clip planes (ie. the fog tables in some versions of mesa). Or the driver may be forced to recompute things like fog tables and other values when you change the position of the clip planes. Thus, there can be visual artifact and or performance implications with moving the clip planes. Also, be aware that the precision of the depth buffer is *very* sensitive to the position of the near clip plane: http://www.sjbaker.org/steve/omniv/love_your_z_buffer.html The conclusion is that for best depth buffer precision we want to push out the near clip plane as far as possible. The position of the far clip plane is mostly irrelevant, although it has to be beyond the furthest object we want to see. :-) So the point of all this is that we can draw the world, then move the near clip plane in, and then draw the panel. This would work best if we put the panel into a different scene graph from everything else: setclipplanesforworld(); ssgCullAndDraw(world); setclipplanesforpanel(); ssgCullAndDraw(panel); Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Problem with panel code
Vallevand, Mark K writes: Sure. Scaling is not a problem with plib. The classes ssgTransform and ssgTexTrans are put in the scene graph to control object and texture transformations of their kids. One of the setTransform operations allows scaling. Be careful with scaling objects though because this can screw up things like normal vectors (which would then screw up lighting.) Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: Re: Wind confusion.
Martin van Beilen writes: On Tue, Feb 19, 2002 at 10:50:40PM +0100, Melchior FRANZ wrote: there is no 'ann' in the manual. I'm using V1.11. But ann isn't a new feature. slaps forehead DUH! /slaps CVS comes with a fake manual page. :-( On most linux systems 'info -f cvs' is very helpful. Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Compilation problem in ATC (0.7.9)
Hmmm, it sounds exactly like you are picking up an older version of simgear some place. I'd check through your hard drive to make sure something older isn't installed (or make sure you did 'make install' after running 'make' for 0.0.17 ...) :-) Regards, Curt. Alasdair Campbell writes: My first attempt at building 0.7.9 led to this: Making all in ATC make[2]: Entering directory `/usr/src/FlightGear-0.7.9/src/ATC' c++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/usr/local/include -I/usr/X11R6/include -g -O2 -c atis.cxx In file included from atis.cxx:49: ../../src/Main/fg_props.hxx: In function `class SGPropertyNode * fgGetNode(const string , int, bool = false)': ../../src/Main/fg_props.hxx:100: no matching function for call to `SGPropertyNode::getNode (const basic_stringchar,string_char_traitschar,__default_alloc_templatetrue,0 , int , bool )' /usr/local/include/simgear/misc/props.hxx:681: candidates are: class SGPropertyNode * SGPropertyNode::getNode(const string , bool = false) /usr/local/include/simgear/misc/props.hxx:687: const class SGPropertyNode * SGPropertyNode::getNode(const string ) const In file included from atis.cxx:52: atis.hxx: In function `class istream operator (istream , FGATIS )': /usr/local/include/simgear/timing/sg_time.hxx:241: too many arguments to function `double sgTimeCurrentMJD(long int)' atis.hxx:116: at this point in file make[2]: *** [atis.o] Error 1 make[2]: Leaving directory `/usr/src/FlightGear-0.7.9/src/ATC' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/FlightGear-0.7.9/src' make: *** [all-recursive] Error 1 Using Linux 2.4.17 I have plib-1.4.2 and simgear 0.0.17 installed. The source tarball was downloaded from the German mirror. Any help, anyone? -- Kind Regards, Alasdair Campbell ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Compilation problem in ATC (0.7.9)
My first attempt at building 0.7.9 led to this: Making all in ATC make[2]: Entering directory `/usr/src/FlightGear-0.7.9/src/ATC' c++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/usr/local/include -I/usr/X11R6/include -g -O2 -c atis.cxx In file included from atis.cxx:49: ../../src/Main/fg_props.hxx: In function `class SGPropertyNode * fgGetNode(const string , int, bool = false)': ../../src/Main/fg_props.hxx:100: no matching function for call to `SGPropertyNode::getNode (const basic_stringchar,string_char_traitschar,__default_alloc_templatetrue,0 , int , bool )' /usr/local/include/simgear/misc/props.hxx:681: candidates are: class SGPropertyNode * SGPropertyNode::getNode(const string , bool = false) /usr/local/include/simgear/misc/props.hxx:687: const class SGPropertyNode * SGPropertyNode::getNode(const string ) const In file included from atis.cxx:52: atis.hxx: In function `class istream operator (istream , FGATIS )': /usr/local/include/simgear/timing/sg_time.hxx:241: too many arguments to function `double sgTimeCurrentMJD(long int)' atis.hxx:116: at this point in file make[2]: *** [atis.o] Error 1 make[2]: Leaving directory `/usr/src/FlightGear-0.7.9/src/ATC' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/FlightGear-0.7.9/src' make: *** [all-recursive] Error 1 Using Linux 2.4.17 I have plib-1.4.2 and simgear 0.0.17 installed. The source tarball was downloaded from the German mirror. Any help, anyone? -- Kind Regards, Alasdair Campbell ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Compilation problem in ATC (0.7.9)
On Wednesday 20 February 2002 10:14 pm, you wrote: Hmmm, it sounds exactly like you are picking up an older version of simgear some place. I'd check through your hard drive to make sure something older isn't installed (or make sure you did 'make install' after running 'make' for 0.0.17 ...) :-) Regards, Curt. It ain't that. The Simgear and Plib includes have todays dates, and anyway I reinstalled to make double sure. I haven't any more copies on the HD. Alasdair Campbell writes: My first attempt at building 0.7.9 led to this: Making all in ATC make[2]: Entering directory `/usr/src/FlightGear-0.7.9/src/ATC' c++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/usr/local/include -I/usr/X11R6/include -g -O2 -c atis.cxx In file included from atis.cxx:49: ../../src/Main/fg_props.hxx: In function `class SGPropertyNode * fgGetNode(const string , int, bool = false)': ../../src/Main/fg_props.hxx:100: no matching function for call to `SGPropertyNode::getNode (const basic_stringchar,string_char_traitschar,__default_alloc_templatetrue, 0 , int , bool )' /usr/local/include/simgear/misc/props.hxx:681: candidates are: class SGPropertyNode * SGPropertyNode::getNode(const string , bool = false) /usr/local/include/simgear/misc/props.hxx:687: const class SGPropertyNode * SGPropertyNode::getNode(const string ) const In file included from atis.cxx:52: atis.hxx: In function `class istream operator (istream , FGATIS )': /usr/local/include/simgear/timing/sg_time.hxx:241: too many arguments to function `double sgTimeCurrentMJD(long int)' atis.hxx:116: at this point in file make[2]: *** [atis.o] Error 1 make[2]: Leaving directory `/usr/src/FlightGear-0.7.9/src/ATC' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/FlightGear-0.7.9/src' make: *** [all-recursive] Error 1 Using Linux 2.4.17 I have plib-1.4.2 and simgear 0.0.17 installed. The source tarball was downloaded from the German mirror. Any help, anyone? -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Problem with panel code
Yes, you are correct. In fact, this explains an artifact I'm seeing in one of my programs. The normals must be getting screwed up because of scaling because lighting is funny on a pair of identical objects that have been scaled and rotated. I'll have to chase that idea down. Regards. Mark K Vallevand Fat, dumb and happy. 2 out of 3 ain't bad. -Original Message- From: Curtis L. Olson [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 20, 2002 3:15 PM To: [EMAIL PROTECTED] Subject: RE: [Flightgear-devel] Problem with panel code Vallevand, Mark K writes: Sure. Scaling is not a problem with plib. The classes ssgTransform and ssgTexTrans are put in the scene graph to control object and texture transformations of their kids. One of the setTransform operations allows scaling. Be careful with scaling objects though because this can screw up things like normal vectors (which would then screw up lighting.) Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Problem with panel code
Curtis L. Olson [EMAIL PROTECTED] said: This would work best if we put the panel into a different scene graph from everything else: setclipplanesforworld(); ssgCullAndDraw(world); setclipplanesforpanel(); ssgCullAndDraw(panel); Does this make sense? Setting up a seperate scene graph? Perhaps it should be called cockpit so that a 3d cockpit can be added. Now I just have to figure out where to start :-) Time to look at those ssg examples. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Compilation problem in ATC (0.7.9)
* [EMAIL PROTECTED] (Alasdair Campbell) [2002.02.20 16:00]: My first attempt at building 0.7.9 led to this: Making all in ATC make[2]: Entering directory `/usr/src/FlightGear-0.7.9/src/ATC' c++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/usr/local/include -I/usr/X11R6/include -g -O2 -c atis.cxx In file included from atis.cxx:49: ../../src/Main/fg_props.hxx: In function `class SGPropertyNode * fgGetNode(const string , int, bool = false)': ../../src/Main/fg_props.hxx:100: no matching function for call to `SGPropertyNode::getNode (const basic_stringchar,string_char_traitschar,__default_alloc_templatetrue,0 , int , bool )' /usr/local/include/simgear/misc/props.hxx:681: candidates are: class SGPropertyNode * SGPropertyNode::getNode(const string , bool = false) /usr/local/include/simgear/misc/props.hxx:687: const class SGPropertyNode * SGPropertyNode::getNode(const string ) const This has to be a problem of multiple versions of simgear. The function being called was added about 4 weeks ago. I've know you've already checked, but check again. I'm almost 100% sure you have two copies of simgear. -- Cameron Moore / I planted some bird seed. A bird came up. \ \ Now I don't know what to feed it. / ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Compilation problem in ATC (0.7.9)
On Wednesday 20 February 2002 11:29 pm, you wrote: * [EMAIL PROTECTED] (Alasdair Campbell) [2002.02.20 16:00]: My first attempt at building 0.7.9 led to this: Making all in ATC make[2]: Entering directory `/usr/src/FlightGear-0.7.9/src/ATC' c++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/usr/local/include -I/usr/X11R6/include -g -O2 -c atis.cxx In file included from atis.cxx:49: ../../src/Main/fg_props.hxx: In function `class SGPropertyNode * fgGetNode(const string , int, bool = false)': ../../src/Main/fg_props.hxx:100: no matching function for call to `SGPropertyNode::getNode (const basic_stringchar,string_char_traitschar,__default_alloc_templatetrue, 0 , int , bool )' /usr/local/include/simgear/misc/props.hxx:681: candidates are: class SGPropertyNode * SGPropertyNode::getNode(const string , bool = false) /usr/local/include/simgear/misc/props.hxx:687: const class SGPropertyNode * SGPropertyNode::getNode(const string ) const This has to be a problem of multiple versions of simgear. The function being called was added about 4 weeks ago. I've know you've already checked, but check again. I'm almost 100% sure you have two copies of simgear. I had only one copy of Simgear installed, but what has occurred is that somewhere along the line two VERSIONS of Simgear appear to have been released with the same version number. The length of the 0.0.17.tgz I already had was 1,150,303 bytes long and compiled and installed perfectly. The length of the one I have just downloaded is 1,384,955. 0.0.16.tgz was 1,146,201 bytes. Now, how could that have come about, I wonder??? Anyway, fgfs compiled fine with the new Simgear. I can't wait to try it. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Sorted property picker list
[This didn't seem to come through the first time. Apologies if you
see it twice.]
Here's a fun toy. I've been using the property picker a lot recently,
while working on a panel for the Harrier. Sometimes it gets difficult
to find the property you're looking for in a crowded tree. The
attached patch sorts the list alphabetically.
Andy
Index: prop_picker.cxx
===
RCS file: /var/cvs/FlightGear-0.7/FlightGear/src/GUI/prop_picker.cxx,v
retrieving revision 1.6
diff -u -w -r1.6 prop_picker.cxx
--- prop_picker.cxx 8 Feb 2002 12:31:22 - 1.6
+++ prop_picker.cxx 21 Feb 2002 01:16:30 -
@@ -501,6 +501,23 @@
files [ num_files ] = NULL ;
+// Sort the entries. This is a simple N^2 extraction sort. More
+// elaborate algorithms aren't necessary for the few dozen
+// properties we're going to sort.
+for(i=0; inum_files; i++) {
+int j, min = i;
+char df, *tmp;
+for(j=i+1; jnum_files; j++)
+if(strcmp(names[j], names[min]) 0)
+min = j;
+if(i != min) {
+tmp = names[min]; names[min] = names[i]; names[i] = tmp;
+tmp = files[min]; files[min] = files[i]; files[i] = tmp;
+tmp = values[min]; values[min] = values[i]; values[i] = tmp;
+df = dflag[min]; dflag[min] = dflag[i]; dflag[i] = df;
+}
+}
+
// printf(files pointer=%i/%i\n, files, num_files);
proppath -setLabel (startDir);
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] twin panel
Why is the twin panel starting out mostly off screen? Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
