Re: [Flightgear-devel] Base Package size (was 3D clouds)
Jim Wilson [EMAIL PROTECTED] wrote : My guess is something is messed up in the large.sky file, or how it is picking up the cloud files (the index is probably 0 so the cloud loading loop in the loader isn't being run). When I get a chance I'll try a gdb session, but looking at the large.sky file in cvs I don't see anything that looks like a value for Numfiles (number of cloudfiles under the CloudFiles tag). This might not mean anything as I'm not sure that there even is such a value in large.sky's structure, but like I said the program is acting like it is getting 0 for number of cloud files. Have you set the current directory to $FG_ROOT ? The cloud loader don't prepend the cloud file name with the fg-root path. Cheers, -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Base Package size (was 3D clouds)
Frederic BOUVIER [EMAIL PROTECTED] said: Have you set the current directory to $FG_ROOT ? The cloud loader don't prepend the cloud file name with the fg-root path. That was the problem. BTW the failure to find a cld file isn't being returned by the function. Now that it is working, the current code/method is a bit too heavy on my 32mb geforce2. Dropping down to 640x480 improves the frame rate to a useable level...but...well...that's an area for improvement :-) Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Clouds progress : screenshot
Guys! Maybe I missed something but I can't got nicy views with clouds3d just got similar to http://rockfish.net/~nhv/fgfs/images/fgfs-screen-009.jpg I compiled from today CVS with gcc3.2 and have nvidia-31.23 drivers on geforce3 running in 1024x768 32bpp so there is a some problem with alpha how to get nice view of 3d clouds on linux maybe on windows all is OK and problem is related to linux? Thanx in advance Bye ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Clouds progress : screenshot
Roman, From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Roman maybe on windows all is OK and problem is related to linux? Don't worry, on windows (cygwin), SimGear does not even compile - yet, despite all the patches ;-) - I think Norman is working on that, though. Regards, Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Clouds progress : screenshot
Roman Grigoriev writes: Maybe I missed something but I can't got nicy views with clouds3d just got similar to http://rockfish.net/~nhv/fgfs/images/fgfs-screen-009.jpg I compiled from today CVS with gcc3.2 and have nvidia-31.23 drivers on geforce3 running in 1024x768 32bpp That's what I get as well, with a GeForce2Go 32MB. When I get a little closer, it turns into a white cube. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
re: [Flightgear-devel] Re: [Flightgear-cvslogs] Base CVSupdate:'FlightGear/FlightGear/Aircraft/c172'
Tony Peden writes: It looks like this may have helped crosswind handling on the ground considerably. The relatively small amount of testing I've done shows that the c172 will sit still in up to a 15 knot crosswind and turn very slowly in 20 knots. Let us know what you think. I'll test it more today, but it must have been a fairly recent change that put the nosewheel into the NONE group. I have some photocopies from a C172R POH, so I can also correct some of the arms, but I didn't want to do that without discussing it with you (Tony) first. Using the firewall in front of the pilot as the reference datum (as both the POH and c172.xml do), here are the arms, or x-positions, of various masses: * Usable fuel: 38in (c172.xml has 56in) * Pilot and front passenger: 34-46in, typically 37in (c172.xml has 36in, which is OK) * Rear passengers: 73in (not in c172.xml) * Baggage area 1: typically 95in (not in c172.xml) * Baggage area 2: typically 123in (not in c172.xml) The empty weight and arm (i.e. CG) obviously vary depending on configuration. Here are the default values for a C172R: * Empty weight (including oil and unusuable fuel): 1639lb (c172.xml has 1500lb) * Empty arm (CG): 39.3in (c172.xml has 41in) Here are the current values for our club's C172R, which has a 180HP upgrade: * Empty weight (including oil and unusable fuel): 1681.5lb * Empty arm (CG): 39.1in All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
re: [Flightgear-devel] Re: [Flightgear-cvslogs] Base CVSupdate:'FlightGear/FlightGear/Aircraft/c172'
On Wed, 2002-09-18 at 05:52, David Megginson wrote: Tony Peden writes: It looks like this may have helped crosswind handling on the ground considerably. The relatively small amount of testing I've done shows that the c172 will sit still in up to a 15 knot crosswind and turn very slowly in 20 knots. Let us know what you think. I'll test it more today, but it must have been a fairly recent change that put the nosewheel into the NONE group. I didn't look at everything, but the nose wheel was in NONE and the mains CASTERED as far back as I looked (which went back to the beginning of time for the configurable gear). I can't explain the CASTERED mains, but I understood what you call steer groups to be brake groups. It never occurred to me that that would affect the steering control. (and maybe it didn't, changing the mains from CASTERED to fixed could have a significant effect). I need to experiment with it some more. I have some photocopies from a C172R POH, so I can also correct some of the arms, but I didn't want to do that without discussing it with you (Tony) first. Using the firewall in front of the pilot as the reference datum (as both the POH and c172.xml do), here are the arms, or x-positions, of various masses: * Usable fuel: 38in (c172.xml has 56in) Hmm, I got my numbers from a POH as well. I'll have to double check. * Pilot and front passenger: 34-46in, typically 37in (c172.xml has 36in, which is OK) * Rear passengers: 73in (not in c172.xml) * Baggage area 1: typically 95in (not in c172.xml) * Baggage area 2: typically 123in (not in c172.xml) The empty weight and arm (i.e. CG) obviously vary depending on configuration. Here are the default values for a C172R: * Empty weight (including oil and unusuable fuel): 1639lb (c172.xml has 1500lb) * Empty arm (CG): 39.3in (c172.xml has 41in) Here are the current values for our club's C172R, which has a 180HP upgrade: * Empty weight (including oil and unusable fuel): 1681.5lb * Empty arm (CG): 39.1in All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- Tony Peden [EMAIL PROTECTED] We all know Linux is great ... it does infinite loops in 5 seconds. -- attributed to Linus Torvalds ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
re: [Flightgear-devel] Re: [Flightgear-cvslogs] Base CVSupdate:'FlightGear/FlightGear/Aircraft/c172'
Tony Peden writes:
I didn't look at everything, but the nose wheel was in NONE and the
mains CASTERED as far back as I looked (which went back to the beginning
of time for the configurable gear). I can't explain the CASTERED mains,
but I understood what you call steer groups to be brake groups. It
never occurred to me that that would affect the steering control.
Here's an excerpt from FGLGear.cpp:
case bgNose:
SteerGain = -0.50;
BrakeFCoeff = rollingFCoeff;
break;
case bgTail:
SteerGain = -0.10;
BrakeFCoeff = rollingFCoeff;
break;
case bgNone:
SteerGain = 0.0;
BrakeFCoeff = rollingFCoeff;
break;
and, a little further down:
switch (eSteerType) {
case stSteer:
SteerAngle = SteerGain*FCS-GetDrPos();
break;
In other words, if gear belongs to bgNone, it gets SteerGain=0.0, so
SteerAngle is always 0. Perhaps it's a recent C++ change that caused
this problem.
Note a second problem with this code: it uses getDrPos (the actual
rudder position) and ignores maxSteerAngle from the config file. A
better option would probably be
SteerAngle = SteerGain*FCS-GetDrCmd()*maxSteerAngle*RADTODEG;
It would also be nice to be able to specify SteerGain in the XML
config file rather than hard-coding it in FGLGear.cpp.
(and maybe it didn't, changing the mains from CASTERED to fixed could
have a significant effect). I need to experiment with it some more.
The castoring doesn't make a difference (yet), because FGLGear.cpp
still treats castoring gear as fixed anyway:
case stFixed:
SteerAngle = 0.0;
break;
case stCaster:
// Note to Jon: This is not correct for castering gear. I'll fix it later.
SteerAngle = 0.0;
break;
* Usable fuel:
38in (c172.xml has 56in)
Hmm, I got my numbers from a POH as well. I'll have to double check.
That's from the C172R POH. The C172P POH puts usable fuel at 48in,
probably because of the different wing shape, but it's still not as
far as c172.xml.
All the best,
David
--
David Megginson, [EMAIL PROTECTED], http://www.megginson.com/
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Clouds progress : screenshot
Michael Basler writes: maybe on windows all is OK and problem is related to linux? Don't worry, on windows (cygwin), SimGear does not even compile - yet, despite all the patches ;-) - I think Norman is working on that, though. Things were going rather well for me on Windows then I decided to try merging the latest stuff from CVS and I suddenly had problems I didn't see before. Spent way to much time trying to decipher what is happening and need to get some real work done so I tarred up my files with tar -czvf clouds.tgz \ FlightGear/src/Main/main.cxx \ FlightGear/src/Main/fg_init.cxx \ SimGear/configure.ac \ SimGear/simgear/sky/clouds3d/*.cpp \ SimGear/simgear/sky/clouds3d/*.h* \ SimGear/simgear/sky/clouds3d/*.c and put the tarball at http://rockfish.net/~nhv/fgfs/clouds.tgz so others could play too. This should build on Windows and Unix, I didn't add the necessary Mac changes but I think Jonathan has that covered Back up your original files !! Enjoy Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Clouds progress : screenshot
Could you please describe this situation Why this happened? Roman - Original Message - From: David Megginson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, September 18, 2002 4:29 PM Subject: Re: [Flightgear-devel] Clouds progress : screenshot Roman Grigoriev writes: Maybe I missed something but I can't got nicy views with clouds3d just got similar to http://rockfish.net/~nhv/fgfs/images/fgfs-screen-009.jpg I compiled from today CVS with gcc3.2 and have nvidia-31.23 drivers on geforce3 running in 1024x768 32bpp That's what I get as well, with a GeForce2Go 32MB. When I get a little closer, it turns into a white cube. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ 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] Re: [Flightgear-cvslogs] Base CVSupdate:'FlightGear/FlightGear/Aircraft/c172'
David Megginson writes: Note a second problem with this code: it uses getDrPos (the actual rudder position) and ignores maxSteerAngle from the config file. A better option would probably be SteerAngle = SteerGain*FCS-GetDrCmd()*maxSteerAngle*RADTODEG; For RADTODEG, read DEGTORAD. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Clouds progress : screenshot
Roman Grigoriev writes: Could you please describe this situation Why this happened? I don't know the code well enough to suggest why. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Clouds progress : screenshot
Jim, Norman, I'm getting the following compile error: fg_init.cxx: In function `void fgInitView()': fg_init.cxx:667: no matching function for call to `FGViewer::get_LOCAL ()' Regards, Curt. Norman Vine writes: Michael Basler writes: maybe on windows all is OK and problem is related to linux? Don't worry, on windows (cygwin), SimGear does not even compile - yet, despite all the patches ;-) - I think Norman is working on that, though. Things were going rather well for me on Windows then I decided to try merging the latest stuff from CVS and I suddenly had problems I didn't see before. Spent way to much time trying to decipher what is happening and need to get some real work done so I tarred up my files with tar -czvf clouds.tgz \ FlightGear/src/Main/main.cxx \ FlightGear/src/Main/fg_init.cxx \ SimGear/configure.ac \ SimGear/simgear/sky/clouds3d/*.cpp \ SimGear/simgear/sky/clouds3d/*.h* \ SimGear/simgear/sky/clouds3d/*.c and put the tarball at http://rockfish.net/~nhv/fgfs/clouds.tgz so others could play too. This should build on Windows and Unix, I didn't add the necessary Mac changes but I think Jonathan has that covered Back up your original files !! Enjoy Norman ___ 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
Re: [Flightgear-devel] Re: [Flightgear-cvslogs] Base CVSupdate:'FlightGear/FlightGear/Aircraft/c172'
On Wed, 18 Sep 2002 09:29:40 -0400 David Megginson [EMAIL PROTECTED] wrote: Here's an excerpt from FGLGear.cpp: case bgNose: SteerGain = -0.50; BrakeFCoeff = rollingFCoeff; break; In other words, if gear belongs to bgNone, it gets SteerGain=0.0, so SteerAngle is always 0. Perhaps it's a recent C++ change that caused this problem. I may be guilty, here. Note that this file needs to be gone through again with a fine tooth comb and validated. Just when I think I can't become more overwhelmed than I already am ... :-) Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: [Flightgear-cvslogs] Base CVSupdate:'FlightGear/FlightGear/Aircraft/c172'
On Wed, 18 Sep 2002 10:15:54 -0400 David Megginson [EMAIL PROTECTED] wrote: For RADTODEG, read DEGTORAD. Use degtorad and radtodeg These are consts from the FGJSBBase class. This is where commonly used constants are being migrated to, instead of #defines, which we are moving away from. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: [Flightgear-cvslogs] Base CVSupdate:'FlightGear/FlightGear/Aircraft/c172'
Jon S Berndt writes: I may be guilty, here. Note that this file needs to be gone through again with a fine tooth comb and validated. Just when I think I can't become more overwhelmed than I already am ... Wife pregnant with triplets again? (Don't laugh, my wife has a friend who had two sets of twins less than two years apart ... 4 kids less than 2 and in diapers. Yikes! Talk about bad luck.) :-) 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] Clouds progress : screenshot
Curtis L. Olson writes:
Jim, Norman,
I'm getting the following compile error:
fg_init.cxx: In function `void fgInitView()':
fg_init.cxx:667: no matching function for call to `FGViewer::get_LOCAL ()'
oops ... forgot one :-)
I was doing a little sanity checking
// $FG_SRC / Main / viewer.hxx
virtual const sgVec4 *get_LOCAL() { if ( _dirty ) { recalc(); } return
LOCAL; }
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Clouds progress : screenshot
Norman, From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Norman Vine and put the tarball at http://rockfish.net/~nhv/fgfs/clouds.tgz Thanks. Great work. First the good news: SimGear does build now on my Cygwin system (with a host of warnings in clouds3d, but still). The not so good ones are, FlightGear compiles too, but final linking does not yet work. This is the result: Making all in Main make[2]: Entering directory `/usr/local/source/flightgear/src/Main' source='main.cxx' object='main.o' libtool=no \ depfile='.deps/main.Po' tmpdepfile='.deps/main.TPo' \ depmode=gcc /bin/sh ../../depcomp \ g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/usr/ loca l/include -DPKGLIBDIR=\/usr/local/FlightGear/lib/FlightGear\ -g -O2 -c -o main .o `test -f main.cxx || echo './'`main.cxx source='fg_commands.cxx' object='fg_commands.o' libtool=no \ depfile='.deps/fg_commands.Po' tmpdepfile='.deps/fg_commands.TPo' \ depmode=gcc /bin/sh ../../depcomp \ g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/usr/ loca l/include -DPKGLIBDIR=\/usr/local/FlightGear/lib/FlightGear\ -g -O2 -c -o fg_c ommands.o `test -f fg_commands.cxx || echo './'`fg_commands.cxx source='fg_init.cxx' object='fg_init.o' libtool=no \ depfile='.deps/fg_init.Po' tmpdepfile='.deps/fg_init.TPo' \ depmode=gcc /bin/sh ../../depcomp \ g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/usr/ loca l/include -DPKGLIBDIR=\/usr/local/FlightGear/lib/FlightGear\ -g -O2 -c -o fg_i nit.o `test -f fg_init.cxx || echo './'`fg_init.cxx fg_init.cxx: In function `void fgInitView()': fg_init.cxx:666: no matching function for call to `FGViewer::get_LOCAL ()' make[2]: *** [fg_init.o] Error 1 make[2]: Leaving directory `/usr/local/source/flightgear/src/Main' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/source/flightgear/src' make: *** [all-recursive] Error 1 regards, Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Slackware packages
I've put flightgear packages for slackware 8.1 on my site at: http://flightgear.stockill.org.uk/ While these have been tested on 2 of my machines, 1 was the machine that I try all the builds on, so there could be all sorts on there that it's relying on to work. If there are any other slackware users out there that would like to try it then with a bit more feedback I'll announce it on the users list, and it can be linked from the downloads page. Packages for the 9.0 beta will be available on there once I've tested it with the latest updates. -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Removed simgear/interpreter/
I've removed the simgear/interpreter/ directory for three reasons: 1. It was wasting a lot of space. 2. Nobody (including me) was doing anything with it. 3. Plib now has its own C-like interpreted language in CVS. I've updated configure.ac, but have not changed SimGear.dsp (an MSVC thing?). If someone who uses this file can send me a patched version, I'll commit it ASAP. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Removed simgear/interpreter/
David Megginson writes: I've updated configure.ac, but have not changed SimGear.dsp (an MSVC thing?). If someone who uses this file can send me a patched version, I'll commit it ASAP. The MSVC work spaces are generated automatically whenever I run make dist. I have taken care of this. 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] forwarded message from Christina Guilbert
The winter LinuxWorld Conference Expo is in NY, January 21 - 24, 2003. If we want to have a booth, now is the time to think about requesting it. I sincerely doubt that I would be able to attend, so if we do have a booth, we'd need a volunteer to interface with the conference managers and do all the organization. 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 ---BeginMessage--- Hi Curt, It is that time again...see below for details for LinuxWorld Conference Expo NY '03. Best Regards, Christina Guilbert - What: LinuxWorld Conference Expo When: January 21 - 24, 2003 Where: Jacob K. Javits Center 655 West 34th Street New York, NY http://www.linuxworldexpo.com/linuxworldny03/V33/index.cvn ---End Message---
Re: [Flightgear-devel] Removed simgear/interpreter/
Curtis L. Olson writes: The MSVC work spaces are generated automatically whenever I run make dist. I have taken care of this. Thanks for handling that. If the files are autogenerated, we might want to yank them out of CVS. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Removed simgear/interpreter/
David Megginson Curtis L. Olson writes: The MSVC work spaces are generated automatically whenever I run make dist. I have taken care of this. Thanks for handling that. If the files are autogenerated, we might want to yank them out of CVS. Most MSVC users probably don't have Perl installed so in this case I think we should make an exception Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] 3d cloud rendering problems
Norman, Here's something for you to play with. Based on my own experiments, I believe that the cloud rendering problem centers around not having the correct state setup when we draw the cloud imposters. So, I don't believe it's an issue of protecting state around a particular section of code, I believe it's an issue of getting the state setup correctly before calling the imposter rendering Update() code. I'm wondering if it is related to the correct glColorMaterial() glEnable(GL_COLOR_MATERIAL) glColor() calls, because I'm seeing clouds with different colors, including but not limited to black. The imposter generation code could be inheriting whatever color was left over from the last thing we drew. 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] Clouds progress : screenshot - SOLVED!
Norman, From: Norman Vine [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 18, 2002 11:59 PM OK attached find a new makefile.am for the clouds3d directory that should pick up exgl.c on Windows and hopefully will still work on other systems This finally did the job. Now SimGear + FlightGear compiles under Cygwin. The display ist not yet what I expect, but this is another story already. Norman, you have done a marvellous job on this. I wouldn't count the hours this took to resolve. Can we get all this into the CVS so I could check it is in place tomorrow? Thanks a lot. Regards Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Another automake victim
I could not build on cygwin until I installed automake 1.6. I tried to install autoconf 2.53 or 2.54 and could not do it for some reason, so I am still running autoconf 2.52. This seems to require that I get in and take the continuation symbols out of the configure.ac files. I can build the stable cvs versions of simgear and flightgear now, but the devel version of simgear does not build, failing as follows: g++ -DHAVE_CONFIG_H -I. -I. -I../../../simgear -I../../..-g -O2 -D_REENTRANT -c -o SkyLight.o `test -f SkyLight.cpp || echo './'`SkyLight.cpp SkyLight.cpp:31: extgl.h: No such file or directory In file included from SkyTextureState.hpp:28, from SkyMaterial.hpp:31, from SkyLight.cpp:35: SkyContext.hpp:40: extgl.h: No such file or directory make[4]: *** [SkyLight.o] Error 1 make[4]: Leaving directory `/usr/local/src/cvs-devel/SimGear/simgear/sky/clouds3 d' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/usr/local/src/cvs-devel/SimGear/simgear/sky' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/cvs-devel/SimGear/simgear' make[1]: *** [all] Error 2 make[1]: Leaving directory `/usr/local/src/cvs-devel/SimGear/simgear' make: *** [all-recursive] Error 1 Mark -Original Message- From: Norman Vine [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 17, 2002 9:49 PM To: [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] Another automake victim The Bergrens writes: Sounds like you need the perl module called strict to be installed. Or maybe your perl installation is hosed. You can get perl modules from cpan.org, I think. There was a bug in Cygwin Perl that 'can' be triggered by automake when running on a project on a 'text' mounted drive. The cure is to do all of your work on a 'binary' mount Since I discovered the problem I have never tried automake on a text mount so I am not 100% that this bug still exists BUT if you are working on a 'text' mount HTH Norman - Original Message - From: William Earnest [EMAIL PROTECTED] To: Devel Flightgear [EMAIL PROTECTED] Sent: Tuesday, September 10, 2002 10:38 PM Subject: [Flightgear-devel] Another automake victim Hello all, Came back from vacation to find the new release and lots of discussion. Read everything (I think), and managed to get CVS caught up, including the new SimGear path. Updated plib without problem, then went to SimGear to continue. At the autogen.sh step, got the following pile of errors, which has me rather puzzled. Supposedly have automake 1.5 installed, as well as autoconf 2.52. Any suggestions? [wde@hulk SG]$ ./autogen.sh Can't locate strict.pm in @INC (@INC contains: /usr/share/automake /usr/lib/perl5/5.00503/i386-linux /usr/lib/perl5/5.00503 /usr/lib/perl5/site_perl/5.005/i386-linux /usr/lib/perl5/site_perl/5.005 .) at /usr/share/automake/Automake/Struct.pm line 29. BEGIN failed--compilation aborted at /usr/share/automake/Automake/Struct.pm line 29. BEGIN failed--compilation aborted at /usr/bin/automake line 39. ./autogen.sh: test: -lt: unary operator expected Host info: Linux i686 Can't locate strict.pm in @INC (@INC contains: /usr/share/automake /usr/lib/perl5/5.00503/i386-linux /usr/lib/perl5/5.00503 /usr/lib/perl5/site_perl/5.005/i386-linux /usr/lib/perl5/site_perl/5.005 .) at /usr/share/automake/Automake/Struct.pm line 29. BEGIN failed--compilation aborted at /usr/share/automake/Automake/Struct.pm line 29. BEGIN failed--compilation aborted at /usr/bin/automake line 39. automake: () Running aclocal Running autoheader /usr/bin/m4: configure.in: No such file or directory ERROR: autoheader didn't create simgear/simgear_config.h.in! -- Bill Earnest wde3@ptd-dot-net Linux Powered Allentown, PA, USA Computers, like air conditioners, work poorly with Windows open. ___ 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 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] Re: [Flightgear-cvslogs] Base CVSupdate:'FlightGear/FlightGear/Aircraft/c172'
Is there some reasoning behind setting the steering gains according to the brake selection? This makes no sense to me. It looks to me like their needs to be a separate steering selection (or just specify the gain in the config file). Agreed. I beg your indulgence - let me have a look at this this evening. I'll try and get it resolved. I'll have to wait til the season opener for Enterprise is over though. :-) Jon smime.p7s Description: application/pkcs7-signature
Re: [Flightgear-devel] Removed simgear/interpreter/
On Wed, 18 Sep 2002 15:39:11 -0500 Curtis L. Olson [EMAIL PROTECTED] wrote: David Megginson writes: I've updated configure.ac, but have not changed SimGear.dsp (an MSVC thing?). If someone who uses this file can send me a patched version, I'll commit it ASAP. The MSVC work spaces are generated automatically whenever I run make dist. I have taken care of this. I'm not sure if the am2dsp perl script will work any longer since we've changed to configure.ac. Am2dsp is just automake modified to generate dsp and dsw files instead of Makefile.am. If and when time allows I'll modify it to use the new regime. Bernie ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Re: [Flightgear-cvslogs] BaseCVSupdate:'FlightGear/FlightGear/Aircraft/c172'
On Wed, 2002-09-18 at 17:48, Jon Berndt wrote: Is there some reasoning behind setting the steering gains according to the brake selection? This makes no sense to me. It looks to me like their needs to be a separate steering selection (or just specify the gain in the config file). Agreed. I beg your indulgence - let me have a look at this this evening. I'll try and get it resolved. I'll have to wait til the season opener for Enterprise is over though. :-) Oh, oh tonight's the premiere? Cool. You are officially excused from all JSBSim obligations. ;-) Jon -- Tony Peden [EMAIL PROTECTED] We all know Linux is great ... it does infinite loops in 5 seconds. -- attributed to Linus Torvalds ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Removed simgear/interpreter/
Bernie Bright writes: On Wed, 18 Sep 2002 15:39:11 -0500 Curtis L. Olson [EMAIL PROTECTED] wrote: David Megginson writes: I've updated configure.ac, but have not changed SimGear.dsp (an MSVC thing?). If someone who uses this file can send me a patched version, I'll commit it ASAP. The MSVC work spaces are generated automatically whenever I run make dist. I have taken care of this. I'm not sure if the am2dsp perl script will work any longer since we've changed to configure.ac. Am2dsp is just automake modified to generate dsp and dsw files instead of Makefile.am. If and when time allows I'll modify it to use the new regime. the am2dsp script still seems to be doing something at least plausible. Hopefully it won't take too much tweaking to update. Thanks, 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] Another automake victim
Mark, I don't think anyone has sent me a copy of extgl.h to add to the cvs repository. Curt. Boslough, Mark B writes: I could not build on cygwin until I installed automake 1.6. I tried to install autoconf 2.53 or 2.54 and could not do it for some reason, so I am still running autoconf 2.52. This seems to require that I get in and take the continuation symbols out of the configure.ac files. I can build the stable cvs versions of simgear and flightgear now, but the devel version of simgear does not build, failing as follows: g++ -DHAVE_CONFIG_H -I. -I. -I../../../simgear -I../../..-g -O2 -D_REENTRANT -c -o SkyLight.o `test -f SkyLight.cpp || echo './'`SkyLight.cpp SkyLight.cpp:31: extgl.h: No such file or directory In file included from SkyTextureState.hpp:28, from SkyMaterial.hpp:31, from SkyLight.cpp:35: SkyContext.hpp:40: extgl.h: No such file or directory make[4]: *** [SkyLight.o] Error 1 make[4]: Leaving directory `/usr/local/src/cvs-devel/SimGear/simgear/sky/clouds3 d' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/usr/local/src/cvs-devel/SimGear/simgear/sky' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/cvs-devel/SimGear/simgear' make[1]: *** [all] Error 2 make[1]: Leaving directory `/usr/local/src/cvs-devel/SimGear/simgear' make: *** [all-recursive] Error 1 Mark -Original Message- From: Norman Vine [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 17, 2002 9:49 PM To: [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] Another automake victim The Bergrens writes: Sounds like you need the perl module called strict to be installed. Or maybe your perl installation is hosed. You can get perl modules from cpan.org, I think. There was a bug in Cygwin Perl that 'can' be triggered by automake when running on a project on a 'text' mounted drive. The cure is to do all of your work on a 'binary' mount Since I discovered the problem I have never tried automake on a text mount so I am not 100% that this bug still exists BUT if you are working on a 'text' mount HTH Norman - Original Message - From: William Earnest [EMAIL PROTECTED] To: Devel Flightgear [EMAIL PROTECTED] Sent: Tuesday, September 10, 2002 10:38 PM Subject: [Flightgear-devel] Another automake victim Hello all, Came back from vacation to find the new release and lots of discussion. Read everything (I think), and managed to get CVS caught up, including the new SimGear path. Updated plib without problem, then went to SimGear to continue. At the autogen.sh step, got the following pile of errors, which has me rather puzzled. Supposedly have automake 1.5 installed, as well as autoconf 2.52. Any suggestions? [wde@hulk SG]$ ./autogen.sh Can't locate strict.pm in @INC (@INC contains: /usr/share/automake /usr/lib/perl5/5.00503/i386-linux /usr/lib/perl5/5.00503 /usr/lib/perl5/site_perl/5.005/i386-linux /usr/lib/perl5/site_perl/5.005 .) at /usr/share/automake/Automake/Struct.pm line 29. BEGIN failed--compilation aborted at /usr/share/automake/Automake/Struct.pm line 29. BEGIN failed--compilation aborted at /usr/bin/automake line 39. ./autogen.sh: test: -lt: unary operator expected Host info: Linux i686 Can't locate strict.pm in @INC (@INC contains: /usr/share/automake /usr/lib/perl5/5.00503/i386-linux /usr/lib/perl5/5.00503 /usr/lib/perl5/site_perl/5.005/i386-linux /usr/lib/perl5/site_perl/5.005 .) at /usr/share/automake/Automake/Struct.pm line 29. BEGIN failed--compilation aborted at /usr/share/automake/Automake/Struct.pm line 29. BEGIN failed--compilation aborted at /usr/bin/automake line 39. automake: () Running aclocal Running autoheader /usr/bin/m4: configure.in: No such file or directory ERROR: autoheader didn't create simgear/simgear_config.h.in! -- Bill Earnest wde3@ptd-dot-net Linux Powered Allentown, PA, USA Computers, like air conditioners, work poorly with Windows open. ___ 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 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 -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin
Re: [Flightgear-devel] 3d cloud rendering problems
Norman Vine writes: I think you are on to something ! That would explain the lightening of the clouds with each pass. BUT this only started after I updated my code the other day !. Also I never had the 'text' texture Right now I'm wondering if it is related to the use of glColorMaterial()? I've never had that play nice with setting material colors explicitely (with lighting turned on.) I remember Steve Baker investigating the exact specification of what should happen when you switch between the two methods of specifying colors. His conclusion was that the spec was ill defined and not even his high placed contacts had a good answer. The cloud3d code appears to be using glColorMaterial() to set the color and I'm thinking that colors from the rest of FlightGear are bleeding over into the cloud code. i.e. when I enable the HUD I start getting dark green clouds. When I disable the HUD, the clouds start popping back to shades of gray. FYI I have to leave FGFS alone so I get some real work done for a couple of days, mapserver stuff. But I am still reading mail :-) Not fair! We are so close... :-) 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] 3d cloud rendering problems
Curtis L. Olson Norman Vine writes: I think you are on to something ! That would explain the lightening of the clouds with each pass. BUT this only started after I updated my code the other day !. Also I never had the 'text' texture Right now I'm wondering if it is related to the use of glColorMaterial()? The curious thing is that the 'coloring bug' and the the texture 'jitter' just appeared recently and I can't see what changed to cause it. Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Another automake victim
Curtis L. Olson writes: I don't think anyone has sent me a copy of extgl.h to add to the cvs repository. It is in this tarball http://rockfish.net/~nhv/fgfs/clouds.tgz Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Modeling wing twist animation
One possible application of being able to apply the smoothing calculation to a group of 3D Model objects (as opposed to a single object in ac3d format) is in animating the Wright Brother's twisting wing lateral control method. One way would be to use and interpret user data entries in the model, but I'm wondering if it would be better (or possible) to do it through the xml model animation interface. That way the ac3d models would be complete as is (without interpreting the user data) and the behavior could be more easily modified (in XML) by someone that did not have the software. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] 3d cloud rendering problems
Norman Vine writes: Curtis L. Olson Norman Vine writes: I think you are on to something ! That would explain the lightening of the clouds with each pass. BUT this only started after I updated my code the other day !. Also I never had the 'text' texture Right now I'm wondering if it is related to the use of glColorMaterial()? The curious thing is that the 'coloring bug' and the the texture 'jitter' just appeared recently and I can't see what changed to cause it. Dohh! Disabling lighting seems like it may have fixed the problem. Still playing. 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] SimGear CVS failure?
I get this error this evening for the SimGear CVS server: $ cvs update -dP ? metakit-2.4.2 ? metakit-2.4.2-32.tar ? zlib-1.1.3.tar.gz ? simgear/metakit ? simgear/zlib ? src-libs/boost ? src-libs/Makefile ? src-libs/Makefile.in cvs server: Updating . cvs server: failed to create lock directory for `/var/cvs/SimGear-0.0/SimGear' (/var/cvs/SimGear-0.0/SimGear/#cvs.lock): Permission denied cvs server: failed to obtain dir lock in repository `/var/cvs/SimGear-0.0/SimGear' cvs [server aborted]: read lock failed - giving up smime.p7s Description: application/pkcs7-signature
[Flightgear-devel] C++ Question/Problem, WRT New Sky Code
When I rebuilt the MacOS X version of FlightGear, after the 3D cloud code was added, I started getting an EXC_BAD_ACCESS runtime error. I did some looking around with gdb and found out that the error was happening BEFORE the main was being called. Program received signal EXC_BAD_ACCESS, Could not access memory. 0x90989544 in glGetIntegerv () (gdb) backtrace #0 0x90989544 in glGetIntegerv () #1 0x002130b8 in SkyTextureState::SkyTextureState() (this=0x41e0478) at SkyTextureState.cpp:47 #2 0x00212814 in SkyMaterial::SkyMaterial() (this=0x41e03d0) at SkyMaterial.cpp:60 #3 0x0016df60 in SkyLight::SkyLight(SkyLight::SkyLightType) (this=0x0, eType=3221223248) at SkyLight.cpp:67 #4 0x003167c4 in __static_initialization_and_destruction_0(int, int) () #5 0x8fe16594 in __dyld_call_module_initializers_for_objects () #6 0x8fe160a0 in __dyld_call_module_initializers () #7 0x8fe133ac in __dyld__dyld_make_delayed_module_initializer_calls () #8 0x2c04 in _call_mod_init_funcs () at /SourceCache/Csu/Csu-45/crt.c:299 #9 0x2aec in _start (argc=1, argv=0xbc54, envp=0xbc5c) at /SourceCache/Csu/Csu-45/crt.c:217 #10 0x2a4c in start () How is this possible? If this were Ada, I would say that it is happening during Elaboration, but I'm not sure if C++ has something similar. SkyLight::SkyLight is creating a new instance of SkyMaterial, and my bet is that glGetIntegerv is having the problem because OpenGL hasn't been initialized yet. Does anyone have any ideas as to what is going wrong and why? Thanks, Jonathan Polley ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Base Package size (was 3D clouds)
What I meant is to only keep $FG_ROOT/Clouds3D/large.sky and $FG_ROOT/Clouds3D/field56.cld Right, thats what I thought you meant. I was talking about the other files in that directory. I know that field56.cld is the only file currently referenced in large.sky, but I'd still rather wait a little. Yes, might be useful down the road to keep the other cloud 'scripts' Okay, I sent an update of the loader to Curtis which hopefully cleared up some of the problems with the file names. The new loader allows you to place the base directory wherever you please as in: /my/favorite/place/FlightGear. Now large.sky should be at the FlightGear level and Data can be renamed to whatever. The suggestion Fred made for Clouds3D seems like an execellent choice provided the name in large.sky is changed to /Clouds3D/SkyClouds/field56.cld. this should be usable until we get around to rewriting the loader to remove all file pathname references from the file itself. You should be able to run from any location as long as your $fg_root is set to /my/favorite/place/ Regards John W. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] C++ Question/Problem, WRT New Sky Code
From: Jonathan Polley [EMAIL PROTECTED] When I rebuilt the MacOS X version of FlightGear, after the 3D cloud code was added, I started getting an EXC_BAD_ACCESS runtime error. I did some looking around with gdb and found out that the error was happening BEFORE the main was being called. Program received signal EXC_BAD_ACCESS, Could not access memory. 0x90989544 in glGetIntegerv () (gdb) backtrace #0 0x90989544 in glGetIntegerv () #1 0x002130b8 in SkyTextureState::SkyTextureState() (this=0x41e0478) at SkyTextureState.cpp:47 #2 0x00212814 in SkyMaterial::SkyMaterial() (this=0x41e03d0) at SkyMaterial.cpp:60 #3 0x0016df60 in SkyLight::SkyLight(SkyLight::SkyLightType) (this=0x0, Very strange ! eType=3221223248) at SkyLight.cpp:67 ^^ Strange too ! #4 0x003167c4 in __static_initialization_and_destruction_0(int, int) () #5 0x8fe16594 in __dyld_call_module_initializers_for_objects () #6 0x8fe160a0 in __dyld_call_module_initializers () #7 0x8fe133ac in __dyld__dyld_make_delayed_module_initializer_calls () #8 0x2c04 in _call_mod_init_funcs () at /SourceCache/Csu/Csu-45/crt.c:299 #9 0x2aec in _start (argc=1, argv=0xbc54, envp=0xbc5c) at /SourceCache/Csu/Csu-45/crt.c:217 #10 0x2a4c in start () How is this possible? If this were Ada, I would say that it is happening during Elaboration, but I'm not sure if C++ has something similar. SkyLight::SkyLight is creating a new instance of SkyMaterial, and my bet is that glGetIntegerv is having the problem because OpenGL hasn't been initialized yet. I don't looked at the code but it seems that there is a SkyLight global variable (or a static member one) defined. However, the fact that the constructor is called with a this null pointer seems odd to me. Cheers, -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
