Fred Dech (fred@cerulean.bvis.uic.edu)
Thu, 5 Aug 1999 11:37:42 -0500 (CDT)
my dev platform is IR w/4 RMs. displaying large volumes.
application is Performer-based, using a heavily modified version of
Volumizer Performer node from the Performer example program.
symptoms:
1. 512x512data at 128 (1 brick) or less slices, great performance (~20 fps).
2. with over 128 slices (>1 brick) performance goes south, big-time
(~0.15 fps)
3. remove small texture(s) from GUI portion of application and great
performance returns to multiple brick volume (512x512ushort) over
128 slices.
4. i uninstalled patch3696, just to check. no change.
conclusions:
1. i'm sc**wed! :o :^)
2. the texture(s) in my GUI are killing Volumizer performance when more
than one brick is required to hold the voxel data. but why?
any suggestions would be greatly appreciated.
--fred
-- Fred Dech fdech@uic.edu VRMedLab (312) 413-3092: fax (312) 996-8342
This archive was generated by hypermail 2.0b2 on Mon Nov 01 1999 - 14:21:39 PST