Hi Martin, Martin Spott wrote: > At the current state, the latest release packages don't "know" about a > rock surface (material) type and therefore the users of release > packages will be unable to deal with Scenery which contains the such a > type. Thus, in order to ship proper "rock" surface with the Scenery, > users would not only have to add the respective texture to their setup > but also to modify the 'materials.xml" file in order to map the type to > the respective texure. > I understand this argument perfectly. That is why I am trying to have a Rock material available as soon as possible, because I think I might want to use it in the future ;) In the meantime, my latest scenery release only uses the default materials.
> Adding new/more/missing land cover types to the Base Package is > certainly fine for the development tree - which obviously lacks a > representation for quite a few types - but leads to difficulties for > those who prefer to stick to a release package. Therefore I'd be happy > to get you involved into developing an extended set of cover types (for > example on the basis of CORINE) together with the respective textures > and to prepare a nice collection for the next release. > I'd be happy to contribute to this. I will start by making available a write-up of my mapping between the Corine classes and the FG materials, since I spent quite some time on it. Best regards, Maxime ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
