Re: volumeOptimize()

New Message Reply Date view Thread view Subject view Author view

Sean Spicer (spicer@bme.stanford.edu)
Thu, 29 Jul 1999 00:38:22 -0700 (PDT)

Clara,

One problem you may be seeing is that while mvInitGfx is called only once,
MonsterInit is called on every pipe as it is started. (essentially to
load the lookup table on each pipe from shared memory.) Since the volume
is kept in shared memory, the optimization probably should only be done
once, so I would guess that leaving the optimize call to mvInitGfx alone
would be the best thing. As for why one prints out and one doesn't, I
have no clue. Did you voError::setDebugLevel(...) _before_ mvInitialize in
main.cxx??

hope that helps.

sean

On Wed, 28 Jul 1999, Clara Chan wrote:

> Hi, I am a little puzzled about how
> voAppearanceActions::volumeOptimize() works.
> I am using the monsterview program.
>
> voAppearanceActions::volumeOptimize(
> aVolume,voOptimizeVolumeTypeScope::BEST_PERFORMANCE);
>
> was called in both mvInitGfx() and MonsterInit()
>
> When I run with 4 pipes, part of the image
> is missing and I get the following messages:
>
> voAppearanceActions::volumeOptimize(): BEST_PERFORMANCE
> voAppearanceActions::volumeOptimize(): TEXTURE_OBJECTS
> 1073758208 1073758208 1073758208 1073758208 1073758208
> 1073758208 1073758208 1073758208 1073758208 1073758208 1073758208
> 1073758208 1073758208 1073758208 1073758208 1073758208 1073758208
> 1073758208 1073758208 1073758208
> voAppearanceActions::volumeOptimize(): TEXTURE_OBJECTS done.
> voAppearanceActions::volumeOptimize(): BEST_PERFORMANCE done.
> voAppearanceActions::volumeOptimize(): BEST_PERFORMANCE
> voAppearanceActions::volumeOptimize(): TEXTURE_OBJECTS
> 1073758208 1073758208 1073758208 1073758208 1073758208
> 1073758208 1073758208 1073758208 1073758208 1073758208 1073758208
> 1073758208 1073758208 1073758208 1073758208 1073758208 1073758208
> 1073758208 1073758208 1073758208
> voAppearanceActions::volumeOptimize(): TEXTURE_OBJECTS done.
> voAppearanceActions::volumeOptimize(): BEST_PERFORMANCE done.
> voAppearanceActions::volumeOptimize(): BEST_PERFORMANCE
> voAppearanceActions::volumeOptimize(): TEXTURE_OBJECTS
> 1073758208 1073758208 1073758208 1073758208 1073758208
> 1073758208 1073758208 1073758208 1073758208 1073758208 1073758208
> 1073758208 1073758208 1073758208 1073758208 1073758208 1073758208
> 1073758208 1073758208 1073758208
> voAppearanceActions::volumeOptimize(): TEXTURE_OBJECTS done.
> voAppearanceActions::volumeOptimize(): BEST_PERFORMANCE done.
>
> Then I commented out the volumeOptimize call in mvInitGfx() and
> I get the following but the image doesn't come on:
>
> voAppearanceActions::volumeOptimize(): BEST_PERFORMANCE
> voAppearanceActions::volumeOptimize(): INTERLEAVE_2WAY
> voAppearanceActions::volumeOptimize(): BEST_PERFORMANCE
> voAppearanceActions::volumeOptimize(): INTERLEAVE_2WAY
> voAppearanceActions::volumeOptimize(): BEST_PERFORMANCE
> voAppearanceActions::volumeOptimize(): INTERLEAVE_2WAY
> OpenGL Volumizer error 2:
> voAppearanceActions::textureInterleave(): invlid dataType
> OpenGL Volumizer error 2:
> voAppearanceActions::textureInterleave(): invlid dataType
> OpenGL Volumizer error 2:
> voAppearanceActions::textureInterleave(): invlid dataType
> ...
>
> If I leave the one in mvInitGfx and comment out the one
> in MonsterInit, I get no printouts at all with an image
> that looks OK.
>
> Can you explain the above behavior?
> Thank you very much.
> Clara
>

______________________________________________________________________________
Sean Spicer Stanford University Medical Center
Biomechanical Engineering Division of Vascular Surgery, Suite H3642
Cardiovascular Biomechanics Lab Stanford CA, 94305
                                     Telephone...650.723.1695
                                       Fax.........650.723.8762

                http://solvedeath.stanford.edu/~spicer
  

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Nov 01 1999 - 14:11:14 PST