Re: [Flightgear-devel] RFC: fgdata merge request 76: Improvedairport Textures
Vivian Meazza wrote: The main problem is that the taxiway textures expose the workaround that we use because we don't (yet) have curved taxiways. The concrete colour does not blend with the old texture, which is still used for aprons etc., and the edge and centre lines also serve to emphasize the problem. Here are a couple of examples. I really don't see the problem here. The new textures look nicer as they have a slightly different colour than the apron. This looks more like planes are taxiing there and leave some tire traces behind. Note the lack of stopways. Presumably something went wrong with the merge. See how every segment of the taxiways is obvious. The colour of the grass is probably a matter of opinion, but note how it fails to merge with the surrounding textures, exposing the cut-in edge of the airfield. I'm very sorry, but IMO this all looks rather unprofessional. I would not wish to release this as it stands. The stopways still work for me here, so there is maybe something wrong in your fgdata? The taxiways in your screenshot surely look ugly but that's more due to the fact that they are not correctly ordered in the apt.dat file. It's not a problem of the new textures. I'm sorry, but I can't reproduce those problems here Chris -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] RFC: fgdata merge request 76:Improvedairport Textures
Christian Schmitt wrote Vivian Meazza wrote: The main problem is that the taxiway textures expose the workaround that we use because we don't (yet) have curved taxiways. The concrete colour does not blend with the old texture, which is still used for aprons etc., and the edge and centre lines also serve to emphasize the problem. Here are a couple of examples. I really don't see the problem here. The new textures look nicer as they have a slightly different colour than the apron. This looks more like planes are taxiing there and leave some tire traces behind. Note the lack of stopways. Presumably something went wrong with the merge. See how every segment of the taxiways is obvious. The colour of the grass is probably a matter of opinion, but note how it fails to merge with the surrounding textures, exposing the cut-in edge of the airfield. I'm very sorry, but IMO this all looks rather unprofessional. I would not wish to release this as it stands. The stopways still work for me here, so there is maybe something wrong in your fgdata? The taxiways in your screenshot surely look ugly but that's more due to the fact that they are not correctly ordered in the apt.dat file. It's not a problem of the new textures. I'm sorry, but I can't reproduce those problems here Yes they do look ugly, because the new textures expose problems that are hidden by the old ones. Here are some more: ftp://abbeytheatre2.org.uk:2121/flightgear/Terrain/KSFO-Textures.jpg ftp://abbeytheatre2.org.uk:2121/flightgear/Terrain/KSFO-Textures-1.jpg ftp://abbeytheatre2.org.uk:2121//Terraflightgearin/KSFO-Textures-2.jpg These are not ordering problems - these are errors. And they are not in any old airport which I happened to find - they are at KSFO. Who is going to find and correct all these errors? I think these errors, while minor, give our primary airport an unacceptable appearance, and make the sim look unprofessional. We have enough errors and omissions in our airports without actually introducing more I have absolutely up-to-date data and source from Git here - still no stopways. Is your data up-to-date? But I suspect that the error is local, since there are no other reports of this problem. Vivian -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] RFC: fgdata merge request 76:Improvedairport Textures
Hi, Yes they do look ugly, because the new textures expose problems that are hidden by the old ones. Here are some more: ftp://abbeytheatre2.org.uk:2121/flightgear/Terrain/KSFO-Textures.jpg ftp://abbeytheatre2.org.uk:2121/flightgear/Terrain/KSFO-Textures-1.jpg ftp://abbeytheatre2.org.uk:2121//Terraflightgearin/KSFO-Textures-2.jpg These are not ordering problems - these are errors. And they are not in any old airport which I happened to find - they are at KSFO. Who is going to find and correct all these errors? I think these errors, while minor, give our primary airport an unacceptable appearance, and make the sim look unprofessional. We have enough errors and omissions in our airports without actually introducing more From the pictures it looks indeed not really good. Even this is caused just by ordering problems- until we don't have fixed every airport we have (and I guess we have a very lot of them- even 10% of our 20.000 would be too much) and the new scenery is generated then, we should make FGFS not look more badly as it already does. Heiko -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] RFC: fgdata merge request 76:Improvedairport Textures
On Wed, May 11, 2011 at 6:38 PM, Vivian Meazza vivian.mea...@lineone.net wrote: Christian Schmitt wrote The stopways still work for me here, so there is maybe something wrong in your fgdata? I have absolutely up-to-date data and source from Git here - still no stopways. Is your data up-to-date? But I suspect that the error is local, since there are no other reports of this problem. For the record, I don't think I have ever seen any stopways. I have now checked with fgdata from before the new textures were committed and the current head - no stopways with either. Anybody got a screenshot with stopways? -- Cheers, Csaba/Jester -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] RFC: fgdata merge request 76:Improvedairport Textures
On Wednesday 11 May 2011 15:14:01 Csaba Halász wrote: On Wed, May 11, 2011 at 6:38 PM, Vivian Meazza vivian.mea...@lineone.net wrote: Christian Schmitt wrote The stopways still work for me here, so there is maybe something wrong in your fgdata? I have absolutely up-to-date data and source from Git here - still no stopways. Is your data up-to-date? But I suspect that the error is local, since there are no other reports of this problem. For the record, I don't think I have ever seen any stopways. I have now checked with fgdata from before the new textures were committed and the current head - no stopways with either. Anybody got a screenshot with stopways? http://www.jentronics.com/fgfs/temp/genapts_stopway01.jpg http://www.jentronics.com/fgfs/temp/genapts_stopway02.jpg http://www.jentronics.com/fgfs/temp/genapts_stopway05.jpg Stopways were added to genapts in January, 2010. Ron -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] RFC: fgdata merge request 76:Improvedairport Textures
Anybody got a screenshot with stopways? -- Yep: GIT 04/29/2011 win32 Hudson Build www.hoerbird.net/fgfs-screen-251.jpg -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] RFC: fgdata merge request 76:Improvedairport Textures
On Wed, May 11, 2011 at 11:24 PM, Heiko Schulz aeitsch...@yahoo.de wrote: Anybody got a screenshot with stopways? Yep: www.hoerbird.net/fgfs-screen-251.jpg Thanks! Apparently I have to use the scenery from fgdata and not terrasync. With that, I have stopway with both the old and the new textures. -- Csaba/Jester -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] RFC: fgdata merge request 76: Improvedairport Textures
Ryan M -Original Message- From: Ryan M [mailto:tpbspamm...@gmail.com] Sent: 10 May 2011 03:46 To: vivian.mea...@lineone.net; FlightGear developers discussions Subject: Re: [Flightgear-devel] RFC: fgdata merge request 76: Improvedairport Textures On Sun, 2011-05-08 at 23:46 +0100, Vivian Meazza wrote: I'm afraid that the improved textures really aren't an improvement. Not only do they not work for taxiways, we have also lost the chevrons at the threshold that were quite recently added: Really? I certainly did *not* touch the stopway textures- I just copied the high-resolution stopway textures, scaled them down, and put them into the low-resolution folder. If they were removed, I'm not sure what happened. I didn't do that in my commit. Stopway textures have been around for quite some time, but they were missing from materials.xml. I was the one who made that fix. :) As for them not looking good at all, most people agree that the grass is an improvement. Perhaps you could tell me what, specifically, is wrong with it. Is it too bright? Too bland? Too repetitive? The main problem is that the taxiway textures expose the workaround that we use because we don't (yet) have curved taxiways. The concrete colour does not blend with the old texture, which is still used for aprons etc., and the edge and centre lines also serve to emphasize the problem. Here are a couple of examples. ftp://abbeytheatre2.org.uk:2121/flightgear/Terrain/EGMH-textures.jpg ftp://abbeytheatre2.org.uk:2121/flightgear/Terrain/EGMH-textures-2.jpg Note the lack of stopways. Presumably something went wrong with the merge. See how every segment of the taxiways is obvious. The colour of the grass is probably a matter of opinion, but note how it fails to merge with the surrounding textures, exposing the cut-in edge of the airfield. I'm very sorry, but IMO this all looks rather unprofessional. I would not wish to release this as it stands. Vivian -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] RFC: fgdata merge request 76: Improvedairport Textures
Hi Vivian, On 09 May 2011, at 00:46, Vivian Meazza wrote: I’m afraid that the “improved textures” really aren’t an improvement. Not only do they not work for taxiways, we have also lost the chevrons at the threshold that were quite recently added: https://picasaweb.google.com/gijsrooy/FlightGearSkyopSTextures#5604420979421192098 The grass isn’t much of an improvement either. On balance, this upload is a regression. IMO we should back it out. Thanks for the report. A missing feature would certainly be a good argument to back out this commit (and I have to admit that I had completely missed that). With respect to the aesthetics, I personally didn't see that many differences, so I had to rely on the evaluation from others, which were generally positive in my reading. I will have a look into the chevron / taxiway issue, although it may take a few days before I'm actually taking action. So if others want to comment, please do so. Cheers, Durk-- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] RFC: fgdata merge request 76: Improvedairport Textures
On Sun, 2011-05-08 at 23:46 +0100, Vivian Meazza wrote: I’m afraid that the “improved textures” really aren’t an improvement. Not only do they not work for taxiways, we have also lost the chevrons at the threshold that were quite recently added: Really? I certainly did *not* touch the stopway textures- I just copied the high-resolution stopway textures, scaled them down, and put them into the low-resolution folder. If they were removed, I'm not sure what happened. I didn't do that in my commit. Stopway textures have been around for quite some time, but they were missing from materials.xml. I was the one who made that fix. :) As for them not looking good at all, most people agree that the grass is an improvement. Perhaps you could tell me what, specifically, is wrong with it. Is it too bright? Too bland? Too repetitive? -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] RFC: fgdata merge request 76: Improvedairport Textures
I'm afraid that the improved textures really aren't an improvement. Not only do they not work for taxiways, we have also lost the chevrons at the threshold that were quite recently added: https://picasaweb.google.com/gijsrooy/FlightGearSkyopSTextures#5604420979421 192098 The grass isn't much of an improvement either. On balance, this upload is a regression. IMO we should back it out. Vivian -Original Message- From: Durk Talsma [mailto:durkt...@gmail.com] Sent: 07 May 2011 09:39 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] RFC: fgdata merge request 76: Improvedairport Textures Whoops, should have been: (request #61). https://gitorious.org/fg/fgdata/merge_requests/61 (Need more coffee, need more coffee, need more coffeee . :-) ) D. On 07 May 2011, at 10:35, Durk Talsma wrote: Hi all, Going through the list of open merge requests for fgdata, I noticed that this one is still open: https://gitorious.org/fg/fgdata/merge_requests/76 One person, other than the author commented positively on the new textures in question (in addition to receiving generally positive comments on the forum), so I would be inclined to accept this merge request, but I cannot really judge if there are any side effects? Any objections? Cheers, Durk -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
