Hi Vincent, I don't really know where to start as it does sound like to me you are trying to do something that I would see as inappropriate for a real-time application. It's like you're trying to re-direct a river back up a mountain and expecting it to flow back up-hill.
Now if you really think what you are trying to do is sensible for you application and PagedLOD doesn't do this, then there is a point when you need to decide that you need to go it alone and role your own paging node, and your own database pager. There is nothing stopping you for implementing your own paging node and database pager, sure it's more work but then you'd have complete control. I can't really help you further on this journey. My advice would be to just use PagedLOD as it is, for me trying to expiry low level of detail nodes is a false economy and counter-productive to purse, but if you feel you need to do then so be it. Off you go. Robert. On Thu, Apr 8, 2010 at 10:02 AM, Vincent Bourdier <[email protected]> wrote: I know that I am fighting with PagedLOD default behavior. The default behavior is very good in 80% of the use case, and for the last 20%, I just need to make PagedLOD nodes only manage the higher level, and if possible release the Low-level to save some memory... So with my actual code, the Low and the High level will be loaded in memory and the High level will be displayed. I just would like to make the Low level not beeing kept in memory (if possible) PagedLOD is designed to have keep the lowest level of detail nodes in memory and expiry the high level of details, and only expire the lower level of details once the high level ones have been removed. So the low level can expires ? I thought the lowest level never expire to keep at least one level to be displayed. Thanks for your help _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
