[Flightgear-users] problems finding correct OpenGL lib with Slackware 0.9.9 and Nvidia (solved !)
Hi, When starting Flightgear from the 0.9.9 package prepared by Jon Stockill the startup logo looked fine until the point where the actually strip and plane should showup. There FG just quitted with the following error message : /local/FlightGear/FlightGear-0.9.9/share/FlightGear/Navaids/TACAN_freq.dat X Error of failed request: BadLength (poly request too large or internal Xlib length error) Major opcode of failed request: 144 (GLX) Minor opcode of failed request: 29 () Serial number of failed request: 837 Current serial number in output stream: 837 I spent 1/2 day searching and even compiled my own version from scratch (with exactly the same problem !) before I had it solved, so thought I'd better tell other people as well :-) What goes wrong ? Simply that FG must be loading the wrong libGL library ! Check with ldd fgfs which libraries it uses. If you use the Nvidia driver but fgfs uses /usr/X11R6/lib/libGL.so.1 instead of /usr/lib/libGL.so.1 this is certainly the culprit. Nvidia installs it's libGL.so for Nvidia cards in /usr/lib while the original X11R6 is in /usr/X11R6/lib. Normally the latter is removed by the Nvidia installer, but if you install e.g. Dropline Gnome new X libraries are installed and one of them is libGL. Simply remove this library in /usr/X11R6/lib or alternatively set your librarypath to use /usr/lib BEFORE /usr/X11R6/lib and everything works fine : export LD_LIBRARY_PATH=/usr/lib:/opt/openal/lib -- Kees Lemmens, TU Delft, Netherlands. Ceterum Censeo Microsoftem esse Delendam ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Sound on Linux systems
Hi, These problems are often casued by simple soundcards (often on the motherboard) that cannot multiplex sound (play more than one sound stream at the same time). If one application uses sound, other sound requests are blocked until the first one released the sound system. This is solved on many systems (including Linux and Windows) by using a software multiplexer like ESD (Gnome) or Arts (KDE). Sound streams are then not send directly to the soundcard, but to this deamon instead. That works fine, but has one drawback : the ARTS or ESD daemons claim the soundcard PERMANENTLY , thereby frustrating apps that want to address the soundcard directly and bypass artsd. 5 solutions : 1) Disable the artsd or esd daemons (KDE/Gnome config menu´s) and avoid other using sound apps during FG (like xmms). 2) Set the timeout for the artsd daemon to a low value (e.g. 5 sec.) and avoid other using sound apps during FG (like xmms). 3) Let FG run through artsd instead of directly to the soundcard (e.g. by using artsdsp fgfs . (Question : I am not sure if that is possible with OpenAL , can anyone comment on this ?) 4) Buy a better soundcard that can multiplex in hardware (like the SB Live). 5) Several simple soundcards have 2 dsp devices : simply let artsd talk to the second one instead of the first one (/dev/dsp1 or similar). This leaves the first dsp free for applications that want to address the soundcard directly. Regards, Kees Lemmens. Delft. ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Scrolling views crashes plane
Hi, This sounds to me much more like a problem of your own hardware and/or software than a FlightGear problem. Why don't you try a slightly more robust operating system than that crappy Windows ME ? (XP, Linux) It may also be your videodriver (is it a recent one ?) and/or a problem of the videocard. Kees On Wednesday 16 November 2005 07:18, Dene Maxwell wrote: After about an hour of flying, scrolling through the views and restoring from the tower view to the chase view causes the aircraft(on auto-pilot) to loose control and crash.. Under Win 98Me with all other precesses except systray and explorer shut down Pentium 4, 1.8GHz, 256kbyte Ram, 32 NeVidia Graphics Card No error messages in the fgfs window. any ideas? Dene -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.13.0/167 - Release Date: 11/11/05 ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Scrolling views crashes plane
On Wednesday 16 November 2005 14:08, [EMAIL PROTECTED] wrote: On Wednesday 16 November 2005 07:18, Dene Maxwell wrote: After about an hour of flying, scrolling through the views and restoring from the tower view to the chase view causes the aircraft(on auto-pilot) to loose control and crash.. Under Win 98Me with all other precesses except systray and explorer shut down Pentium 4, 1.8GHz, 256kbyte Ram, 32 NeVidia Graphics Card No error messages in the fgfs window. any ideas? This sounds to me much more like a problem of your own hardware and/or software than a FlightGear problem. Why don't you try a slightly more robust operating system than that crappy Windows ME ? (XP, Linux) It may also be your videodriver (is it a recent one ?) and/or a problem of the videocard. Just out of curiosity, can you elaborate on this? How did you decide that it looked like a hardware problem or an OS/video driver problem? A long experience with both many oses and with flightgear :-) -c ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Scrolling views crashes plane
Hi, Just to make sure : do you mean that flightgear crashed itself or that simply the airplane INSIDE flightgear crashed ? In the last case I misinterpreted you're question and as such my answer is rather useless ;-) Kees On Wednesday 16 November 2005 07:18, Dene Maxwell wrote: After about an hour of flying, scrolling through the views and restoring from the tower view to the chase view causes the aircraft(on auto-pilot) to loose control and crash.. Under Win 98Me with all other precesses except systray and explorer shut down Pentium 4, 1.8GHz, 256kbyte Ram, 32 NeVidia Graphics Card No error messages in the fgfs window. any ideas? Dene -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.362 / Virus Database: 267.13.0/167 - Release Date: 11/11/05 ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Problem running fgfs (0.9.8)
Hi Shelton, It doesn't seem to come easy in your case ;-) Anyway : just tell flightgear wehere to FIND the openal library if it isn't in the standard libpaths and everything will automagically work : export LD_LIBRARY_PATH=/usr/local/whatever/openal/ start flightgear You may always check with ldd if the library can be found after doing this. Example : BEFORE setting the library path : prompt % ldd /local/Games/FlightGear/FlightGear-0.9.8/bin/fgfs linux-gate.so.1 = (0xe000) libpthread.so.0 = /lib/tls/libpthread.so.0 (0xb7f72000) libz.so.1 = /usr/lib/libz.so.1 (0xb7f5f000) libglut.so.3 = /usr/X11R6/lib/libglut.so.3 (0xb7f29000) libGLU.so.1 = /usr/X11R6/lib/libGLU.so.1 (0xb7eb) libGL.so.1 = /usr/lib/libGL.so.1 (0xb7e31000) libXmu.so.6 = /usr/X11R6/lib/libXmu.so.6 (0xb7e1b000) libXt.so.6 = /usr/X11R6/lib/libXt.so.6 (0xb7dca000) libSM.so.6 = /usr/X11R6/lib/libSM.so.6 (0xb7dc1000) libICE.so.6 = /usr/X11R6/lib/libICE.so.6 (0xb7da9000) libXi.so.6 = /usr/X11R6/lib/libXi.so.6 (0xb7da1000) libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0xb7d93000) libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0xb7cc9000) libdl.so.2 = /lib/tls/libdl.so.2 (0xb7cc5000) libopenal.so.0 = not found libm.so.6 = /lib/tls/libm.so.6 (0xb7ca1000) libstdc++.so.5 = /usr/lib/libstdc++.so.5 (0xb7be9000) libgcc_s.so.1 = /usr/lib/libgcc_s.so.1 (0xb7be) libc.so.6 = /lib/tls/libc.so.6 (0xb7ac4000) /lib/ld-linux.so.2 (0xb7f9e000) libGLcore.so.1 = /usr/lib/libGLcore.so.1 (0xb735a000) libnvidia-tls.so.1 = /usr/lib/tls/libnvidia-tls.so.1 (0xb7358000) And AFTER doing so : prompt % export LD_LIBRARY_PATH=/local/Games/FlightGear/FlightGear-0.9.8/lib/ prompt % ldd /local/Games/FlightGear/FlightGear-0.9.8/bin/fgfs linux-gate.so.1 = (0xe000) libpthread.so.0 = /lib/tls/libpthread.so.0 (0xb7f17000) libz.so.1 = /usr/lib/libz.so.1 (0xb7f04000) libglut.so.3 = /usr/X11R6/lib/libglut.so.3 (0xb7ece000) libGLU.so.1 = /usr/X11R6/lib/libGLU.so.1 (0xb7e55000) libGL.so.1 = /usr/lib/libGL.so.1 (0xb7dd6000) libXmu.so.6 = /usr/X11R6/lib/libXmu.so.6 (0xb7dc) libXt.so.6 = /usr/X11R6/lib/libXt.so.6 (0xb7d6f000) libSM.so.6 = /usr/X11R6/lib/libSM.so.6 (0xb7d66000) libICE.so.6 = /usr/X11R6/lib/libICE.so.6 (0xb7d4e000) libXi.so.6 = /usr/X11R6/lib/libXi.so.6 (0xb7d46000) libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0xb7d38000) libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0xb7c6e000) libdl.so.2 = /lib/tls/libdl.so.2 (0xb7c6a000) libopenal.so.0 = /local/Games/FlightGear/FlightGear-0.9.8/lib/libopenal.so.0 (0xb7bdf000) libm.so.6 = /lib/tls/libm.so.6 (0xb7bbc000) libstdc++.so.5 = /usr/lib/libstdc++.so.5 (0xb7b04000) libgcc_s.so.1 = /usr/lib/libgcc_s.so.1 (0xb7afb000) libc.so.6 = /lib/tls/libc.so.6 (0xb79df000) /lib/ld-linux.so.2 (0xb7f43000) libGLcore.so.1 = /usr/lib/libGLcore.so.1 (0xb7275000) libnvidia-tls.so.1 = /usr/lib/tls/libnvidia-tls.so.1 (0xb7273000) Kees PS : isn't it a good idea to ask permission to integrate openal into flightgear and store the lib in the distro tree (as in the example above) ? It may save a lot of novices a LOT of time :-) On Tuesday 01 November 2005 11:00, Shelton D'Cruz wrote: Ok thanks Erik I will look into it further, It says I have OpenAL installed but obviously not. Thanks again Shelton. Shelton D'Cruz wrote: Hi Erik Well 0.9.4 works fine - does it not use OpenAL ?? Nope, it's used plib's SL library. Erik ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Problem running fgfs (0.9.8)
Hi Shelton, Glad to hear you made it thisfar ! But ... /usr/lib should be in the standard searchpath on every Linux system. If it isn't there may be something wrong with the setup. Did you install openal and then rerun ldconfig and or reboot afterwards ? IF not, then you just have to reboot. If you did you have to check your installation (notably /etc/ld.so.conf). Bye, Kees PS: did you already try the Bo 105 Eurocopter ? Fascinating ! On Tuesday 01 November 2005 11:39, you wrote: Kees You are brilliant!!! all i had to do was export the LD_LIBRARY_PATH to /usr/lib and I have FG again!! Thank you very much and Erik too!! Regards Shelton. PS be ready for some more (silly) questions ;) Hi Shelton, It doesn't seem to come easy in your case ;-) Anyway : just tell flightgear wehere to FIND the openal library if it isn't in the standard libpaths and everything will automagically work : export LD_LIBRARY_PATH=/usr/local/whatever/openal/ start flightgear You may always check with ldd if the library can be found after doing this. Example : BEFORE setting the library path : prompt % ldd /local/Games/FlightGear/FlightGear-0.9.8/bin/fgfs linux-gate.so.1 = (0xe000) libpthread.so.0 = /lib/tls/libpthread.so.0 (0xb7f72000) libz.so.1 = /usr/lib/libz.so.1 (0xb7f5f000) libglut.so.3 = /usr/X11R6/lib/libglut.so.3 (0xb7f29000) libGLU.so.1 = /usr/X11R6/lib/libGLU.so.1 (0xb7eb) libGL.so.1 = /usr/lib/libGL.so.1 (0xb7e31000) libXmu.so.6 = /usr/X11R6/lib/libXmu.so.6 (0xb7e1b000) libXt.so.6 = /usr/X11R6/lib/libXt.so.6 (0xb7dca000) libSM.so.6 = /usr/X11R6/lib/libSM.so.6 (0xb7dc1000) libICE.so.6 = /usr/X11R6/lib/libICE.so.6 (0xb7da9000) libXi.so.6 = /usr/X11R6/lib/libXi.so.6 (0xb7da1000) libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0xb7d93000) libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0xb7cc9000) libdl.so.2 = /lib/tls/libdl.so.2 (0xb7cc5000) libopenal.so.0 = not found libm.so.6 = /lib/tls/libm.so.6 (0xb7ca1000) libstdc++.so.5 = /usr/lib/libstdc++.so.5 (0xb7be9000) libgcc_s.so.1 = /usr/lib/libgcc_s.so.1 (0xb7be) libc.so.6 = /lib/tls/libc.so.6 (0xb7ac4000) /lib/ld-linux.so.2 (0xb7f9e000) libGLcore.so.1 = /usr/lib/libGLcore.so.1 (0xb735a000) libnvidia-tls.so.1 = /usr/lib/tls/libnvidia-tls.so.1 (0xb7358000) And AFTER doing so : prompt % export LD_LIBRARY_PATH=/local/Games/FlightGear/FlightGear-0.9.8/lib/ prompt % ldd /local/Games/FlightGear/FlightGear-0.9.8/bin/fgfs linux-gate.so.1 = (0xe000) libpthread.so.0 = /lib/tls/libpthread.so.0 (0xb7f17000) libz.so.1 = /usr/lib/libz.so.1 (0xb7f04000) libglut.so.3 = /usr/X11R6/lib/libglut.so.3 (0xb7ece000) libGLU.so.1 = /usr/X11R6/lib/libGLU.so.1 (0xb7e55000) libGL.so.1 = /usr/lib/libGL.so.1 (0xb7dd6000) libXmu.so.6 = /usr/X11R6/lib/libXmu.so.6 (0xb7dc) libXt.so.6 = /usr/X11R6/lib/libXt.so.6 (0xb7d6f000) libSM.so.6 = /usr/X11R6/lib/libSM.so.6 (0xb7d66000) libICE.so.6 = /usr/X11R6/lib/libICE.so.6 (0xb7d4e000) libXi.so.6 = /usr/X11R6/lib/libXi.so.6 (0xb7d46000) libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0xb7d38000) libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0xb7c6e000) libdl.so.2 = /lib/tls/libdl.so.2 (0xb7c6a000) libopenal.so.0 = /local/Games/FlightGear/FlightGear-0.9.8/lib/libopenal.so.0 (0xb7bdf000) libm.so.6 = /lib/tls/libm.so.6 (0xb7bbc000) libstdc++.so.5 = /usr/lib/libstdc++.so.5 (0xb7b04000) libgcc_s.so.1 = /usr/lib/libgcc_s.so.1 (0xb7afb000) libc.so.6 = /lib/tls/libc.so.6 (0xb79df000) /lib/ld-linux.so.2 (0xb7f43000) libGLcore.so.1 = /usr/lib/libGLcore.so.1 (0xb7275000) libnvidia-tls.so.1 = /usr/lib/tls/libnvidia-tls.so.1 (0xb7273000) Kees PS : isn't it a good idea to ask permission to integrate openal into flightgear and store the lib in the distro tree (as in the example above) ? It may save a lot of novices a LOT of time :-) On Tuesday 01 November 2005 11:00, Shelton D'Cruz wrote: Ok thanks Erik I will look into it further, It says I have OpenAL installed but obviously not. Thanks again Shelton. Shelton D'Cruz wrote: Hi Erik Well 0.9.4 works fine - does it not use OpenAL ?? Nope, it's used plib's SL library. Erik ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-users mailing list Flightgear-users@flightgear.org
Re: [Flightgear-users] FlightGearTools Version 1.0 now available
Hi, The whole problem is that MS-Windows users are quite prepared to use the better products from the Open Source world, but are at the same time simply too stupid and/or too lazy to work on those projects themselves ;-) If they think FlightGear is worthy of MSWindows (I wouldn't be proud of it ...) they should simply start contributing to it . There is no such thing as a free meal, albeit it may not be money you'll have to invest this time ;-) Bye, Kees Lemmens PS : Eric Brasseur , thanks for your excellent contribution (the tutorial) ! On Monday 03 October 2005 18:55, Gerard ROBIN wrote: Le lundi 03 octobre 2005 à 18:46 +0200, Arnt Karlsen a écrit : On Sun, 02 Oct 2005 18:28:25 -0400, Ed wrote in message [EMAIL PROTECTED]: If Flightgear plans to draw a large audience ..precisely. If. ;o) (and I think it is worthy of it), the Flightgear community HAS TO REALIZE that they MUST appeal to the MS-Windows community. That's just ..bull. You are welcome to compare the merits of what you have experienced with Wintendo, with what you learn with FlightGear. ;o) the facts ... it's not an opinion, it's not an us versus them scenario. It's just what it is. There's no denying it. ..this sounds more like some MSFS folks bracing themselves for the Horrors of Capitalism, like in Competition on Tech etc Merits. ;o) Bring it on! ;o) Your remarks sound to me like a Sibelius Symphony :-)) ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-users] slow framerates with Nvidia PIC Express under Linux solved !
Hi, Just in case it helps someone else with the same problem : On my rather new PIV Linux system with V6600 PCI-Express Nvidia card and the NVIDIA-Linux-x86-1.0-7167 driver FlightGear slowed down to an unacceptable framerate ( 1fps) as soon as an airport became visible. Turning away from the airport would immediately restore the original , normal, framerate but it made of course landings impossible ;-) I tried everything, more simple rendering, lesser details and even went down to 640x480 but nothing solved the problem and so I didn't even use FlightGear on that system for some time. For the rest both card and Nvidia driver worked fine, also for more sophisticated 3D Linux games (as my son assured me ;-) But ... yesterday I installed the latest NVIDIA-7667 driver and now Flightgear works perfectly well on this system ! I even can use 1280x1024 and still have high framerates without any noticable hickups ! Thanks to NVIDIA for their fine Linux drivers : many other videocard vendors could learn a LOT from the way Nvidia supports Linux ! Nevertheless there still remains the question : why would the card with the old driver slowdown to a crawl if any airport was visible while other 3D apps wouldn't have any performance problems ? Could it have been something with the landing lights ? BTW: on AGP systems also the old 7167 driver worked fine and fast. Only PCI-Express cards had this problem (until yesterday ;-) Bye, Kees Lemmens. ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Re: Flightgear-users Digest, Vol 25, Issue 6
Hi, On Tuesday 10 May 2005 10:07, Erik Hofman wrote: ... In my install, I have most of the files and directories (airport, aircraft, etc) in /usr/local/FlightGear-0.9.8/share/FlightGear so I thought it is the fg-root; in fact, in this directory, there is also that version file that contains the version number of flightgear, Oh man, this really sounds like a mess. The normal behaviour is: main program:/usr/local/bin/fgfs data directory: /usr/local/shared/FlightGear/data I do not agree with Eriks remark that this sounds like a mess : it is a commonly used method to ensure that EVERYTHING that belongs to a certain packet ends up in the same tree without cluttering anything else and can thus be easily removed without having to rely on an UN-install script. It also makes it possible to install everything as a NON-root user by giving the directory away prior to running install. Everything that fails to install MUST be illegal then (e.g. /etc or /lib ) ;-) The tree I see above is simply the result of something like : ./configure --prefix=/usr/local/FlightGear-0.9.8 --with-plib=/opt/plib \ --with-simgear=/opt/simgear .. and there is nothing wrong with that IMO. Bye, Kees Lemmens. ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Re: Flightgear-users Digest, Vol 25, Issue 6
Hi, On Thursday 12 May 2005 10:00, Erik Hofman wrote: Kees Lemmens wrote: Hi, On Tuesday 10 May 2005 10:07, Erik Hofman wrote: ... In my install, I have most of the files and directories (airport, aircraft, etc) in /usr/local/FlightGear-0.9.8/share/FlightGear so I thought it is the fg-root; in fact, in this directory, there is also that version file that contains the version number of flightgear, Oh man, this really sounds like a mess. The normal behaviour is: main program:/usr/local/bin/fgfs data directory: /usr/local/shared/FlightGear/data I do not agree with Eriks remark that this sounds like a mess : it is a commonly used method to ensure that EVERYTHING that belongs to a certain packet ends up in the same tree without cluttering anything else and can thus be easily removed without having to rely on an UN-install script. That's why we have a data directory, the tree would like something like this then: /opt/FlightGear /opt/FlightGear/bin /opt/FlightGear/sbin /opt/FlightGear/data /opt/FlightGear/include If you run with --prefix=/opt/FlightGear WITHOUT specifying anything else you'll end up exactly with what is described by the first writer and not with what you show above. Bye, Kees ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Re: version 0.9.8
Hi, I'd like to point out I have no objection to feeding families : we also happily use Maple (another commercial product by Waterloo) for instance. The problem is that Mathworks - in contrast with Waterloo - charges excessive prices that are in no relation to the quality of their product, simply because they have more or less a monopoly in their field. My idea is that we shouldn't contribute to make a greedy monopolist even richer : feeding your family doesn't necessarily mean that every child needs 2 Rolls Royces and a private jet ;-) -- Bye, Kees On Thursday 07 April 2005 16:14, Curtis L. Olson wrote: Kees Lemmens wrote: Hi, In our Math department we are rapidly replacing Matlab (commercial and VERY expensive !) with Octave (GNU Open Source). I wonder: wouldn't it be a better to make a connection to an Open Source project like Octave instead ? As someone else in this thread pointed out, the I/O capabilities in FlightGear are open for anyone to use. The work I did was simply to make the binary structure a bit more predictable in a cross platform environment. Does Octave have facilities for modeling flight dynamics or control systems? If so, I'm happy to work with an Octave developer to iron out any interfacing issues. Matlab is squeezing lot's of money out of people. They try to connect just about anything to their software so that users won't even consider using anything else (apart for those who pay the bills ;-). But I don't think that FlightGear - as an outstanding Open Source project - should co-operate in making this nasty company even more powerful ... Even Airbus seemed to be fed up with the Matlab tax-collectors and started developing their own Open Source Matlab-clone already some years ago : SciLab. BTW: this reminds me of another nasty company ;-) People are going to think what they are going to think about business, politics, etc. And this forum is the wrong place to discuss those issues. I have never looked at Octave, myself, but if it's a legitimate contender, and Octave users want to interface with FlightGear for some reason, then I'm happy to participate and make that as seamless and easy as possible. For what it's worth, many very big name companies use matlab/simulink. If these companies also start using FlightGear in conjunction with matlab as a visualization tool, then that increases FlightGear's market share in a very high profile segment of the market. That's good in and of itself, but if some of these companies (or developers that work at these companies) make changes/additions to FlightGear, that's a direct benefit to us. All of these forces feed each other, and hopefully build an upward spiral to make FlightGear better and better. Personally, I think open-source is a great and wonderful way to develop software ... it's not perfect, but it has many advantages. There's no question that this is the best approach for FlightGear. But at the same time, people need to feed thier families ... those of us who are cursed to live out their lives as software geeks (with few other marketable skills) shouldn't be prevented from making a living from our primary skill. I believe the world needs a combination of proprietary and open-source software. Both approaches have their own unique strengths and weaknesses. I think the optimal way to develop software is to find good ways to marry the two approaches. But like any marriage, one of the hardest things is to figure out the exact details (balance of power, division of labor, etc.) between the spouses. Some matches work better than others, but a good match is far more powerful and capable than individuals working in isolation. Regards, Curt. ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] FlightGear slow under Linux maximized window/ hardware upgrade recommendation
On Monday 14 March 2005 07:52, Andrzej Leszczynski wrote: Hi, 3. Last question, having in mind Linux as a target platform, ATI or Nvidia, which way to go? ATI is a disaster : horrible installation procedure. Nvidia on the other hand is superb : they did an excellent job and so their driver is probably the best (commercial) driver in the whole Linux world ;) (No, I'm not employed by Nvidia, just a happy user ;-) Kees Lemmens. ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Logitech USB 'Dual Action' Joypad under linux
Hi, I have the same joystick and getting it to work on 2.6 is trivial : just make sure the joydev and usbhid driver are loaded. Note that the driver name in 2.6 has changed from hid to usbhid. These are my relevant kernel mods (lsmod command) : Module Size Used by joydev 7616 0 usbhid 22304 0 uhci_hcd 27240 0 usbcore91028 7 usb_storage,audio,pwc,usbhid,uhci_hcd If you load the modules manually (eg using /etc/rc.d/rc.modules) you may use this to distinguish between 2.4 and 2.6 : test $( uname -r ) = 2.6.7 \ /sbin/modprobe usbhid|| \ /sbin/modprobe hid # 2.4 kernels (KL) Bye, Kees Lemmens On Wednesday 21 July 2004 00:56, Matthew Law wrote: I've just obtained a Logitech USB 'Dual Action' Joypad: http://www.logitech.com/index.cfm/products/details/GB/EN,CRID=11,CONT ENTID=6951 Has anyone managed to get this to work under linux kernel 2.6? I can see this when I tail /var/log/messages: Jul 20 23:52:49 turing usb 4-1: new low speed USB device using address 2 Jul 20 23:52:49 turing input: USB HID v1.10 Joystick [Logitech Logitech Dual Action] on usb-:00:10.2-1 but I'm having no luck getting it picked up as a joystick. Any ideas? All the best, Matthew. ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users
