Hi Paul, On Wed, Jan 28, 2009 at 3:07 PM, Paul Melis <p...@science.uva.nl> wrote: > Robert Osfield wrote: > The osgvolume example supports reading a file containing a transfer > function. Am I correct in assuming this file must have the format > <scalar value> <r> <g> <b> <a> > where the color values are in the range [0-1]?
This is correct, here's an example of a simple little transfer function that I put together for testing. 0 0 0 0 0 0.15 1 0 0 0.2 0.2 0 1 0 0.3 0.35 0 1 1 0.4 0.6 1 1 1 0.8 1 1 1 1 1 > It also seems that you must > use --cpu-tf in order for the transfer function to actually get used, but > I'm still not getting the results I expect (compared to other volume > rendering packages). No, you should be able to use the GPU for transfer functions - this is supported already, the shaders are available and built into osgVolume. You get the best visual quality by doing the transfer function down on the GPU as well as it works at higher precision than the CPU based conversion which drops you down to RGBA8. > What are the current requirements on the data in > VolumeTiles, only 8-bit? You can use any precision you want. Most of the dicom files I've been testing against are 16bit, and this certainly produces better results than 8bit data sets. I wonder if it's how you are setting up osgvolume that is the problem. Could you give an example of the osgvolume command line you are using, as well as links to the data. Thanks, Robert. _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
