Re: [Flightgear-devel] FlightGear 2.0.0 release process: Update
On Wed, Feb 3, 2010 at 9:09 AM, Tim Moore wrote: > > > On Wed, Feb 3, 2010 at 12:33 AM, John Denker wrote: > >> >> >> The "rc4" from a couple of days ago has a glitch >> that I haven't seen before: >> >> FRAGMENT glCompileShader "" FAILED >> FRAGMENT Shader "" infolog: >> Fragment shader failed to compile with the following errors: >> ERROR: 0:28: error(#162) Wrong operand types no operation '*' exists that >> takes a left-hand operand of type 'default varying 4-component vector of >> float' and a right operand of type '3-component vector of float' (or there >> is no acceptable conversion) >> ERROR: 0:27: error(#160) Cannot convert from '4-component vector of float' >> to '3-component vector of float' >> ERROR: error(#273) 2 compilation errors. No code generated >> >> What hardware and driver? A possible workaround is to comment out the > conditional tests related to gl_FrontFacing > in Shaders/default.frag and Shaders/mat-anim.frag. > Tim > > Whoops, never mind. Try the Shaders/mat-anim.frag that I just checked into CVS data. I devine that the hardware is ATI... Tim -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear 2.0.0 release process: Update
On Wed, Feb 3, 2010 at 12:33 AM, John Denker wrote: > > > The "rc4" from a couple of days ago has a glitch > that I haven't seen before: > > FRAGMENT glCompileShader "" FAILED > FRAGMENT Shader "" infolog: > Fragment shader failed to compile with the following errors: > ERROR: 0:28: error(#162) Wrong operand types no operation '*' exists that > takes a left-hand operand of type 'default varying 4-component vector of > float' and a right operand of type '3-component vector of float' (or there > is no acceptable conversion) > ERROR: 0:27: error(#160) Cannot convert from '4-component vector of float' > to '3-component vector of float' > ERROR: error(#273) 2 compilation errors. No code generated > > What hardware and driver? A possible workaround is to comment out the conditional tests related to gl_FrontFacing in Shaders/default.frag and Shaders/mat-anim.frag. Tim -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear 2.0.0 release process: Update
On 03/02/10 03:41, Francesco Angelo Brisa wrote: > Do you need me to create deb packages for ubuntu (9.10)/debian(5.0) for > this release ? > Remember that Ubuntu uses Pulseaudio as standard, and at the moment it doesn't play well with flightgear/openal-soft/something. I suggest that probably the best solution is for the ubuntu package to ensure that pasuspender is used to suspend pulseaudio while flightgear is running, I think that should work, not ideal, but workable. Nothing I tried was reliable to get FG working with Pulseaudio, sometimes it worked, but usually it didn't, fairly randomly, so I have taken to manually disabling one of my two sound cards in pulseaudio volume control and using that for Flightgear (with alsa). -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear 2.0.0 release process: Update
On 02/01/2010 10:52 AM, Durk Talsma wrote: > Here's just a quick update regarding the 2.0.0 release. The final release is > really close now. We had planned to have a third release candidate by now, > which we would promote to the final release within a few days from now, > provided that no further showstopping bugs show up. We're currently having a > few minor technical glitches to deal with, which has been delaying the roll > up > of this final release candidate. We're pretty close now, and I expect that > the > final glitches will be solved real soon now. I'm still seeing quite a lot of glitches. Since 2008, before the previous release, I have been keeping a list of bugs at: http://www.av8n.com/fly/fgfs/htm/bug-list.htm I have been updating the list as best I can when I see that bugs have been fixed. There are still dozens and dozens of open bugs there, many of which have been known for years. It might be nice to fix them, rather than putting them off for another year. In many cases, code to fix the problem has been available for months or years. The "rc4" from a couple of days ago has a glitch that I haven't seen before: FRAGMENT glCompileShader "" FAILED FRAGMENT Shader "" infolog: Fragment shader failed to compile with the following errors: ERROR: 0:28: error(#162) Wrong operand types no operation '*' exists that takes a left-hand operand of type 'default varying 4-component vector of float' and a right operand of type '3-component vector of float' (or there is no acceptable conversion) ERROR: 0:27: error(#160) Cannot convert from '4-component vector of float' to '3-component vector of float' ERROR: error(#273) 2 compilation errors. No code generated glLinkProgram "" FAILED Program "" infolog: Fragment shader(s) were not successfully compiled before glLinkProgram() was called. Link failed. glLinkProgram "" FAILED Program "" infolog: Fragment shader(s) were not successfully compiled before glLinkProgram() was called. Link failed. glLinkProgram "" FAILED Program "" infolog: Fragment shader(s) were not successfully compiled before glLinkProgram() was called. Link failed. where the last three lines repeat many many times (and then stop). So far this has been 100% reproducible chez moi. -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear 2.0.0 release process: Update
- "John Denker" a écrit : > > 2) which aircraft to include ? > > That's a different question. I can't help with that. in data : cvs up -Pd -r V2_0_0B in source : make data-tar Or wait the release: official data and source tarballs will be released. -Fred -- Frédéric Bouvier http://my.fotolia.com/frfoto/ Photo gallery - album photo http://fgsd.sourceforge.net/ FlightGear Scenery Designer -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear 2.0.0 release process: Update
Le 01/02/2010 18:52, Durk Talsma a écrit : > Hi All, > > Here's just a quick update regarding the 2.0.0 release. The final release is > really close now. We had planned to have a third release candidate by now, > which we would promote to the final release within a few days from now, > provided that no further showstopping bugs show up. We're currently having a > few minor technical glitches to deal with, which has been delaying the roll > up > of this final release candidate. We're pretty close now, and I expect that > the > final glitches will be solved real soon now. > Win32 and Win64 packages : http://frbouvi.free.fr/flightsim/fgsetup-2.0.0-RC4.exe.torrent http://frbouvi.free.fr/flightsim/fgsetup64-2.0.0-RC4.exe.torrent The 64-bit version should be installed after having installed 32-bit version. I am also uploading them to ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32 but be patient, files are huge. The torrents are ready right now -Fred -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear 2.0.0 release process: Update
On 02/02/2010 07:41 AM, Francesco Angelo Brisa wrote: > Do you need me to create deb packages for ubuntu (9.10)/debian(5.0) for > this release ? Well, it would be nice if somebody would create such things. > if yes I need to know a couple of things: > 1) where to get the exact fgfs/simgear/osg code for this realease (I mean I > don't think I can get it througt csv). You "should" be able to get it via CVS ... but I stopped using CVS a long time ago. I recommend using the git repository at http://gitorious.org/fg/ including e.g. the FG "source" at http://gitorious.org/fg/flightgear Alas gitorious seems to be somewhat confused about tags; if you click on the v2.0.0-rc4 link in the "activites" section of today's summary page: http://gitorious.org/fg/flightgear then it takes you to http://gitorious.org/fg/flightgear/commit/v2.0.0-rc4 which is 404 not found. Things work better if you happen to know that the release candidates live on the _master_ branch. On the aforementioned summary page, click on one of the various places that mention "master" ... which will take you to http://gitorious.org/fg/flightgear/commits/master And then look at the far far bottom of that page. Near bottom right-hand corner there is a box listing _tags_. There you will discover that the v2.0.0-rc4 tag is in fact identical to the http://gitorious.org/fg/flightgear/commit/729e2875 object. === I would assume that to an excellent approximation, every file in that repository (except for the .git directory if any) should be included in the deb-source package. A few extra files here and there never killed anybody. Another thing that you would need is a usable DEBIAN/control file. There actually exists a package/debian/control file in the git repo, but it has apparently not been touched since it was created in mid-2004. I suspect it has never been used. Indeed I suspect most people on this list have forgotten that it ever existed. It seems to me that it would be a Good Thing to have the control file be part of the project, and to revise it as needed. It would be easier to use (e.g. via pkg-deb -b ...) if we uppercasified the directory -> DEBIAN/control and made a few other cosmetic changes. dpkg-scanpackages also comes in handy in this context. Here is a control file that I have found useful as a metapackage to make sure I have the needed development environment. I doubt it is exactly correct, but it is way better than nothing, and may serve as a useful building block. Package: flightgear-dev Version: 2.0.0 Architecture: all Maintainer: FlightGear Developers Installed-Size: 100 Depends: g++ (>= 4:4.3.1), make, autoconf, binutils, coreutils, freeglut3-dev (>= 2.4.0-6), libalut-dev (>= 1.1.0-2), libc6 (>= 2.10.1), libgcc1 (>= 1:4.4.1), libglu1-mesa-dev | libglu1-dev, libice-dev (>= 2:1.0.5), libopenal-dev (>= 1:1.8.466), libsm-dev (>= 2:1.1.0), libstdc++6-4.4-dev, libx11-dev (>= 2:1.2.2), libxext-dev (>= 2:1.0.99.1), libxi-dev (>= 2:1.2.1), libxmu-dev (>= 2:1.0.4), libxt-dev (>= 1:1.0.5), zlib1g-dev (>= 1:1.2.3.3), libboost-dev (>= 1.37.1) Recommends: libopenscenegraph-dev (>= 2.8.2), libopenthreads-dev (>= 2.8.2), libplib-dev (>= 1.8.5-1), simgear-dev (>= 2.0.0), fgfs-base (>= 2.0.0) Section: games Priority: extra Homepage: http://www.flightgear.org/ Description: FlightGear Flight Simulator -- development metapackage FlightGear is a free and richly-featured flight simulator. . This metapackage depends on the libraries and utilities required for compiling FlightGear from source. It provides nothing in and of itself, so you may remove it if nothing depends on it. > 2) which aircraft to include ? That's a different question. I can't help with that. -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear 2.0.0 release process: Update
On Mon, 1 Feb 2010 18:52:40 +0100, Durk Talsma wrote: > Hi All, > > Here's just a quick update regarding the 2.0.0 release. The final release > is > really close now. We had planned to have a third release candidate by now, > which we would promote to the final release within a few days from now, > provided that no further showstopping bugs show up. Do you need me to create deb packages for ubuntu (9.10)/debian(5.0) for this release ? if yes I need to know a couple of things: 1) where to get the exact fgfs/simgear/osg code for this realease (I mean I don't think I can get it througt csv). 2) which aircraft to include ? > [...] Cheers Francesco -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear 2.0.0 release process: Update
On Mon, 1 Feb 2010 18:52:40 +0100, Durk Talsma wrote: > Hi All, > > Here's just a quick update regarding the 2.0.0 release. The final release > is > really close now. We had planned to have a third release candidate by > now, > which we would promote to the final release within a few days from now, > provided that no further showstopping bugs show up. Do you need me to create deb packages for ubuntu (9.10)/debian(5.0) for this release ? if yes I need to know a couple of things: 1) where to get the exact fgfs/simgear/osg code for this realease (I mean I don't think I can get it througt csv). 2) which aircraft to include ? > [...] Cheers Francesco -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
