Re: [Flightgear-devel] Error compiling FlightGear
I have tried everything I can think off. I have reinstalled the plib1.8.4 and plib1.8.4-dev packages. I have recompiled simgear. I have even reinstalled all the graphics-related package, but I still get the same error messages when I was trying to compile FlightGear. In the attachment is a list of packaged that I have installed. Perhaps someone can point out the package that I am missing? If I have all the necessary packages, would faulty simlinks be the cause of my problems? Please help, =( Ampere ii adduser3.63 Add and remove users and groups ii alien 8.52 install non-native packages with dpkg ii alsa-base 1.0.8-7ALSA driver configuration files ii alsa-utils 1.0.8-4ALSA utilities ii apt0.5.28.6 Advanced front-end for dpkg ii apt-utils 0.5.28.6 APT utility programs ii aptitude 0.2.15.9-2 terminal-based apt frontend ii ark3.3.2-1KDE archiving tool ii ash0.5.2-4Compatibility package for the Debian Almquis ii at 3.1.8-11 Delayed job execution and batch processing ii autoconf 2.59a-3automatic configure script builder ii automake1.81.8.5-3A tool for generating GNU Standards-complian ii autotools-dev 20050422.1 Update infrastructure for config.{guess,sub} ii base-config2.64 Debian base system configurator ii base-files 3.1.2 Debian base system miscellaneous files ii base-passwd3.5.9 Debian base system master password and group ii bash 3.0-14 The GNU Bourne Again SHell ii bc 1.06-17The GNU bc arbitrary precision calculator la ii binutils 2.15-5 The GNU assembler, linker and binary utiliti ii bsdmainutils 6.0.17 collection of more utilities from FreeBSD ii bsdutils 2.12p-4Basic utilities from 4.4BSD-Lite ii bzip2 1.0.2-5high-quality block-sorting file compressor - ii console-common 0.7.51 Basic infrastructure for text console config ii console-data 2002.12.04dbs- Keymaps, fonts, charset maps, fallback table ii console-tools 0.2.3dbs-56Linux console and font utilities ii coreutils 5.2.1-2The GNU core utilities ii cpio 2.5-1.2GNU cpio -- a program to manage archives of ii cpp3.3.5-3The GNU C preprocessor (cpp) ii cpp-3.33.3.5-12 The GNU C preprocessor ii cpp-3.43.4.3-12 The GNU C preprocessor ii cramfsprogs1.1-6 Tools for CramFs (Compressed ROM File System ii cron 3.0pl1-87 management of regular background processing ii cryptplug 0.3.16-1 Collection of plugins to crytographic engine ii cvs1.12.9-13 Concurrent Versions System ii dash 0.5.2-4The Debian Almquist Shell ii dbus-1 0.23.4-1 simple interprocess messaging system ii debconf1.4.48 Debian configuration management system ii debconf-i18n 1.4.48 full internationalization support for debcon ii debconf-utils 1.4.48 debconf utilities ii debhelper 4.2.35 helper programs for debian/rules ii debianutils2.13.2 Miscellaneous utilities specific to Debian ii defoma 0.11.8-0.1 Debian Font Manager -- automatic font config ii dhcp-client2.0pl5-19.1DHCP Client ii dialog 1.0-20050306-1 Displays user-friendly dialog boxes from she ii dictionaries-c 0.25.8 Common utilities for spelling dictionary too ii diff 2.8.1-11 File comparison utilities ii discover 2.0.7-2.1 hardware identification system ii discover-data 2.2005.02.13-1 Data lists for Discover hardware detection s ii dpkg 1.10.27Package maintenance system for Debian ii dpkg-dev 1.10.27Package building tools for Debian ii drm-trunk-modu 2005.02.08-1 Source for the DRI CVS trunk DRM modules ii dselect1.10.27a user tool to manage Debian packages ii e2fslibs 1.37-2 ext2 filesystem libraries ii e2fsprogs 1.37-2 ext2 file system utilities and libraries ii ed 0.2-20 The classic unix line editor ii eject 2.0.13deb-8sar ejects CDs and operates CD-Changers under Li ii emacsen-common 1.4.16 Common facilities for all emacsen ii enscript 1.6.4-7Converts ASCII text to Postscript, HTML, RTF ii esound-common 0.2.35-2 Enlightened Sound Daemon - Common files ii exim4 4.50-6 metapackage to ease exim MTA (v4) installati ii exim4-base 4.50-6 support files for all exim MTA (v4) packages ii exim4-config 4.50-6 configuration for the exim MTA (v4) ii exim4-daemon-l 4.50-6 lightweight exim MTA (v4) daemon ii fdutils5.4-20040228-3 Linux floppy utilities ii festival
[Flightgear-devel] Re: Error compiling FlightGear
* Ampere K. Hardraade -- Saturday 30 April 2005 23:50: gcc -g -O2 -D_REENTRANT -L/usr/X11R6/lib -L/usr/local//lib -o gl-info gl-info.o -lSM -lICE -lXi -lXext -lX11 -ldl -lm gl-info.o(.text+0xd): In function `getPrints': /usr/local/src/FlightGear-0.9.8/tests/gl-info.c:28: undefined reference to `glGetString' These libs are missing from the command line: -lglut -lGLU -lGL (that is libglut, libGLU and libGL). I wonder why the configuration script didn't point this out, but it seems as if OpenGL isn't installed. Maybe only the respective *-devel packages are missing. I am seeing double slashes in the above outputs. Same here. That's ugly, but valid and certainly not the cause. I've moved to Xorg recently That explains it. Apparently you had the OpenGL libs/headers installed in the XFree86 tree, but not yet in the Xorg tree. Installing the (nvidia?) graphics drivers again (and probably glut, too -- http://freeglut.sf.net/) should fix the problem. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Error compiling FlightGear
* Ampere K. Hardraade -- Monday 02 May 2005 09:17: In the attachment is a list of packaged that I have installed. Perhaps someone can point out the package that I am missing? Oh. freeglut and something that looks like opengl is already there, but the commend in brackets looks suspicious: xlibmesa-gl4.3.0.dfsg.1-1 Mesa 3D graphics library [XFree86] For XFree86? But you are running Xorg's X11R6.8.* now? Maybe you need a different [Xorg] version of these packages? m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] AI related
Hi there, I'm looking for documentation about AI objects. Maybe someone can help : I want to be able to create AI objects within my code on the fly, to be able to move them and let FG draw them. Does somebody has an idea ? remarks ? Can somebody point me on doc ? Thanks in advance. David ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] AI related
David BONNEVILLE Hi there, I'm looking for documentation about AI objects. Maybe someone can help : I want to be able to create AI objects within my code on the fly, to be able to move them and let FG draw them. Does somebody has an idea ? remarks ? Can somebody point me on doc ? Sounds as if AI Ballistic objects might do much of what you want. See README.submodels in /data/docs Regards, Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Error compiling FlightGear
On Mon, 2 May 2005 03:17:08 -0400, Ampere wrote in message [EMAIL PROTECTED]: I have tried everything I can think off. I have reinstalled the plib1.8.4 and plib1.8.4-dev packages. I have recompiled simgear. I have even reinstalled all the graphics-related package, but I still get the same error messages when I was trying to compile FlightGear. In the attachment is a list of packaged that I have installed. Perhaps someone can point out the package that I am missing? ..I don't see X.org installed in your list, you compiled from source and put it in the /usr/local tree? If I have all the necessary packages, would faulty simlinks be the cause of my problems? Please help, =( Ampere -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] AI related
I'm looking for documentation about AI objects. Maybe someone can help : I want to be able to create AI objects within my code on the fly, to be able to move them and let FG draw them. Does somebody has an idea ? remarks ? Can somebody point me on doc ? There is some here: http://www.seedwiki.com/wiki/flight_gear/ai_model.cfm?wpid=141766 but a problem with rendering XML in wiki makes them hard to read. Right now there are two instances where AI objects are created on-the-fly. One is in the submodels manager (see /source/src/AIModel/submodels.cxx). These are ballistic AI objects the emanate from the user airplane. Currently this is used for contrails, smoke, flares, tracers, etc. The other instance is Durk's Traffic Manager, which creates AI aircraft based on a schedule, and creates flightplans for them. This provides ongoing airline traffic. Dave ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] thunderstorm, lightning
Just checked in to CVS is a demo of an AI thunderstorm with lightning. Some notes: 1) To run this just use the AI scenario called bigstorm_demo.xml 2) You will see a 37000 foot thunderstorm over San Francisco, with lightning flashes. It looks best if your visibility is set to at least 10 miles. Even though the lightning's emmissivity is set to maximum, it will be attenuated by the visibility value. 3) The lightning is triggered by a boolean property, environment/lightning/flash, which is controlled by code within AIStorm.cxx 4) The 3D model, bigstorm.ac, has a lightning object that is selected on whenever environment/lightning/flash is true. 5) The lightning is also attenuated by the rain, so the rain object is set to turn off whenever environment/lighning/flash is true. There might be a better way to do this, but I don't know what it is. 6) This is a first-cut at lightning, and any further development will depend on the possibility of integrating the new clouds code, so I don't know where this will go from here. 7) It would be easy to add triggers for rain, turbulence and St. Elmo's fire, based on the user aircraft's distance from the center of the storm. On the other hand, why model things you are never supposed to do (like crash)? Dave ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] AI related
Right now there are two instances where AI objects are created on-the-fly. One is in the submodels manager (see /source/src/AIModel/submodels.cxx). These are ballistic AI objects the emanate from the user airplane. Currently this is used for contrails, smoke, flares, tracers, etc. The other instance is Durk's Traffic Manager, which creates AI aircraft based on a schedule, and creates flightplans for them. This provides ongoing airline traffic. You might want to have a look at Traffic/Schedule.cxx, around line 353, where I'm creating new AIAircraft objects. These models have their own FDM, however, which take care of moving them around. If you want to move the ojects around yourself, you probably have to write your own movement code, possibly by deriving your own class from AIBase. HTH, Durk ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] AI weirdness
$ strace -fF -eopen fgfs -D --aircraft=ufo 21|grep -c /Airports/AI/ 49194 Is there really no better way than to check for the existance of 49194(!) files during startup? Two for every ICAO id? [pid 377] open(/usr/local/share/FlightGear/Airports/AI//EGKH/parking.xml, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 377] open(/usr/local/share/FlightGear/Airports/AI//EGKH/rwyuse.xml, O_RDONLY) = -1 ENOENT (No such file or directory) ... repeated 24596 times ... What about asking for all existing files in $FG_ROOT/Airports/AI? Let's see: $ ls -l $FG_ROOT/Airports/AI /bin/ls: /usr/local/share/FlightGear/Airports/AI: No such file or directory Whoops ... m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] AI weirdness
On Monday 02 May 2005 20:41, Melchior FRANZ wrote: $ strace -fF -eopen fgfs -D --aircraft=ufo 21|grep -c /Airports/AI/ 49194 Is there really no better way than to check for the existance of 49194(!) files during startup? Two for every ICAO id? [pid 377] open(/usr/local/share/FlightGear/Airports/AI//EGKH/parking.xml, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 377] open(/usr/local/share/FlightGear/Airports/AI//EGKH/rwyuse.xml, O_RDONLY) = -1 ENOENT (No such file or directory) ... repeated 24596 times ... What about asking for all existing files in $FG_ROOT/Airports/AI? Let's see: $ ls -l $FG_ROOT/Airports/AI /bin/ls: /usr/local/share/FlightGear/Airports/AI: No such file or directory Whoops ... Well, the idea is to make the files in question (rwyuse.xml and parking.xml) completely plugable. If the file exists for an airport, it will be read and used, if not, some generic fallback mechanism will be used. But mind you, this is still very much a development version and if there are alternative approaches, I'm interested. I don't know what point you're trying to make: either that there is such a big discrepancy between the number of files that are checked for their precence, and the fact that there are currently none in CVS, or do you suggest an alternative approach? If the former: I do have a few parking and rwyuse files at my local copy, which I can't release yet, for licencing reasons. I've been taking a break from AI development over the last couple of weeks and only very slowly getting back to it. As such, I haven't had a chance to get back to the parking/rwyuse file issue. If the latter: please elaborate. As I said above, if there's an alternative approach, with obvious advantages, I'm interested. Cheers, Durk ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: AI weirdness
* Durk Talsma -- Monday 02 May 2005 21:16: I don't know what point you're trying to make: either that there is such a big discrepancy between the number of files that are checked for their precence, and the fact that there are currently none in CVS, Well, checking for 5 files when we can probably only expect a few hundreds in the next ten years seems like a waste of performance. No big problem on Linux with normal file systems (apart from the needless noise in debugging runs). But I wouldn't be surprised if this is a problem on other operating systems, like Win95. (Or NFS?) I thought the alternative approach would be obvious. Instead of checking for the existence of 5 possible files just ask the system for actual files? m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: AI weirdness
On Monday 02 May 2005 21:23, Melchior FRANZ wrote: * Durk Talsma -- Monday 02 May 2005 21:16: I don't know what point you're trying to make: either that there is such a big discrepancy between the number of files that are checked for their precence, and the fact that there are currently none in CVS, Well, checking for 5 files when we can probably only expect a few hundreds in the next ten years seems like a waste of performance. No big problem on Linux with normal file systems (apart from the needless noise in debugging runs). But I wouldn't be surprised if this is a problem on other operating systems, like Win95. (Or NFS?) I thought the alternative approach would be obvious. Instead of checking for the existence of 5 possible files just ask the system for actual files? Okay, thanks for clarifying. I see what you mean. I'll put this on my TODO list. Might take a few weeks though before I'm fully back to working on this. Cheers, Durk ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: AI weirdness
Melchior FRANZ wrote : * Durk Talsma -- Monday 02 May 2005 21:16: I don't know what point you're trying to make: either that there is such a big discrepancy between the number of files that are checked for their precence, and the fact that there are currently none in CVS, Well, checking for 5 files when we can probably only expect a few hundreds in the next ten years seems like a waste of performance. No big problem on Linux with normal file systems (apart from the needless noise in debugging runs). But I wouldn't be surprised if this is a problem on other operating systems, like Win95. (Or NFS?) I thought the alternative approach would be obvious. Instead of checking for the existence of 5 possible files just ask the system for actual files? I didn't see a problem yet, but if we can avoid a long startup time, it is better. Let me rephrase Melchior's suggestion : iterate on directories with plib's ulOpenDir and ulReadDir functions, possibly being recursive in the tree, and check if the name of the reported files are an existing ICAO code against the database already loaded in memory. Examples of directory scan are in fgadmin and in fgrun. -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Error compiling FlightGear
On May 2, 2005 07:42 am, Arnt Karlsen wrote: ..I don't see X.org installed in your list, you compiled from source and put it in the /usr/local tree? No. I put a source in my /etc/apt/sources.list and got the binary from http://www.nixnuts.net/files/. I didn't perform any compilation. Xorg is installed: ii xserver-xfree8 2005.02.08-1 The Xorg X server [DRI trunk] I even confirmed it running by running the Check.sh script from ATI's website. Here's the output: Detected configuration: Architecture: i686 (32-bit) X Server: Xorg 6.8.1.99 Oh, one more thing. Could this be the problem? [EMAIL PROTECTED]:~$ cat /var/log/Xorg.0.log | grep EE (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (EE) Failed to load /usr/X11R6/lib/modules-dri-trunk/extensions/libGLcore.so (EE) Failed to load module GLcore (loader failed, 7) (II) Loading extension MIT-SCREEN-SAVER (EE) Couldn't load XKB keymap, falling back to pre-XKB keymap Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Error compiling FlightGear
On May 2, 2005 03:39 am, Melchior FRANZ wrote: Oh. freeglut and something that looks like opengl is already there, but the commend in brackets looks suspicious: xlibmesa-gl4.3.0.dfsg.1-1 Mesa 3D graphics library [XFree86] For XFree86? But you are running Xorg's X11R6.8.* now? Maybe you need a different [Xorg] version of these packages? m. I now got the Xorg versions of mesa from ubuntu repostory. ii xlibmesa-dev 6.8.2-10 X.Org Mesa development libraries transitiona ii xlibmesa-dri 6.8.2-10 Mesa 3D graphics library modules [X.Org] ii xlibmesa-gl6.8.2-10 Mesa 3D graphics library [X.Org] ii xlibmesa-gl-de 6.8.2-10 Mesa 3D graphics library development files [ ii xlibmesa-gl1-d 2005.02.08-1 Mesa 3D graphics library [DRI trunk] ii xlibmesa-glu 6.8.2-10 Mesa OpenGL utility library [X.Org] ii xlibmesa-glu-d 6.8.2-10 Mesa OpenGL utility library development file They didn't make any different. I'm still getting the same errors when I am trying to compile FlightGear. Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Error compiling FlightGear
* Ampere K. Hardraade -- Monday 02 May 2005 22:35: I now got the Xorg versions of mesa from ubuntu repostory. ii xlibmesa-dri 6.8.2-10 Mesa 3D graphics library modules [X.Org] [...] They didn't make any different. I'm still getting the same errors when I am trying to compile FlightGear. Strange. Do other 3D apps work? Or is it just an fgfs compilation problem? (The worst thing that could happen, actually! ;-) My favorite strace could give you some hint in either case: A) $ strace -fF -eopen glxinfo 21|tee /tmp/strace.log B) $ strace -fF -eopen ./configure 21|tee /tmp/strace.log If you search through that log file, you'll see *where* and *what* either program searches, and why it doesn't find what it searches. Especially /libopengl would be interesting. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Error compiling FlightGear
* Ampere K. Hardraade -- Monday 02 May 2005 22:16: (EE) Failed to load /usr/X11R6/lib/modules-dri-trunk/extensions/libGLcore.so (EE) Failed to load module GLcore (loader failed, 7) This does indeed look ugly. I assume that no 3d apps are running HW accelerated? I still wonder, though, how fgfs' configure could run through without complaint. You should also clean the source trees if you haven't already (make clean; rm -rf autom4te.cache) and configure again. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Error compiling FlightGear
On May 2, 2005 04:41 pm, Melchior FRANZ wrote: This does indeed look ugly. I assume that no 3d apps are running HW accelerated? I don't really know. glxinfo says direct rendering: yes. Xorg.0.log also reports direct rendering is enabled. Enemy Territory also runs, although it is virtually unplayable just like the days when I was using XFree. All these evidences are telling me that applications are using hardware acceleration, but I have a feeling that applications are still relying on software rendering. I still wonder, though, how fgfs' configure could run through without complaint. You should also clean the source trees if you haven't already (make clean; rm -rf autom4te.cache) and configure again. Configure returned no problem, but FlightGear still failed to compile. Same errors. Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Error compiling FlightGear
On Mon, 2 May 2005 16:16:49 -0400, Ampere wrote in message [EMAIL PROTECTED]: On May 2, 2005 07:42 am, Arnt Karlsen wrote: ..I don't see X.org installed in your list, you compiled from source and put it in the /usr/local tree? No. I put a source in my /etc/apt/sources.list and got the binary from http://www.nixnuts.net/files/. I didn't perform any compilation. Xorg is installed: ii xserver-xfree8 2005.02.08-1 The Xorg X server [DRI trunk] I even confirmed it running by running the Check.sh script from ATI's website. ..their Check.sh is meant for what??? Their own proprietary drivers, or also for open source X.org Here's the output: Detected configuration: Architecture: i686 (32-bit) X Server: Xorg 6.8.1.99 Oh, one more thing. Could this be the problem? [EMAIL PROTECTED]:~$ cat /var/log/Xorg.0.log | grep EE (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (EE) Failed to load /usr/X11R6/lib/modules-dri-trunk/extensions/libGLcore.so (EE) Failed to load module GLcore (loader failed, 7) ..no, it's possibly a symptom pointing to the problem, this line only says GLcore failed to load, further up in your log we might see why. ..try 'grep -B10 EE', to see 10 lines immediately ahead of each EE. (II) Loading extension MIT-SCREEN-SAVER (EE) Couldn't load XKB keymap, falling back to pre-XKB keymap -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] thunderstorm, lightning
On Mon, 2 May 2005 11:53:26 -0500, Dave wrote in message [EMAIL PROTECTED]: Just checked in to CVS is a demo of an AI thunderstorm with lightning. Some notes: 1) To run this just use the AI scenario called bigstorm_demo.xml 2) You will see a 37000 foot thunderstorm over San Francisco, with lightning flashes. It looks best if your visibility is set to at least 10 miles. Even though the lightning's emmissivity is set to maximum, it will be attenuated by the visibility value. 3) The lightning is triggered by a boolean property, environment/lightning/flash, which is controlled by code within AIStorm.cxx 4) The 3D model, bigstorm.ac, has a lightning object that is selected on whenever environment/lightning/flash is true. 5) The lightning is also attenuated by the rain, so the rain object is set to turn off whenever environment/lighning/flash is true. There might be a better way to do this, but I don't know what it is. 6) This is a first-cut at lightning, and any further development will depend on the possibility of integrating the new clouds code, so I don't know where this will go from here. 7) It would be easy to add triggers for rain, turbulence and St. Elmo's fire, based on the user aircraft's distance from the center of the storm. On the other hand, why model things you are never supposed to do (like crash)? ..because some people enjoy sporty rides in WC-130's? ;o) -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Error compiling FlightGear
On May 2, 2005 04:55 pm, Arnt Karlsen wrote: ..their Check.sh is meant for what??? Their own proprietary drivers, or also for open source X.org It meant to check what version of xserver you are running: XFree4.1.0, XFree4.2.0, XFree4.3.0 and Xorg6.8.0, so people can download the appropiate prorietary drivers. I merely used the script to check what version of xserver is current running. ..no, it's possibly a symptom pointing to the problem, this line only says GLcore failed to load, further up in your log we might see why. ..try 'grep -B10 EE', to see 10 lines immediately ahead of each EE. (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor SyncMaster 172T (**) | |--Device ATI 9200SE (**) |--Input Device Generic Keyboard (**) Option XkbRules xorg (**) XKB: rules: xorg (**) Option XkbModel pc104 -- [19] -1 0 0xe400 - 0xe4ff (0x100) IX[B] [20] -1 0 0xe000 - 0xe01f (0x20) IX[B] [21] -1 0 0xffa0 - 0xffaf (0x10) IX[B] [22] -1 0 0xec00 - 0xec1f (0x20) IX[B] [23] -1 0 0xe880 - 0xe89f (0x20) IX[B] [24] -1 0 0xe800 - 0xe81f (0x20) IX[B] [25] -1 0 0xd800 - 0xd8ff (0x100) IX[B](B) (II) LoadModule: GLcore (II) Loading /usr/X11R6/lib/modules-dri-trunk/extensions/libGLcore.so dlopen: /usr/X11R6/lib/modules-dri-trunk/extensions/libGLcore.so: undefined symbol: __glXLastContext (EE) Failed to load /usr/X11R6/lib/modules-dri-trunk/extensions/libGLcore.so (II) UnloadModule: GLcore (EE) Failed to load module GLcore (loader failed, 7) Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Error compiling FlightGear
On May 2, 2005 04:31 pm, Melchior FRANZ wrote: My favorite strace could give you some hint in either case: A) $ strace -fF -eopen glxinfo 21|tee /tmp/strace.log B) $ strace -fF -eopen ./configure 21|tee /tmp/strace.log If you search through that log file, you'll see *where* and *what* either program searches, and why it doesn't find what it searches. Especially /libopengl would be interesting. Interesting. It seems configure is searching for libGLcore.so and libGL.core.a in /usr/X11R6/lib and other directories, but not /usr/X11R6/lib/modules-dri-trunk where the modules are actually in. [pid 10686] open(/usr/X11R6/lib/libGL.so, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10686] open(/usr/X11R6/lib/libGL.a, O_RDONLY) = 13 [pid 10686] open(/usr/X11R6/lib/libGL.a, O_RDONLY) = 14 [pid 10686] open(/usr/X11R6/lib/libGL.a, O_RDONLY) = 8 [pid 10703] open(/usr/X11R6/lib/libGLcore.so, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/X11R6/lib/libGLcore.a, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/local//lib/libGLcore.so, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/local//lib/libGLcore.a, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/lib/gcc-lib/i486-linux/3.3.5/libGLcore.so, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/lib/gcc-lib/i486-linux/3.3.5/libGLcore.a, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/lib/gcc-lib/i486-linux/3.3.5/../../../libGLcore.so, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/lib/gcc-lib/i486-linux/3.3.5/../../../libGLcore.a, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/bin/../lib/libGLcore.so, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/bin/../lib/libGLcore.a, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/i386-linux/lib/libGLcore.so, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/i386-linux/lib/libGLcore.a, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/local/lib/libGLcore.so, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/local/lib/libGLcore.a, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/lib/libGLcore.so, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/lib/libGLcore.a, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/lib/libGLcore.so, O_RDONLY) = -1 ENOENT (No such file or directory) [pid 10703] open(/usr/lib/libGLcore.a, O_RDONLY) = -1 ENOENT (No such file or directory) ... ... Do you think adding /usr/X11R6/lib/modules-dri-trunk to /etc/ld.so.conf will fix the problem? Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Error compiling FlightGear
* Ampere K. Hardraade -- Monday 02 May 2005 23:06: On May 2, 2005 04:41 pm, Melchior FRANZ wrote: I still wonder, though, how fgfs' configure could run through without complaint. You should also clean the source trees if you haven't already (make clean; rm -rf autom4te.cache) and configure again. Configure returned no problem, but FlightGear still failed to compile. Same errors. Sometimes configure does find some required library (because, for instance, /usr/X11R6/lib is explicitly set in configure.ac), but the compiler doesn't. Is the path where libGL resides listed in /etc/ld.so.conf? If so, did you make a ldconfig (as root) since then? And finally, did strace tell anything about libGL? :-) m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] thunderstorm, lightning
..because some people enjoy sporty rides in WC-130's? ;o) Oh yeah, forgot about those guys :) BTW, here's a screenshot of the bigstorm/lightning; http://home.comcast.net/~davidculp2/bigstorm_lightning.jpg Dave ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Error compiling FlightGear
* Ampere K. Hardraade -- Monday 02 May 2005 23:27: [pid 10686] open(/usr/X11R6/lib/libGL.so, O_RDONLY) = -1 ENOENT (No such file or directory) It doesn't find the dynamic lib ... [pid 10686] open(/usr/X11R6/lib/libGL.a, O_RDONLY) = 13 but a static one. It's an old one, right? Better remove it (or temporarily rename it). Also move other libGL.* files away (such as libGL.la). [pid 10703] open(/usr/X11R6/lib/libGLcore.so, O_RDONLY) = -1 ENOENT (No such file or directory) [lots of ENOENT] Do you think adding /usr/X11R6/lib/modules-dri-trunk to /etc/ld.so.conf will fix the problem? Don't know if the whole tree should be searched automatically, but apparently it isn't, or there are permission problems. Yes, I'd try with this dir added to ld.so.conf. (Don't forget to run ldconfig afterwards.) But your should really first move the old cruft out of the way and make sure that only the newly donwloaded files are found. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Error compiling FlightGear
On Mon, 2 May 2005 17:24:17 -0400, Ampere wrote in message [EMAIL PROTECTED]: On May 2, 2005 04:55 pm, Arnt Karlsen wrote: ..their Check.sh is meant for what??? Their own proprietary drivers, or also for open source X.org It meant to check what version of xserver you are running: XFree4.1.0, XFree4.2.0, XFree4.3.0 and Xorg6.8.0, so people can download the appropiate prorietary drivers. I merely used the script to check what version of xserver is current running. ..no, it's possibly a symptom pointing to the problem, this line only says GLcore failed to load, further up in your log we might see why. ..here I meant how, rather than why, but sometimes we get lucky and can read the why rather than interpret it from symptoms. ..try 'grep -B10 EE', to see 10 lines immediately ahead of each EE. (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor SyncMaster 172T (**) | |--Device ATI 9200SE (**) |--Input Device Generic Keyboard (**) Option XkbRules xorg (**) XKB: rules: xorg (**) Option XkbModel pc104 -- [19] -1 0 0xe400 - 0xe4ff (0x100) IX[B] [20] -1 0 0xe000 - 0xe01f (0x20) IX[B] [21] -1 0 0xffa0 - 0xffaf (0x10) IX[B] [22] -1 0 0xec00 - 0xec1f (0x20) IX[B] [23] -1 0 0xe880 - 0xe89f (0x20) IX[B] [24] -1 0 0xe800 - 0xe81f (0x20) IX[B] [25] -1 0 0xd800 - 0xd8ff (0x100) IX[B](B) (II) LoadModule: GLcore (II) Loading /usr/X11R6/lib/modules-dri-trunk/extensions/libGLcore.so dlopen: /usr/X11R6/lib/modules-dri-trunk/extensions/libGLcore.so: ..play with grep -B 20, 25 etc, I find it hard to believe this: undefined symbol: __glXLastContext ..is causing DRI to fall over. (EE) Failed to load /usr/X11R6/lib/modules-dri-trunk/extensions/libGLcore.so (II) UnloadModule: GLcore (EE) Failed to load module GLcore (loader failed, 7) -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] game engines
eagle monart a écrit : hi everyone, is there an idea of switching to another open sourcegame engine. fg is real beatiful but is weak in visuals especially in terrain rendering.we cant edit terrain as whatever we want , we cant change textures and terrain is not complex. as a result cant feel realistic environment and relative speed. even combat simulator project have better graphics by using osg. i look around few open source graphics engines . some are real great . i start workingon fg source 1 months ago ; so i am new and after all i know what i gain by swtching but can not clearly see what i loose ( there are lots of dependencies and functions:)) any idea? Hello Is it Provocation ?? ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Error compiling FlightGear
First, let me say thank you for all the help, guys. I have reinstalled all the graphics related packages again. For some reasons, it worked this time. I managed to compile FlightGear without problems. But now I am having another issue: FlightGear doesn't run and gives me the following messages instead: WARNING: ssgLoad3ds: Texture coords missing. WARNING: ssgLoad3ds: Texture coords missing. WARNING: ssgSGIHeader::: Failed to open '/usr/local/FlightGear/share/FlightGear/Textures/Sky/cl_cumulus.rgb' for reading. WARNING: ssgSGIHeader::: Failed to open '/usr/local/FlightGear/share/FlightGear/Textures/Sky/cl_stratus.rgb' for reading. X Error of failed request: GLXUnsupportedPrivateRequest Major opcode of failed request: 144 (GLX) Minor opcode of failed request: 16 (X_GLXVendorPrivate) Serial number of failed request: 39 Current serial number in output stream: 40 There are a lot of results when I search for X Error of failed requste, but very little when I include GLXUnsupportedPrivateRequest in the search string. Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Error compiling FlightGear
On May 2, 2005 07:12 pm, Arnt Karlsen wrote: ..play with grep -B 20, 25 etc, I find it hard to believe this: undefined symbol: __glXLastContext ..is causing DRI to fall over. That command doesn't work, nor does grep -B=20. So I have just attached the entire log. Sorry. Ampere log.tar.gz Description: application/tgz ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Error compiling FlightGear
On Mon, 2 May 2005 22:30:07 -0400, Ampere wrote in message [EMAIL PROTECTED]: On May 2, 2005 07:12 pm, Arnt Karlsen wrote: ..play with grep -B 20, 25 etc, I find it hard to believe this: undefined symbol: __glXLastContext ..is causing DRI to fall over. That command doesn't work, nor does grep -B=20. So I have just attached the entire log. Sorry. ..to clarify: ' cat /var/log/Xorg.0.log | grep -B 20 EE ' etc. ;o) -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Error compiling FlightGear
On Mon, 2 May 2005 22:30:07 -0400, Ampere wrote in message [EMAIL PROTECTED]: On May 2, 2005 07:12 pm, Arnt Karlsen wrote: ..play with grep -B 20, 25 etc, I find it hard to believe this: undefined symbol: __glXLastContext ..is causing DRI to fall over. That command doesn't work, nor does grep -B=20. So I have just attached the entire log. Sorry. ..no need to be, you didn't. ;o) Post the ul to your log. -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Error compiling FlightGear
On May 2, 2005 10:26 pm, Arnt Karlsen wrote: cat /var/log/Xorg.0.log | grep -B 20 EE -- [9] -1 0 0xf000 - 0xefff (0x0) MX[B]O [10] -1 0 0xff8c - 0xff8d (0x2) MX[B](B) [11] -1 0 0xff8f - 0xff8f (0x1) MX[B](B) [12] -1 0 0xc000 - 0xcfff (0x1000) MX[B](B) [13] -1 0 0x1f80 - 0x1f8003ff (0x400) MX[B] [14] -1 0 0x2000 - 0x27ff (0x800) MX[B](B) [15] -1 0 0x - 0x (0x1) IX[B] [16] -1 0 0x - 0x00ff (0x100) IX[B] [17] -1 0 0xd400 - 0xd4ff (0x100) IX[B] [18] -1 0 0xe080 - 0xe0bf (0x40) IX[B] [19] -1 0 0xe400 - 0xe4ff (0x100) IX[B] [20] -1 0 0xe000 - 0xe01f (0x20) IX[B] [21] -1 0 0xffa0 - 0xffaf (0x10) IX[B] [22] -1 0 0xec00 - 0xec1f (0x20) IX[B] [23] -1 0 0xe880 - 0xe89f (0x20) IX[B] [24] -1 0 0xe800 - 0xe81f (0x20) IX[B] [25] -1 0 0xd800 - 0xd8ff (0x100) IX[B](B) (II) LoadModule: GLcore (II) Loading /usr/X11R6/lib/modules-dri-trunk/extensions/libGLcore.so dlopen: /usr/X11R6/lib/modules-dri-trunk/extensions/libGLcore.so: undefined symbol: __glXLastContext (EE) Failed to load /usr/X11R6/lib/modules-dri-trunk/extensions/libGLcore.so (II) UnloadModule: GLcore (EE) Failed to load module GLcore (loader failed, 7) -- (II) Module dri: vendor=X.Org Foundation compiled for 6.8.1.99, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.2 (II) Loading sub module drm (II) LoadModule: drm (II) Loading /usr/X11R6/lib/modules-dri-trunk/linux/libdrm.so (II) Module drm: vendor=X.Org Foundation compiled for 6.8.1.99, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.2 (II) Loading extension XFree86-DRI (II) LoadModule: extmod (II) Loading /usr/X11R6/lib/modules-dri-trunk/extensions/libextmod.so (II) Module extmod: vendor=X.Org Foundation compiled for 6.8.1.99, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.2 (II) Loading extension SHAPE (II) Loading extension MIT-SUNDRY-NONSTANDARD (II) Loading extension BIG-REQUESTS (II) Loading extension SYNC (II) Loading extension MIT-SCREEN-SAVER -- (**) Generic Mouse: Protocol: Microsoft (**) Option SendCoreEvents true (**) Generic Mouse: always reports core events (**) Option Device /dev/ttyS0 (**) Option BaudRate 1200 (**) Option StopBits 1 (**) Option DataBits 7 (**) Option Parity None (**) Option Vmin 1 (**) Option Vtime 0 (**) Option FlowControl None (**) Option Emulate3Buttons true (**) Generic Mouse: Emulate3Buttons, Emulate3Timeout: 50 (**) Option ZAxisMapping 4 5 (**) Generic Mouse: ZAxisMapping: buttons 4 and 5 (**) Generic Mouse: Buttons: 5 (**) Generic Mouse: BaudRate: 1200 (II) XINPUT: Adding extended input device Generic Mouse (type: MOUSE) (II) XINPUT: Adding extended input device Configured Mouse (type: MOUSE) (II) XINPUT: Adding extended input device Generic Keyboard (type: KEYBOARD) (EE) Couldn't load XKB keymap, falling back to pre-XKB keymap I have gone through the entire log. Aside from the errors in loading libGLcore.so, there's also a couple of lines about success in loading libGLcore.so (as a sub module). =/ (II) LoadModule: GLcore (II) Loading /usr/X11R6/lib/modules-dri-trunk/extensions/libGLcore.so dlopen: /usr/X11R6/lib/modules-dri-trunk/extensions/libGLcore.so: undefined symbol: __glXLastContext (EE) Failed to load /usr/X11R6/lib/modules-dri-trunk/extensions/libGLcore.so (II) UnloadModule: GLcore (EE) Failed to load module GLcore (loader failed, 7) ... ... ... (II) LoadModule: glx (II) Loading /usr/X11R6/lib/modules-dri-trunk/extensions/libglx.so (II) Module glx: vendor=X.Org Foundation compiled for 6.8.1.99, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.2 (II) Loading sub module GLcore (II) LoadModule: GLcore (II) Loading /usr/X11R6/lib/modules-dri-trunk/extensions/libGLcore.so (II) Module GLcore: vendor=X.Org Foundation compiled for 6.8.1.99, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.2 I guess the problem isn't from libGLcore.so itself. Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Wiki Documentation
Has anyone thought about having a wiki documentation system for FlightGear? One of the real weaknesses of flightgear is that there is little documentation. I am sure that if it were easy for the community to edit the documentation it would improve vastly. This could save so much of people's time and effort that is currently used to help people fix the same problems over and over. Cheers, Mostyn ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: AI weirdness
On Monday 02 May 2005 21:43, Frederic Bouvier wrote: Let me rephrase Melchior's suggestion : iterate on directories with plib's ulOpenDir and ulReadDir functions, possibly being recursive in the tree, and check if the name of the reported files are an existing ICAO code against the database already loaded in memory. Examples of directory scan are in fgadmin and in fgrun. -Fred Okay, that would be fairly easy to do. I'll have a look. Cheers, Durk ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d