[Flightgear-devel] Atlas release candidate
Hi all, I've put a release candidate of Atlas-0.3 up at: http://www.nottingham.ac.uk/~eazdluf/Atlas-0.3.0-rc1.tar.gz If a few folk could take the time to download this and try it out that would be great. Changes in the last year or so: * Now reads FG-0.9.8 airport and navaid formats * Atlas now displays ILS localisers * Map has an off-screen rendering option (--headless) to avoid image corruption due to overlaid windows and possibly allow maps greater than screen resolution depending on graphics hardware and drivers [X-Windows with fairly modern GLX only at present] * Map supports multiple scenery paths via FG_SCENERY or --fg-scenery= (only Map at present, not MapPS). * Atlas has --airport=ICAO startup option. * Bug fixes. Note that Atlas/Map is written by Per Liedman and others, not myself, but Per is unable to maintain it at the moment. Cheers - Dave This message has been checked for viruses but the contents of an attachment may still contain software viruses, which could damage your computer system: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Atlas release candidate
Hello David, I just compiled the new Atlas-version on my Linux-Box (Debian 3.1) and it works great. I have had no compile-problems and the maps are looking very nice. With the new version I am able to visit foreign airports without additionnel enroute and approach charts. Great. One question I have: With the left key,I am able to move around on the map. But then I destroy the flight track. Is it a bug or just a missing feature ? The only thing I am missing is the multiplayer capability. Last week I flew with my daughter, each on a Linux box. But it was very difficult to fly together. Then I wanted to use atlas to have an overview, where we are. But that doesn't work. I would be great to have to ports where atlas is listening. Kind regards Hans-Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Atlas release candidate
> Hi all, > I've put a release candidate of Atlas-0.3 up at: > http://www.nottingham.ac.uk/~eazdluf/Atlas-0.3.0-rc1.tar.gz Do you think there will be some Win32 binary too? It would be very nice :-) I don't know if it's even possible (I didn't look into the code in order to determine if libraries and the source itself is portable) but I really hope so. Roberto -- GMX im TV ... Die Gedanken sind frei ... Schon gesehen? Jetzt Spot online ansehen: http://www.gmx.net/de/go/tv-spot ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Atlas release candidate
On 28/01/2005 at 15:34 Roberto Inzerillo wrote: > >Do you think there will be some Win32 binary too? It would be very nice :-) > >I don't know if it's even possible (I didn't look into the code in order to >determine if libraries and the source itself is portable) but I really hope >so. > > A windows binary of the code a few weeks ago is here: ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/atlas-win32-20050112.zip courtesy of Fred Bouvier. Hopefully he will produce a release binary as well. Cheers - Dave This message has been checked for viruses but the contents of an attachment may still contain software viruses, which could damage your computer system: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Atlas release candidate
I have never tried to build Atlas before, but just tried with this release. I am working on a Mac and ./configure gives me the following errors: checking for pthread_exit in -lpthread... yes checking for glNewList in -lGLcore... no checking for glNewList in -lGL... yes checking for gluLookAt in -lGLU... yes checking for glutGetModifiers in -lglut... no checking for glutGameModeString in -lglut... no Unable to find the necessary OpenGL or GLUT libraries. See config.log for automated test details and results ... In order to build flightgear, a little while ago, it was necessary to make a few changes to the source code to get it to properly find GLUT stuff. But these changes are now all incorporated into FG. These locations are now all captured in simgear/compiler.h. In the time that I have been working with the code, no changes were required to the config stuff, only some of the paths in the source itself, now in compiler.h. The truth is that I have not done much with automake, so I am not really sure how to go about fixing this. But clearly something is different in how Atlas checks for GLUT versus how Simgear and FG do it, since they succeed just fine in finding and using that stuff. If you can point me in the right direction I can try to work with it some more. Atlas looks very useful. Thanks, -- Adam > From: David Luff <[EMAIL PROTECTED]> > Reply-To: FlightGear developers discussions > Date: Fri, 28 Jan 2005 13:16:28 + > To: <[EMAIL PROTECTED]> > Cc: > Subject: [Flightgear-devel] Atlas release candidate > > Hi all, > > I've put a release candidate of Atlas-0.3 up at: > > http://www.nottingham.ac.uk/~eazdluf/Atlas-0.3.0-rc1.tar.gz > > If a few folk could take the time to download this and try it out that > would be great. > > Changes in the last year or so: > > * Now reads FG-0.9.8 airport and navaid formats > > * Atlas now displays ILS localisers > > * Map has an off-screen rendering option (--headless) to avoid image > corruption due to overlaid windows and possibly allow maps greater than > screen resolution depending on graphics hardware and drivers [X-Windows > with fairly modern GLX only at present] > > * Map supports multiple scenery paths via FG_SCENERY or --fg-scenery= (only > Map at present, not MapPS). > > * Atlas has --airport=ICAO startup option. > > * Bug fixes. > > Note that Atlas/Map is written by Per Liedman and others, not myself, but > Per is unable to maintain it at the moment. > > Cheers - Dave > > > This message has been checked for viruses but the contents of an attachment > may still contain software viruses, which could damage your computer system: > you are advised to perform your own checks. Email communications with the > University of Nottingham may be monitored as permitted by UK legislation. > > > ___ > Flightgear-devel mailing list > Flightgear-devel@flightgear.org > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Atlas release candidate
David Luff wrote: Hi all, I've put a release candidate of Atlas-0.3 up at: http://www.nottingham.ac.uk/~eazdluf/Atlas-0.3.0-rc1.tar.gz If a few folk could take the time to download this and try it out that would be great. It builds ok on Slackware Linux 10.0, --headless seems to work ok with Map - I'm running it remotely at the moment. I'll test the Atlas app when I get home and it finishes building the maps. One thing it is showing up is quite a few missing scenery tiles in the 0.9.8 scenery. -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Atlas release candidate
On 28/01/2005 at 09:15 Adam Dershowitz wrote: >I have never tried to build Atlas before, but just tried with this >release. >I am working on a Mac and ./configure gives me the following errors: > >checking for pthread_exit in -lpthread... yes >checking for glNewList in -lGLcore... no >checking for glNewList in -lGL... yes >checking for gluLookAt in -lGLU... yes >checking for glutGetModifiers in -lglut... no >checking for glutGameModeString in -lglut... no > >Unable to find the necessary OpenGL or GLUT libraries. >See config.log for automated test details and results ... > >In order to build flightgear, a little while ago, it was necessary to make >a >few changes to the source code to get it to properly find GLUT stuff. But >these changes are now all incorporated into FG. These locations are now >all >captured in simgear/compiler.h. >In the time that I have been working with the code, no changes were >required >to the config stuff, only some of the paths in the source itself, now in >compiler.h. >The truth is that I have not done much with automake, so I am not really >sure how to go about fixing this. But clearly something is different in >how >Atlas checks for GLUT versus how Simgear and FG do it, since they succeed >just fine in finding and using that stuff. >If you can point me in the right direction I can try to work with it some >more. > Hi Adam, I'm afraid I don't use a Mac, and I'm not good with shell or configure scripts. If you want to have a try at fixing this, then configure.ac is the file you need to edit (try looking in FlightGear's configure.ac for inspiration), and you'll need to run ./autogen.sh before ./configure after making any changes to configure.ac. Unfortunately, the whole glut/gl section of the Atlas/FlightGear configure.ac files appears to be somewhat different - I don't think it's a matter of just dropping a mac test in from the FG one to the Atlas one. It really needs someone who know's what they're doing in this area to take a look at it. Cheers - Dave This message has been checked for viruses but the contents of an attachment may still contain software viruses, which could damage your computer system: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Atlas release candidate
On 28/01/2005 at 17:55 Jon Stockill wrote: >It builds ok on Slackware Linux 10.0, --headless seems to work ok with >Map - I'm running it remotely at the moment. I'll test the Atlas app >when I get home and it finishes building the maps. > >One thing it is showing up is quite a few missing scenery tiles in the >0.9.8 scenery. > Yes, there's one just north of Cambridge. I checked, and it is a definite missing scenery tile, not a Map/Atlas error. Cheers - Dave This message has been checked for viruses but the contents of an attachment may still contain software viruses, which could damage your computer system: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Atlas release candidate
Jon Stockill wrote: One thing it is showing up is quite a few missing scenery tiles in the 0.9.8 scenery. I noticed the missing tiles last week, but found they were introduced a while back, as they are also in scenery-0.9.5, (at least the 3 I managed to download last year) I've almost got all the 0.9.8 scenery for the 48 states, and have been making a list of the errors. Curt, as I'm not on the terragear list, and the errors seem to be in the source data, please make a note of these. Am I correct in observing this is something we can't fix without getting the source data repaired? unfinished squares, hole in Scenery Terrain w082n23 w083n23 w087n41 w081n48 w073n49 w074n49 w075n49 square elevation errors w083n30 large diamond w079n34 large was not in 0.7.8 w094n41 medium square w106n30 large diamond w117n41 small was not in 0.7.8 w072n41 medium diamond shoreline blocks: w081n21 w082n21 w085n21 w080n42 Stewart ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Atlas release candidate
A windows binary of the code a few weeks ago is here: ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/atlas-win32-20050112.zip courtesy of Fred Bouvier. Hopefully he will produce a release binary as well. Oh! That's nice :-) Thank you Frederic, you are sooo great ! Downloaded right now ... I needed to dowload GLUT win32 binaries too before getting Atlas to run. Then I had to copy the Atlas files into a \atlas subdiretory under c:\programmi\flightgear\data\ and write some command line options to atlas.exe ... anyway, it works, I will play around with it tonite :-) Roberto ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Atlas release candidate
On Friday 28 January 2005 13:16, David Luff wrote: > Hi all, > > I've put a release candidate of Atlas-0.3 up at: > > http://www.nottingham.ac.uk/~eazdluf/Atlas-0.3.0-rc1.tar.gz > > If a few folk could take the time to download this and try it > out that would be great. > > Changes in the last year or so: > > * Now reads FG-0.9.8 airport and navaid formats > > * Atlas now displays ILS localisers > > * Map has an off-screen rendering option (--headless) to avoid > image corruption due to overlaid windows and possibly allow > maps greater than screen resolution depending on graphics > hardware and drivers [X-Windows with fairly modern GLX only at > present] > > * Map supports multiple scenery paths via FG_SCENERY or > --fg-scenery= (only Map at present, not MapPS). > > * Atlas has --airport=ICAO startup option. > > * Bug fixes. > > Note that Atlas/Map is written by Per Liedman and others, not > myself, but Per is unable to maintain it at the moment. > > Cheers - Dave Hello Dave, I'm using an ATI 9200 vid card with ATI's drivers and I'm getting: Seaching for extensions... GLX_SGIX_fbconfig: NO GLX_SGIX_pbuffer: NO One or more required extension(s) could not be found: GLX_SGIX_fbconfig GLX_SGIX_pbuffer Unable to continue in headless mode - revert to doublebuffer mode? [Y/n] if I try to use --headless mode:( Seems ok if I render to a screen though. I was hoping to generate some 2048x2048 maps, to improve the roads & railways and then intended to scale them down to a more usable size for use with Atlas. LeeE ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Atlas release candidate
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lee Elliott schrieb: > Hello Dave, > > I'm using an ATI 9200 vid card with ATI's drivers and I'm > getting: > > Seaching for extensions... > GLX_SGIX_fbconfig: NO > GLX_SGIX_pbuffer: NO > > One or more required extension(s) could not be found: > GLX_SGIX_fbconfig > GLX_SGIX_pbuffer > Unable to continue in headless mode - revert to doublebuffer > mode? [Y/n] I've just looked up the ATI documentation on OpenGL extensions: http://www.ati.com/developer/atiopengl.pdf There they state that they support WGL_ARB_pbuffer for all interesting Radeon versions (not under NT4 though). GLX_SGIX_pbuffer isn't mentioned. The doc also doesn't mention any extension with "fbconfig". Is it possible that other extensions should be used? CU, Christian -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFB+6AWlhWtxOxWNFcRAnG7AKCmv1nrPwXZhtDtoNYopq/50jJQyACaA8Ea qRLGJvnJBX7lfCrEnklBqws= =mZ7N -END PGP SIGNATURE- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Atlas release candidate
Robicd wrote : A windows binary of the code a few weeks ago is here: ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/atlas-win32-20050112.zip courtesy of Fred Bouvier. Hopefully he will produce a release binary as well. Oh! That's nice :-) Thank you Frederic, you are sooo great ! Downloaded right now ... I needed to dowload GLUT win32 binaries too before getting Atlas to run. Then I had to copy the Atlas files into a \atlas subdiretory under c:\programmi\flightgear\data\ and write some command line options to atlas.exe ... anyway, it works, I will play around with it tonite :-) There is a new set with headless support for Windows as well as for Unix : ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/atlas-win32-20050129.zip It works for me with --size= up to 4096 -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Atlas release candidate
Lee Elliott wrote: I was hoping to generate some 2048x2048 maps, to improve the roads & railways and then intended to scale them down to a more usable size for use with Atlas. I'm just waiting for a bunch of 4096x4096 maps to generate before I feed them to mogrify. 2048x2048 still had a lot of breaks in - 4096x4096 while it still has gaps gives more of an impression of them being continuous lines. I'll probably scale them down to 1024x1024 and 256x256 when they're finished. I've just been having crazy ideas about using the objects database to do an obstructions overprint too :-) -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Atlas release candidate
Jon Stockill wrote: Lee Elliott wrote: I was hoping to generate some 2048x2048 maps, to improve the roads & railways and then intended to scale them down to a more usable size for use with Atlas. I'm just waiting for a bunch of 4096x4096 maps to generate before I feed them to mogrify. 2048x2048 still had a lot of breaks in - 4096x4096 while it still has gaps gives more of an impression of them being continuous lines. I'll probably scale them down to 1024x1024 and 256x256 when they're finished. I've just been having crazy ideas about using the objects database to do an obstructions overprint too :-) not so crazy an idea, for you are giving me ideas. The roads and rails do look much better, but at this resolution, the tile edges show up. Ooops, filled up my hard drive partition... These files are huge, 1-3Mb each at 2048x2048. but only 10% of that size in JPG Hey!, why can't Atlas read JPG files??? smoothed terrain would be an excellent place for JPG. Stewart ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Atlas release candidate
Lee Elliott writes: > > I'm using an ATI 9200 vid card with ATI's drivers and I'm > getting: > > Seaching for extensions... > GLX_SGIX_fbconfig: NO > GLX_SGIX_pbuffer: NO > > One or more required extension(s) could not be found: > GLX_SGIX_fbconfig > GLX_SGIX_pbuffer > Unable to continue in headless mode - revert to doublebuffer > mode? [Y/n] > > if I try to use --headless mode:( > > Seems ok if I render to a screen though. > Hi Lee, Could you post the output of glxinfo please? I've tested this on Radeon 7200 + DRI drivers, and GeForce 5900XT + NVidia binary drivers on Linux, but never on ATI's binary Linux drivers. It's quite possible that they've omitted support for GLX extensions entirely, but it's also conceivable that they might have used a different name - the output from glxinfo might enlighten us. Cheers - Dave ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Atlas release candidate
David Luff writes: > Lee Elliott writes: > > > > > I'm using an ATI 9200 vid card with ATI's drivers and I'm > > getting: > > > > Seaching for extensions... > > GLX_SGIX_fbconfig: NO > > GLX_SGIX_pbuffer: NO > > > > One or more required extension(s) could not be found: > > GLX_SGIX_fbconfig > > GLX_SGIX_pbuffer > > Unable to continue in headless mode - revert to doublebuffer > > mode? [Y/n] > > > > if I try to use --headless mode:( > > > > Seems ok if I render to a screen though. > > > > Hi Lee, > > Could you post the output of glxinfo please? > > I've tested this on Radeon 7200 + DRI drivers, and GeForce 5900XT + NVidia > binary drivers on Linux, but never on ATI's binary Linux drivers. It's quite > possible that they've omitted support for GLX extensions entirely, but it's > also conceivable that they might have used a different name - the output from > glxinfo might enlighten us. > Umm, a google around indicates that they don't support GLX_SGIX_pbuffer & fbconfig, but offer GLX_ATI_render_texture instead: http://www.gamedev.net/community/forums/topic.asp?topic_id=191510 I believe that Fred has got a cross-platform render-texture library to work with Map in order to extend headless mode to windows - hopefully this will be more robust than the code that I wrote and work across a greater range of cards on Linux as well. I'll make up another release candidate when it's added. Cheers - Dave ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Atlas release candidate
Hi Fred Thank you Fred for these. I don't thank you often enough for the windows binaries you provide for the windows community.They are probably as close as most windows users get to a CVS system. I think I would speek for the majority of windows users when I say that without these binaries I would not be using,or contributing,to Flightgear today . Frederic Bouvier writes There is a new set with headless support for Windows as well as for Unix : ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/atlas-win32-20050129.zip It works for me with --size= up to 4096 -Fred Thank you once again. Cheers Innis ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Atlas release candidate
On Saturday 29 January 2005 14:39, Christian Mayer wrote: > Lee Elliott schrieb: > > Hello Dave, > > > > I'm using an ATI 9200 vid card with ATI's drivers and I'm > > getting: > > > > Seaching for extensions... > > GLX_SGIX_fbconfig: NO > > GLX_SGIX_pbuffer: NO > > > > One or more required extension(s) could not be found: > > GLX_SGIX_fbconfig > > GLX_SGIX_pbuffer > > Unable to continue in headless mode - revert to doublebuffer > > mode? [Y/n] > > I've just looked up the ATI documentation on OpenGL > extensions: > > http://www.ati.com/developer/atiopengl.pdf > > There they state that they support WGL_ARB_pbuffer for all > interesting Radeon versions (not under NT4 though). > GLX_SGIX_pbuffer isn't mentioned. > > The doc also doesn't mention any extension with "fbconfig". > > Is it possible that other extensions should be used? > > CU, > Christian Hmm... no idea. Just something else to add to the list of problems with ATI's drivers, I guess. Thanks for having a look into it. LeeE ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Atlas release candidate
On Saturday 29 January 2005 17:31, Jon Stockill wrote: > Lee Elliott wrote: > > I was hoping to generate some 2048x2048 maps, to improve the > > roads & railways and then intended to scale them down to a > > more usable size for use with Atlas. > > I'm just waiting for a bunch of 4096x4096 maps to generate > before I feed them to mogrify. 2048x2048 still had a lot of > breaks in - 4096x4096 while it still has gaps gives more of an > impression of them being continuous lines. I'll probably scale > them down to 1024x1024 and 256x256 when they're finished. > > I've just been having crazy ideas about using the objects > database to do an obstructions overprint too :-) I've wondered about using the vmap(?) data to draw the lines etc using mogrify. Never got any further than thinking about it though. LeeE ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Atlas release candidate
On Saturday 29 January 2005 21:56, David Luff wrote: > Lee Elliott writes: > > I'm using an ATI 9200 vid card with ATI's drivers and I'm > > getting: > > > > Seaching for extensions... > > GLX_SGIX_fbconfig: NO > > GLX_SGIX_pbuffer: NO > > > > One or more required extension(s) could not be found: > > GLX_SGIX_fbconfig > > GLX_SGIX_pbuffer > > Unable to continue in headless mode - revert to doublebuffer > > mode? [Y/n] > > > > if I try to use --headless mode:( > > > > Seems ok if I render to a screen though. > > Hi Lee, > > Could you post the output of glxinfo please? > > I've tested this on Radeon 7200 + DRI drivers, and GeForce > 5900XT + NVidia binary drivers on Linux, but never on ATI's > binary Linux drivers. It's quite possible that they've > omitted support for GLX extensions entirely, but it's also > conceivable that they might have used a different name - the > output from glxinfo might enlighten us. > > Cheers - Dave [EMAIL PROTECTED]:~$ glxinfo name of display: :0.0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.2 server glx extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context client glx vendor string: ATI client glx version string: 1.3 client glx extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_ATI_pixel_format_float, GLX_ATI_render_texture GLX extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: RADEON 9200 DDR x86/MMX/3DNow!/SSE OpenGL version string: 1.3 (X4.3.0-3.7.0) OpenGL extensions: GL_ARB_multitexture, GL_EXT_texture_env_add, GL_EXT_compiled_vertex_array, GL_S3_s3tc, GL_ARB_occlusion_query, GL_ARB_point_parameters, GL_ARB_texture_border_clamp, GL_ARB_texture_compression, GL_ARB_texture_cube_map, GL_ARB_texture_env_add, GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3, GL_ARB_texture_mirrored_repeat, GL_ARB_transpose_matrix, GL_ARB_vertex_blend, GL_ARB_vertex_buffer_object, GL_ARB_vertex_program, GL_ARB_window_pos, GL_ATI_element_array, GL_ATI_envmap_bumpmap, GL_ATI_fragment_shader, GL_ATI_map_object_buffer, GL_ATI_texture_env_combine3, GL_ATI_texture_mirror_once, GL_ATI_vertex_array_object, GL_ATI_vertex_attrib_array_object, GL_ATI_vertex_streams, GL_ATIX_texture_env_combine3, GL_ATIX_texture_env_route, GL_ATIX_vertex_shader_output_point_size, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_func_separate, GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_clip_volume_hint, GL_EXT_draw_range_elements, GL_EXT_fog_coord, GL_EXT_multi_draw_arrays, GL_EXT_packed_pixels, GL_EXT_point_parameters, GL_EXT_rescale_normal, GL_EXT_secondary_color, GL_EXT_separate_specular_color, GL_EXT_stencil_wrap, GL_EXT_texgen_reflection, GL_EXT_texture3D, GL_EXT_texture_compression_s3tc, GL_EXT_texture_cube_map, GL_EXT_texture_edge_clamp, GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, GL_EXT_texture_filter_anisotropic, GL_EXT_texture_lod_bias, GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_vertex_array, GL_EXT_vertex_shader, GL_HP_occlusion_test, GL_NV_texgen_reflection, GL_NV_blend_square, GL_NV_occlusion_query, GL_SGI_color_matrix, GL_SGIS_texture_edge_clamp, GL_SGIS_texture_border_clamp, GL_SGIS_texture_lod, GL_SGIS_generate_mipmap, GL_SGIS_multitexture, GL_SUN_multi_draw_arrays glu version: 1.3 glu extensions: GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat -- 0x23 24 tc 0 24 0 r y . 8 8 8 8 0 24 8 16 16 16 16 1 0 Slow 0x24 24 tc 0 24 0 r . . 8 8 8 8 0 24 8 16 16 16 16 1 0 Slow 0x25 24 tc 0 24 0 r y . 8 8 8 8 0 24 0 16 16 16 16 1 0 Slow 0x26 24 tc 0 24 0 r . . 8 8 8 8 0 24 0 16 16 16 16 1 0 Slow 0x27 24 tc 0 24 0 r y . 8 8 8 8 0 24 8 0 0 0 0 1 0 None 0x28 24 tc 0 24 0 r . . 8 8 8 8 0 24 8 0 0 0 0 1 0 None 0x29 24 tc 0 24 0 r y . 8 8 8 8 0 24 0 0 0 0 0 1 0 None 0x2a 24 tc 0 24 0 r . . 8 8 8 8 0 24 0 0 0 0 0 1 0 None 0x2b 24 dc 0 24 0 r y . 8 8 8 8 0 24 8 16 16 16 16 1 0 Slow 0x2c 24 dc 0 24 0 r . . 8 8 8 8 0 24 8 16 16 16 16 1 0 Slow 0x2d 24 dc 0 24 0 r y . 8 8 8 8 0 24 0 16 16 16 16 1 0 Slow 0x2e 24 dc 0 24 0 r . . 8 8 8 8 0 24 0 16 16 16 16 1 0 Slow 0x2f 24 dc 0 24 0 r y . 8 8 8 8 0 24 8 0 0 0 0 1 0 None 0x30 24 dc 0 24 0 r . . 8 8 8 8 0 24 8 0 0 0 0 1 0 None 0x31 24 dc 0 24 0 r y . 8 8 8 8 0 24 0 0
Re: [Flightgear-devel] Atlas release candidate
On Sun, 30 Jan 2005 17:43:47 +, Lee wrote in message <[EMAIL PROTECTED]>: > On Saturday 29 January 2005 14:39, Christian Mayer wrote: > > Lee Elliott schrieb: > > > Hello Dave, > > > > > > I'm using an ATI 9200 vid card with ATI's drivers and I'm > > > getting: ..tried DRI? I run my 9250 on it. (128 bit Sapphire Radeon 9250 w 128 MB vram for 8xAGP slots.) > Just something else to add to the list of problems with ATI's > drivers, I guess. -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...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] Atlas release candidate
On Thursday 03 February 2005 16:31, Arnt Karlsen wrote: > On Sun, 30 Jan 2005 17:43:47 +, Lee wrote in message > > <[EMAIL PROTECTED]>: > > On Saturday 29 January 2005 14:39, Christian Mayer wrote: > > > Lee Elliott schrieb: > > > > Hello Dave, > > > > > > > > I'm using an ATI 9200 vid card with ATI's drivers and > > > > I'm getting: > > ..tried DRI? I run my 9250 on it. (128 bit Sapphire Radeon > 9250 w 128 MB vram for 8xAGP slots.) I did start looking at it but it wasn't clear to me exactly what I had to download and compile. At some points it started to look as though I'd have to get the entire XF86 tree. LeeE ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Atlas release candidate
Lee Elliott wrote: > I did start looking at it but it wasn't clear to me exactly what > I had to download and compile. At some points it started to > look as though I'd have to get the entire XF86 tree. Yes, X11 is actually an example of a monolithic piece of software. But rebuilding X11 isn't that difficult. Befoure you start this project you might want to have a look to see if your Linux distributor provides an update for you - some distributors do, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Atlas release candidate
On Thu, 3 Feb 2005 22:11:52 + (UTC), Martin wrote in message <[EMAIL PROTECTED]>: > Lee Elliott wrote: > > > I did start looking at it but it wasn't clear to me exactly what > > I had to download and compile. At some points it started to > > look as though I'd have to get the entire XF86 tree. > > Yes, X11 is actually an example of a monolithic piece of software. But > rebuilding X11 isn't that difficult. Befoure you start this project > you might want to have a look to see if your Linux distributor > provides an update for you - some distributors do, ..yup, me, I just replaced "ati" with "radeon" in the driver section of /etc/X11/XF86Config-4 , X being 4.3.0.dfsg.1-10 for Debian Sid, came right up and is packed rather nicely too: [EMAIL PROTECTED]:~ # COLUMNS=100 dpkg -l | grep XFree ii xf86config-knoppix 0.8-4 XFree86 template config files and setup program for kn ii xfree86-common 4.3.0.dfsg.1-10X Window System (XFree86) infrastructure ii xlibmesa-dri4.3.0.dfsg.1-10 Mesa 3D graphics library modules [XFree86] ii xlibmesa-dri-dbg4.3.0.dfsg.1-10 Mesa 3D graphics library modules (unstripped) [XFree86 ii xlibmesa-drm-src 4.3.0-0pre1v1 XFree86 4.3 DRM kernel module source snapshot ii xlibmesa-gl 4.3.0.dfsg.1-10 Mesa 3D graphics library [XFree86] ii xlibmesa-gl-dbg 4.3.0.dfsg.1-10 Mesa 3D graphics library (unstripped) [XFree86] ii xlibmesa-gl-dev 4.3.0.dfsg.1-10Mesa 3D graphics library development files [XFree86] ii xlibmesa-glu 4.3.0.dfsg.1-10 Mesa OpenGL utility library [XFree86] ii xlibmesa-glu-dbg4.3.0.dfsg.1-10 Mesa OpenGL utility library (unstripped) [XFree86] ii xlibmesa-glu-dev4.3.0.dfsg.1-10 Mesa OpenGL utility library development files [XFree86 ii xlibosmesa44.3.0.dfsg.1-10 Mesa off-screen rendering library [XFree86] ii xlibosmesa4-dbg 4.3.0.dfsg.1-10 Mesa off-screen rendering library (unstripped) [XFree8 ii xlibs-pic 4.3.0.dfsg.1-10XFree86 static PIC libraries dummy package ii xserver-xfree864.3.0.dfsg.1-10 the XFree86 X server ii xviddetect 0.3-4 XFree86 installation helper [EMAIL PROTECTED]:~ # ..and, no, I do not need all these, but I've helped fix a few naming conflicts running this bloat. ;o) -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...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] Atlas release candidate
On Friday 04 February 2005 02:27, Arnt Karlsen wrote: > On Thu, 3 Feb 2005 22:11:52 + (UTC), Martin wrote in > message > > <[EMAIL PROTECTED]>: > > Lee Elliott wrote: > > > I did start looking at it but it wasn't clear to me > > > exactly what I had to download and compile. At some > > > points it started to look as though I'd have to get the > > > entire XF86 tree. > > > > Yes, X11 is actually an example of a monolithic piece of > > software. But rebuilding X11 isn't that difficult. Befoure > > you start this project you might want to have a look to see > > if your Linux distributor provides an update for you - some > > distributors do, > > ..yup, me, I just replaced "ati" with "radeon" in the driver > section of /etc/X11/XF86Config-4 , X being 4.3.0.dfsg.1-10 > for Debian Sid, came right up and is packed rather nicely too: > [EMAIL PROTECTED]:~ # COLUMNS=100 dpkg -l | grep XFree > ii xf86config-knoppix 0.8-4 XFree86 template > config files and setup program for kn > ii xfree86-common 4.3.0.dfsg.1-10X Window System > (XFree86) infrastructure > ii xlibmesa-dri4.3.0.dfsg.1-10 Mesa 3D graphics > library modules [XFree86] > ii xlibmesa-dri-dbg4.3.0.dfsg.1-10 Mesa 3D graphics > library modules (unstripped) [XFree86 > ii xlibmesa-drm-src 4.3.0-0pre1v1 XFree86 4.3 DRM > kernel module source snapshot > ii xlibmesa-gl 4.3.0.dfsg.1-10 Mesa 3D graphics > library [XFree86] > ii xlibmesa-gl-dbg 4.3.0.dfsg.1-10 Mesa 3D graphics > library (unstripped) [XFree86] > ii xlibmesa-gl-dev 4.3.0.dfsg.1-10Mesa 3D graphics > library development files [XFree86] > ii xlibmesa-glu 4.3.0.dfsg.1-10 Mesa OpenGL utility > library [XFree86] > ii xlibmesa-glu-dbg4.3.0.dfsg.1-10 Mesa OpenGL utility > library (unstripped) [XFree86] > ii xlibmesa-glu-dev4.3.0.dfsg.1-10 Mesa OpenGL > utility library development files [XFree86 > ii xlibosmesa44.3.0.dfsg.1-10 Mesa off-screen > rendering library [XFree86] > ii xlibosmesa4-dbg 4.3.0.dfsg.1-10 Mesa off-screen > rendering library (unstripped) [XFree8 > ii xlibs-pic 4.3.0.dfsg.1-10XFree86 static PIC > libraries dummy package > ii xserver-xfree864.3.0.dfsg.1-10 the XFree86 X > server ii xviddetect 0.3-4 XFree86 > installation helper [EMAIL PROTECTED]:~ # > > ..and, no, I do not need all these, but I've helped fix a few > naming conflicts running this bloat. ;o) Ah - I might want to have a look at xlibmesa-drm-src. I've also been including the 'radeon' module when I build my kernels but haven't tried using it recently. LeeE ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Atlas release candidate
On Thursday 03 February 2005 22:11, Martin Spott wrote: > Lee Elliott wrote: > > I did start looking at it but it wasn't clear to me exactly > > what I had to download and compile. At some points it > > started to look as though I'd have to get the entire XF86 > > tree. > > Yes, X11 is actually an example of a monolithic piece of > software. But rebuilding X11 isn't that difficult. Befoure you > start this project you might want to have a look to see if > your Linux distributor provides an update for you - some > distributors do, > > Martin. It's so much actually building X11 that puts me off but sorting out the resulting dependencies. Downloading it would be a bit of a pain too as I'm on dial-up. I think I'll stick with using the Debian packages/ATI drivers for now as they are working... ...mostly;) LeeE ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Atlas release candidate
On 12/02/2005 at 22:31 Hans-Georg Wunder wrote: >One question I have: With the left key,I am able to move around on >the map. But then I destroy the flight track. Is it a bug or just a >missing feature ? > A bit of both, I guess. It won't be fixed for this release, but it irritates me as well, so I guess I'll eventually fix it if no-one does it sooner. > >The only thing I am missing is the multiplayer capability. Last week I >flew with my daughter, each on a Linux box. But it was very difficult to >fly together. Then I wanted to use atlas to have an overview, where we >are. But that doesn't work. I would be great to have to ports where >atlas is listening. > Hmm, I hadn't thought of that. I guess it shouldn't be too difficult, but once again, it won't make this release (unless you send in a patch ;-)). Support for multiple tracks, and separate colours per track, is something I'd like to add at some point since I'd like to use Atlas to visualise the AI traffic - it shouldn't be much of a stretch from that to listening on two ports. Cheers - Dave This message has been checked for viruses but the contents of an attachment may still contain software viruses, which could damage your computer system: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Atlas release candidate
Dave, How about retrying to make a release ? -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
