Is the following enough information or should I post the big dump file?[dave@localhost bin]$ ./fgfslibGL warning: 3D driver claims to not support visual 0x24libGL warning: 3D driver claims to not support visual 0x28libGL warning: 3D driver claims to not support visual 0x2clibGL warning: 3D driver claims to not support visual 0x30opening file: /usr/share/FlightGear/data/Navaids/carrier_nav.dat/usr/share/FlightGear/data/Navaids/TACAN_freq.datRenderTexture Error: Couldn't find a suitable pixel format../fgfs: symbol lookup error: ./fgfs: undefined symbol: alutLoadWAVFile[dave@localhost bin]$Thanks in advance for your help.Dave

Isolated the problem -- the alutLoadWAVEFile instruction is broken. Evidently FGFS has used broken code in the way it points to wav files. There is a lot of discussion on other gamer sites about this glitch. Evidently the alut and open sound systems are both broken in the Linux FGFS which causes a premature exit on error condition.Have to step back from the game for now and wait until the programmers fix it.Cheers!Dave

>Isolated the problem -- the alutLoadWAVEFile instruction is>broken. Evidently FGFS has used broken code in the way it>points to wav files. There is a lot of discussion on other>gamer sites about this glitch. Evidently the alut and open>sound systems are both broken in the Linux FGFS which causes a>premature exit on error condition.>>Have to step back from the game for now and wait until the>programmers fix it.There are not only OpenAL related warning messages in your console log but also OpenGL related ones. So, I don't think your analysis of the problem is very comprehensive or even particularly accurate, if you are truly interested in running FlightGear, you might want to try giving compiling FlightGear a shot. It's really not all that complicated, particularly given you already seem to have a Linux background. As long as your hardware is up to the task of running FlightGear there should be hardly any reason for you not to be able to run FlightGear. Simply get the latest:PLIBOpenALSimGearFlightGearand depending on the performance of your machine you should be done within 1-6 hrs, finally getting a binary specifically built for your very system.Also, please note that it is usually recommended to provide a maximum amount of possibly relevant framework information if you are asking for help, none of us knows as much about your system as you do. So, you are definitely improving your chances of actually getting a reply from any of us if you provide all of the information we usually ask for right from the beginning (Full Platform,Hardware,OS,drivers,Software specs,FG version,environment variables,runtime settings etc). For many people it's getting kinda old to keep asking for the "obvious", simply because it would only be a matter of minutes to check out some of the other threads in order to learn that this is exactly the sort of information we require to come up with a reliable diagnosis of your problem. Likewise, many of the other threads are also tremendously helpful resources when it comes to fixing FG related issues, for example if you had searched the forum prior to posting to the forum you might have found various discussions providing insight about how to debug FlightGear.

Feeling a wee bit Pontifical are we?Goodbye.Dave

>Feeling a wee bit Pontifical are we?nope, honestly not at all.I certainly didn't mean to offend you, sorry if that's been the case.I was merely trying to make three things clear:1) I am pretty convinced that your findings were neither comprehensive nor accurate, thus you came up with the -flawed- conclusion that FlightGear would generally not be "playable" for you (at the moment).2) I don't see any reason that FlightGear should not work for you, provided that your system's specs (which, by the way you still didn't provide us with) fulfill FlightGear's requirements and you are able to follow the docs as well as some simple directions.3) People who are replying on forums such as these are usually doing this voluntarily in their spare time, thus you can heavily increase your odds of actually getting helpful replies if you reduce the amount of time that is indeed required to help you.Out of personal experience I can tell you that it can often be pretty straight forward to fix a FG related problem, at least as long as the problem itself and its scope are well described. Of course, this is made harder due to the nature of the internet and these forums.On the other hand, there have been some pretty good bug reports here where the causes were easy to narrow down due to the amount of information that was provided.However, if on the other hand people have to explicitly ask for things that should generally be included in any decent bug report, such as for example:HARDWARE, OS/KERNEL, SERVICEPACKS, SOFTWARE, DRIVERS,VERSIONS OF RELATED LIBRARIES), FG VERSION, RELATED ENVIRONMENT VARIABLES, STARTUP PARAMETERS,RUNTIME SETTINGS, CONSOLE WARNINGS/ERRORS etc.then the pool of potential supporters becomes significantly smaller-simply because not everybody is willing to take up this Q&A battle. Of the aforementioned items you only provided us with information about console warnings and errors.Which in itself is often good and helpful information, however on the other hand you didn't tell us anything about the version of FlightGear you are trying to run, the way you installed it (compiled vs. binary package), your hardware specs (in particular: OpenGL related stuff like card/driver version), the version of OpenAL libraries installed on your system etc.Thus, anybody who truly wanted to help you would have to either guess lots of things or simply ask each question specifically. Thus, when I read your posting recently, I simply didn't bother to get back to it because it seemed hardly "complete".Which makes it unnecessarily complex to help in general, and would also reduce the amount of time we can spend helping others.You know, honstely often times we may be asking for way too much information or for information that simply turns out to be of hardly any relevance, however on the other hand while we can simply filter out irrelevant information, we cannot easily fill in any gaps.So, I apologize if you felt offended by my previous reply, that was certainly not my intention. If you are interested in getting FlightGear to work for you, I do encourage you to provide the information I asked you for so that we can actually begin troubleshooting the problem rather than making absolutely uninformed guesses as to what may be the cause of your problem due to the lack of information.As an aside, please note that these forums are not the official means of providing support for FlightGear, in fact the majority of FlightGear users and developers prefers to use the mailing lists mentioned at http://www.flightgear.org/mail.html So, whenever you truly need competent support you should definitely use the mailing lists as they can be considered to be the ultimate resource for any FG related issues.

The beginning of my original post:Is the following enough information or should I post the bigdump file?Here is some log output; your advice is appreciated:[root@localhost flight]# rpm -ivh --force openal*warning: openal-0.0.9-0.4.20060204cvs.fc3.i386.rpm: V3 DSA signature: NOKEY, key ID 1ac70ce6Preparing... ########################################### [100%] 1:openal ########################################### [100%][root@localhost flight]# rpm -ivh --force free*Preparing... ########################################### [100%] 1:freealut ########################################## [100%][root@localhost flight]# rpm -ivh --force Flight*error: Failed dependencies: openal >= 20050209 is needed by FlightGear-0.9.9-0.FC.i386[root@localhost bin]# ./fgfs -vlibGL warning: 3D driver claims to not support visual 0x24libGL warning: 3D driver claims to not support visual 0x28libGL warning: 3D driver claims to not support visual 0x2clibGL warning: 3D driver claims to not support visual 0x30opening file: /usr/share/FlightGear/data/Navaids/carrier_nav.dat/usr/share/FlightGear/data/Navaids/TACAN_freq.datRenderTexture Error: Couldn't find a suitable pixel format../fgfs: symbol lookup error: ./fgfs: undefined symbol: alutLoadWAVFile[root@localhost bin]Here is my system:uname -a & cat /proc/cpuinfo & cat /proc/interrupts & cat/proc/pci[1] 15645[2] 15646[3] 15647Linux misterfixit.misterfixit 2.6.12-1.1372_FC3 #1 Fri Jul 15 00:59:10 EDT 2005 i686 athlon i386 GNU/Linuxprocessor : 0vendor_id : AuthenticAMDcpu family : 6model : 3model name : AMD Duronstepping : 1cpu MHz : 768.967cache size : 64 KBfdiv_bug : nohlt_bug : nof00f_bug : nocoma_bug : nofpu : yesfpu_exception : yescpuid level : 1wp : yesflags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 mmx fxsr syscall mmxext 3dnowext 3dnowbogomips : 1511.42 CPU0 0: 63102843 XT-PIC timer 1: 15275 XT-PIC i8042 2: 0 XT-PIC cascade 8: 1 XT-PIC rtc 9: 64 XT-PIC ehci_hcd:usb1 10: 98 XT-PIC uhci_hcd:usb3 11: 11212632 XT-PIC eth0, uhci_hcd:usb2, r128@pci:0000:01:00.0 12: 77084 XT-PIC ohci1394, VIA8233, uhci_hcd:usb4 14: 606894 XT-PIC ide0 15: 2708044 XT-PIC ide1NMI: 0ERR: 0root@localhost flight]# rpm -ivh --force --verbose Flight*D: ============== FlightGear-0.9.9-0.FC.i386.rpmD: Expected size: 98737924 = lead(96)+sigs(180)+pad(4)+data(98737644)D: Actual size: 98737924D: FlightGear-0.9.9-0.FC.i386.rpm: MD5 digest: OK (98eb31c001cfcc5c9245bfabac5752a1)D: added binary package [0]D: found 0 source and 1 binary packagesD: opening db environment /var/lib/rpm/Packages joinenvD: opening db index /var/lib/rpm/Packages rdonly mode=0x0D: locked db index /var/lib/rpm/PackagesD: ========== +++ FlightGear-0.9.9-0.FC i386/linux 0x1D: opening db index /var/lib/rpm/Depends create mode=0x0D: opening db index /var/lib/rpm/Providename rdonly mode=0x0D: opening db index /var/lib/rpm/Pubkeys rdonly mode=0x0D: read h# 853 Header sanity check: OKD: ========== DSA pubkey id b44269d04f2a6fd2D: read h# 1242 Header V3 DSA signature: OK, key ID 4f2a6fd2D: Requires: libGL.so.1 YES (db provides)D: read h# 1244 Header V3 DSA signature: OK, key ID 4f2a6fd2D: Requires: libGLU.so.1 YES (db provides)D: read h# 1240 Header V3 DSA signature: OK, key ID 4f2a6fd2D: Requires: libICE.so.6 YES (db provides)D: Requires: libSM.so.6 YES (db provides)D: Requires: libX11.so.6 YES (db provides)D: Requires: libXext.so.6 YES (db provides)D: Requires: libXi.so.6 YES (db provides)D: Requires: libXmu.so.6 YES (db provides)D: Requires: libXt.so.6 YES (db provides)D: read h# 1322 Header V3 DSA signature: OK, key ID 4f2a6fd2D: Requires: libc.so.6 YES (db provides)D: Requires: libc.so.6(GLIBC_2.0) YES (db provides)D: Requires: libc.so.6(GLIBC_2.1) YES (db provides)D: Requires: libc.so.6(GLIBC_2.1.3) YES (db provides)D: Requires: libdl.so.2 YES (db provides)D: Requires: libdl.so.2(GLIBC_2.0) YES (db provides)D: Requires: libdl.so.2(GLIBC_2.1) YES (db provides)D: read h# 854 Header V3 DSA signature: OK, key ID 4f2a6fd2D: Requires: libgcc_s.so.1 YES (db provides)D: Requires: libgcc_s.so.1(GCC_3.0) YES (db provides)D: read h# 475 Header V3 DSA signature: OK, key ID 4f2a6fd2D: Requires: libglut.so.3 YES (db provides)D: Requires: libm.so.6 YES (db provides)D: Requires: libm.so.6(GLIBC_2.0) YES (db provides)D: read h# 1396 Header V3 DSA signature: NOKEY, key ID 1ac70ce6D: Requires: libopenal.so.0 YES (db provides)D: Requires: libpthread.so.0 YES (db provides)D: Requires: libpthread.so.0(GLIBC_2.0) YES (db provides)D: Requires: libpthread.so.0(GLIBC_2.1) YES (db provides)D: Requires: libpthread.so.0(GLIBC_2.3.2) YES (db provides)D: ========== DSA pubkey id b44269d04f2a6fd2D: read h# 393 Header V3 DSA signature: OK, key ID 4f2a6fd2D: Requires: libstdc++.so.5 YES (db provides)D: Requires: libstdc++.so.5(CXXABI_1.2) YES (db provides)D: Requires: libstdc++.so.5(GLIBCPP_3.2) YES (db provides)D: read h# 861 Header V3 DSA signature: OK, key ID 4f2a6fd2D: Requires: libz.so.1 YES (db provides)D: read h# 1396 Header V3 DSA signature: NOKEY, key ID 1ac70ce6D: Requires: openal >= 20050209 NOD: package FlightGear-0.9.9-0.FC.i386 has unsatisfied Requires: openal >= 20050209D: Requires: rpmlib(CompressedFileNames) <= 3.0.4-1 YES (rpmlib provides)D: Requires: rpmlib(PayloadFilesHavePrefix) <= 4.0-1 YES (rpmlib provides)D: opening db index /var/lib/rpm/Conflictname rdonly mode=0x0D: closed db index /var/lib/rpm/PubkeysD: closed db index /var/lib/rpm/DependsD: closed db index /var/lib/rpm/ConflictnameD: closed db index /var/lib/rpm/ProvidenameD: closed db index /var/lib/rpm/PackagesD: closed db environment /var/lib/rpm/Packageserror: Failed dependencies: openal >= 20050209 is needed by FlightGear-0.9.9-0.FC.i386D: ========== recording tsort relationsD: ========== tsorting packages (order, #predecessors, #succesors, tree, depth)D: 0 0 0 0 0 +FlightGear-0.9.9-0.FCNeed anything else?TIA

Well, as I assumed there seem to be various things related to unresolved dependencies, so either you get to satisfy these dependencies, or really do what I suggested previously: compile everything from source code, that way we should at least get rid of all dependency related issues, so that we finally get past the current stage. I think compiling is even somewhere documented on the wiki?Apart from that, you still don't seem to have provided any details concerning your video setup (graphics card, driver version, openGL support available:glxinfo output?), however there are various warnings related to unavailable OpenGL extensions. So, the next step should be to try running the freshly compiled FlightGear binary and post any warnings or errors you may encounter and if required update your graphic card's OpenGL drivers.Also, recently I compiled a list of data that is usually useful when trying to fix such issues, you may find it helpful:http://www.seedwiki.com/wiki/flight_gear/h...cfm?wpid=247004