On 6/1/06, Rafa Gaitan <[EMAIL PROTECTED]> wrote:
> As Robert mentioned, OSG uses "loaders" to bring in files "from disk". Loaders are > plugins, which you can write, which take a "filename" and deliver a scene subgraph when > finished. However, nothing says that the filename has to be a filesystem path, or that the > data actually originates from a file on disk that is specified by that path. In my case, > the "filename" is a tile ID, encoded as a string. My plugin creates the data from both > in-memory and on-disk resources, and delivers the resulting data to the scene graph. > > When the scene graph is not using the tile data, PagedLOD discards the scene subgraph > on its own, and when it is needed again, it calls the plugin to load/create the data again. Thanks!, thats a good idea. We will study it.! > > but by now I prefer to continue the current development, because is not > > clear to me in a unique generated earth mesh.. apply height fields and > > texture tiles. > > Sorry, I don't understand what you're asking there. Well.. I begin with the view of the complete planet. ovPlanet is an implementation of a multiresolution planetary rendering algorithm, with a continuous mesh. But by now the web page is not working! :(. Thanks again. Rafa.
To see a osg based planetary engine, look at my project : http://www.magrathea-engine.org And we generate on the fly procedural details for the terrain, all using the osg database pager without any modification on it. As Chris says, we use a custom osgDB plugin wich use a encoded string as filename to know what to generate. You can find the sources of our project on our site, so feel free to take a look on how we implement it. (There is also a demo version for windows) -- Serge Lages http://www.magrathea-engine.org _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
