|
texture object bug?
Dave Ahn (ahn@vec.wfubmc.edu)
Hello,
I may have uncovered another bug in Volumizer 1.1 + 3696 patch.
I am changing the voxel data in each brick in a brick set collection. All
The pseudo code is:
The code works just fine when the brick collection is unoptimized, as shown:
which proves that the voxel copy and dataConvert() are working properly.
However, if the volume had been optimized beforehand using
I am calling volumeOptimize() only once after the initial creation and
Is my code incorrect, or is this a bug with texture object updates in
My platforms are Max Impact/TRAM and Octane MXE, both running IRIX 6.5.5m.
On a related note, is it legal to optimize, unoptimize, optimize the same
Thanks in advance,
-- 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 Wed Nov 10 1999 - 19:46:48 PST |
|
made by Digital Vintage with nginx-s3-gateway and some magic digitalvintage.ru t.me/digitalvintage_ru instagram.com/digitalvintage.ru |