Cheers for clearing that up.
Kim.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Robert
Osfield
Sent: 20 November 2008 09:18
To: OpenSceneGraph Users
Subject: Re: [osg-users] Texture Management BUMP
Hi Kim,
On Thu, Nov 20, 2008 at 7:36 AM, Kim C Bale <[EMAIL PROTECTED]> wrote:
> I've been pondering this Database pager. It only caches the image
files into memory to prevent loading during runtime doesn't it? Those
are then used to build textures on the card memory.
The DatabasePager doesn't cache any imagery or nodes itself.
The Registry has a cache that you can enable but it's off by default.
There is also now (in SVN/2.7.x) an osgDB::FileCache class that wraps
up a file cache.
> Is there anything to deal with loading textures onto the graphics
card, dishing out texture IDs rather than reloading the texture onto
card memory?
You can't just directly down data to the GPU, you have to load from
disk into main memory then have the OSG download this imagery to the
textures to OpenGL. This is all done for you, the OSG will handle
texture object ruse and us texture subloading to keep everything
efficient.
Robert.
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.or
g
*****************************************************************************************
To view the terms under which this email is distributed, please go to
http://www.hull.ac.uk/legal/email_disclaimer.html
*****************************************************************************************
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
