Dave Akers (dla)
Sat, 20 Nov 1999 15:42:29 -0800
Have you tried running your dataset on voglBasic in its original,
unmodified state? I've tried your example on several machines here at SGI
and haven't been able to replicate it yet..
Could you also send us the results of:
1) hinv
2) /usr/gfx/gfxinfo
Thanks.. and if you want to send me your source code I'll take a look at
it and see what I can figure out..
> PS. Should I be opening bug reports through Supportfolio, or is it sufficient
> for me to continue posting them here for the eyes of the Volumizer team?
Sending them to this newsgroup is sufficient.. :)
-Dave
On Sat, 20 Nov 1999, Dave Ahn wrote:
> Hello,
>
> I may have discovered some additional bugs with volumeOptimize() and
> volumeUnoptimize(). These bugs are different from (but perhaps related to)
> my earlier post about voxel editing & unsynchronized texture objects.
>
> I am not changing the voxel data after the initial load in this scenario.
>
> If I render a 512x512x80 unsigned short CT volume without optimizing the
> brick set collection, the app runs fine and the output is correct:
> http://www.vec.wfubmc.edu/volumizer_bug/vo_bug3_unopt.gif
>
> If I volumeOptimize(BEST_PERFORMANCE) beforehand, the output is also correct.
> However, when I volumeUnoptimize() before deleting the brick set collection,
> I get "mgrTM_UnlockSaveData MGRAS_DMA_EDIT_RELEASE failed: Bad file number"
> and a core dump.
>
> If I volumeOptimize(TEXTURE_OBJECTS), the output is incorrect. In fact,
> as I rotate the volume, the bad bricks seem to randomly "roam" among the
> other bricks:
> http://www.vec.wfubmc.edu/volumizer_bug/vo_bug3_texobj_1.gif
> http://www.vec.wfubmc.edu/volumizer_bug/vo_bug3_texobj_2.gif
> http://www.vec.wfubmc.edu/volumizer_bug/vo_bug3_texobj_3.gif
> http://www.vec.wfubmc.edu/volumizer_bug/vo_bug3_texobj_4.gif
>
> The output from volumeOptimize(TEXTURE_OJBECTS) show strange texobj ID's:
> voAppearanceActions::getBestParameters():
> voInterpolationType 3D
> voDataType UNSIGNED_SHORT
> diskDataFormat LUMINANCE
> externalFormat LUMINANCE_ALPHA
> internalFormat LUMINANCE8_ALPHA8_EXT
> brick sizes 128 128 64
> voBrickSet::voBrickSet():
> fractional TRUNCATE
> Volume sizes: 512 512 80 20 Mtextel
> Brick sizes: 128 128 64 1 Mtextel
> Bricks created: 4 4 1 total of 16
> voAppearanceActions::volumeOptimize(): TEXTURE_OBJECTS
> voAppearanceActions::volumeOptimize(): TEXTURE_OBJECTS
> 0 0 269061752 0 268996160 0 0 0 0 0 0 0 0 0 0 0
> voAppearanceActions::volumeOptimize(): TEXTURE_OBJECTS done.
> voAppearanceActions::volumeOptimize(): TEXTURE_OBJECTS done.
>
> Is this a known bug? And if so, will it be fixed in 1.2?
>
> My platforms are Octane MXE & I2 R10K Max Impact/TRAM running IRIX 6.5.6f +
> Volumizer 1.1 + 3696.
>
> Thanks in advance,
> Dave
>
> PS. Should I be opening bug reports through Supportfolio, or is it sufficient
> for me to continue posting them here for the eyes of the Volumizer team?
>
> --
> Dave Ahn <ahn@vec.wfubmc.edu> | "When you were born, you cried and the
> | world rejoiced. Try to live your life
> Virtual Endoscopy Center | so that when you die, you will rejoice
> Wake Forest Univ. School of Medicine | and the world will cry." -1/2 jj^2
>
This archive was generated by hypermail 2.0b2 on Sat Nov 20 1999 - 20:21:40 PST
