This process was different from the rest in that it had several number-options. I was not sure on what this process was meant to perform, so I was not able to adjust the numbers properly (I don't think). This process should be performed by one who knows what a "volume render shaded" process is, so that they could run it properly Before it is concluded that there is an actual bug in the program.
blox> (load "C:\\WINNT\\Profiles\\rburris\\blox_preferences.scm")
Logging commands on C:\WINNT\Profiles\rburris\blox_frame_1.log
Logging started on Tue Nov 28 11:32:42 EST 2000
kawa version 1.6.70
Memory used: 3378488 bytes
blox> (%file-import-raw-block)
blox> (%process-reduction-process-volume-render-shaded)
java.lang.OutOfMemoryError
<<no stack trace available>>
blox>
Joe ... Is this bug needed? Does volumetric work yet? (AD)