[osg-users] 3D osg::Image allocation size problem

Sebastian Messerschmidt sebastian.messerschmidt at gmx.de
Mon Jul 25 00:53:39 PDT 2016

Am 25.07.2016 um 09:13 schrieb Josiah Jideani:
> Hi SMesserschmidt
> I think you are right about the size issue.
> With sizes less than 640, the getTotalImageSizeIncludingMipmap() function returns the correct size that is 640 x 640 x 640 x 4 x 4.
> With sizes between 640 and 1024 it returns the wrong size that is even less than the maximum size of a 32bit int.
> With sizes above 1024, it just returns 0.
> Changing the data type of the size calculation in the source code could be a step in the right direction.  How soon can it be changed?
OpenSceneGraph as the name implies is open source. You have the source 
code in front of you. Change it, see if it works and submit the change.
I personally don't have the capacities apart from dropping in for a 
reply in the forum every once in a while.

The question arising (and Robert pointed to this already) is that even 
with very very much RAM on your GPU you will start to hit a limit due to 
constant memory transfer between the VRAM and the RAM anyways.
AFAIK the K4200 has 4Gigs of VRAM anyways, so I doubt you will be able 
to effectively handle 3d image beyond this limit.


> Thanks.
> Cheers
> Josiah
> ------------------
> Read this topic online here:
> http://forum.openscenegraph.org/viewtopic.php?p=68202#68202
> _______________________________________________
> osg-users mailing list
> osg-users at lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

More information about the osg-users mailing list