Hi, Dirk Reiners wrote: > The way I look at it it would make sense as something that's explicitly > triggered by the app, i.e. at some point it tells OpenSG: "BTW, I don't need > the > images in memory any more, let's get rid of them". At that point OpenSG would > just release all the images' memory and be optimistic that they really meant > it. > ;) After that point you couldn't save the scene any more or add cluster nodes.
I don't see that necessarily so "global". That should be possible on a TextureChunk-base. Just add a flag "discardImageAfterUpload" or something. I would set that flag on all TextureChunks linked to FBO's PolygonBackground textures, Overlay textures etc. Those things are not tied to the scene at all, so saving should be still possible. Anyhow, if the saving routine encounters a non image-backed texture couldn't it just write out a default image (or a blank image..)? And yes of course clustering would break, but those are things you can control within the application. Regards, Toni ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
