Hi Robert
Robert Osfield a écrit :
So when the file size in memory estimation exceed the free memory estimated,
the load is not done.
But this is the point : if I return /ERROR_IN_READING_FILE, /won't the file
be added to a black list ?
What about /FILE_LOADED /?
The OSG doesn't provide any blacklisting capability so it's something
you'll have to implement yourself in your read callback.
Sorry I was not enough precise in my explanations : I don't want any
blacklist, I was asking if OSG gets one. So it is perfect for me that no
file will be blacklisted. I was asking what error code should I return
to make DatabasePager consider the file in not available, but if a new
request is done later (when some memory has been released) its will try
again. What difference will it makes if I return FILE_LOADED or
ERROR_IN_READING_FILE ?
Next, is there a way to force pagedLod to unload some nodes ? to implement a
"force unload" to free a bit a memory.
I'm using OSG 2.8.1 and I cannot use the last release...
As the ReadFileCallback can be implemented, are there other possible
personalization concerning the way to load/unload cached datas ?
The DatabasePager now defaults to using a MaxPagedLOD scheme where it
expires currently unused PageLOD children on demand, so that as lots
of new PagedLOD come in to view ones that aren't in the view are
deleted keeping a roughly constant load. You can adjust the target
MaxPagedLOD in your app via the OSG_MAX_PAGED_LOD env var or the
DatabasePager::setTargetMaximumNumberOfPageLOD(value).
Please note this is a target that will be exceeded is more PagedLOD's
are required for a single frame, so the view will not ever be
constrained by the MaxPagedLOD target, once the high loaded view is
moved away from the PagedLOD numbers will drop back down to the
target.
Robert.
So If I decrease this value, some PagedLod will be released ?
What difference with cameraLODScale ? I just made a test
increasing/decreasing this value and I saw the effect on PagedLod and
memory.
Thanks for your answers.
Regards,
Vincent.
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4835 (20100204) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
