Rafa Gaitan wrote:
Well, our own tiles.. are an extension of PagedLOD (TilePagedLOD), they
incorporates a tile identification inside... The idea is make all system
dynamic, to support variable layers and in general support GIS datasets.
I know that PagedLOD.. and DatabasePager is not made to support this
architecture, and we are extending functionality to do it.
By now the system creates tiles on demand .. and requestTexture and
HeightFields to a data acces layer. The problem is the continuous
increment of memory, and we want to use (or extend) the databasePager to
unload those tiles less used. If is necessary create those tiles
again..it's ok.. we create and request data again. We have a disk cache
of texture and HF tiles, so it's quickly to reload it.
Any suggestion about the implementation of the DatabasePager?
I do all this already, without having modified DatabasePager at all.
What part do you think DatabasePager is missing?
Thanks.
Rafa.
--
Chris 'Xenon' Hanson aka Eric Hammil | http://www.3DNature.com/ eric at logrus
"I set the wheels in motion, turn up all the machines, activate the programs,
and run behind the scenes. I set the clouds in motion, turn up light and
sound,
activate the window, and watch the world go 'round." -Prime Mover, Rush.
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
