The mapping of land use/cover types to specific textures is defined in the
materials.xml file. In the past we often would map several similar types of
land cover to a single texture to keep texture memory usage under control
and in some situations because we didn't have a specific texture created for
a particular land use/cover type. However, it's all controllable in the
materials.xml file if we have artists out there who'd like to improve the
land cover textures. In my opinion many of our textures are very good, but
many of them could use improvement.
If there is anyone out there who wants to work on improving some of our land
use/cover textures, please speak up and we can give you some more specific
details to keep in mind when designing textures.
Best regards,
Curt.
On Mon, Jun 8, 2009 at 2:43 PM, Maxime Guillaud wrote:
> Hello,
>
> Following my recent uncovering of detailed landcover information for
> France (see
>
> http://www.flightgear.org/forums/viewtopic.php?f=5&t=5105&sid=c3a960f7f3ee2f652973410a6d06ce9b
> ),
> I proceeded to generate custom scenery integrating this data.
>
> Following the tutorial from the wiki
> (
> http://wiki.flightgear.org/index.php/Using_the_Custom_Scenery_TerraGear_Toolset
> ),
> I was able to generate some scenery successfully. However, when I load
> it into FG, it looks like many of the land use data types that I
> included ("EvergreenBroadCover", "Deciduousbroadcover",
> "Drycroppasturecover", "Evergreenbroadcover"...) map into the same
> texture. I do not see the varitey of textures that I expect from looking
> into my data/Textures/Terrain directory.
>
> Can somebody explain the mapping mechanism between the "area string"
> (that is fed to shape-decode during the scenery generation), and the
> names of the texture files ? or point me to the relevant source code ?
>
> I found the page http://wiki.osgeo.org/wiki/LandcoverDB_CS_Detail but it
> doesn't seem to answer my question...
>
> Maxime
>
>
>
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables unlimited
> royalty-free distribution of the report engine for externally facing
> server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
--
Curtis Olson: http://baron.flightgear.org/~curt/
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel