Hi Robert,
I finally got around to getting the 2.6.0 build and tested it out again.
Unfortunatly, the OPTIMIZE_TEXTURE_SETTINGS
flag still causes problems.
As stated below, the problem is if you optimize your scene graph using
the OPTIMIZE_TEXTURE_SETTINGS setting, then recycle the context
Hi Brett,
I've just grokked what is going on - the optimize texture settings is
setting the UnrefImageDataApply to true on scene graph, which is great
for keeping memory usage down, but... it does mean that if you later
what to recompile the texture such as when you create a new viewer,
then
Hi,
Problem:
Using OSG 2.4.0 I have built an app that dynamically creates composite
viewers that have one of more views. The scene graph is kept around as a
ref pointer during the course of multiple viewers. When I delete a
composite viewer and create another one and then use the original
Hi Brett,
We've done work since 2.4.0 to address this issue, could you please
try 2.5.5 or the svn/trunk.
Cheers,
Robert.
On Thu, Jul 17, 2008 at 9:31 PM, Brett Wiesner [EMAIL PROTECTED] wrote:
Hi,
Problem:
Using OSG 2.4.0 I have built an app that dynamically creates composite
viewers that
4 matches
Mail list logo
