Luca Colombari wrote:
Hi,
Thanks for the answer...
Ok, Currently I don't know very much the logic about OpenSceneGraph and I'm
studing it by going into the code. So now my problem is to understand how can I
generate an OpenFlight file by handling also all the related images. I need to
convert DICOM files into OpenFlight model to use another tool that manages .FLT
files.
With OpenFlight Plugin code it is possible to convert (command 'osgconv')
directly DICOM files /or intermediate generated .osg file (with external
automatic generated DDS texture file) into a new .FLT file where is loaded the
volume (nodes): now if I use the command osgviewer to visualize .flt file I am
not able to see nothing, only an empty volume, because no textures are
supported.
I have downloaded an example of .flt file together with .rgb and rgb.attr files
and in this case I am able to visualize it with osgviewer.
So by using RGB plugin I have generate .rgb files from images read from DICOM
files but...how could I link the converted OpenFlight file with the external
RGB textures? Sorry but I'm confused and I'm trying to understand how implement
code with the use of OpenFlight plugin to generate an FLT file with handled
textures and visualize a 3D image with osgviewer or other tools that support
OpenFlight format.
Well, there's quite a few things that could be going wrong here. If you can view
the DICOM file with DDS textures, then it sounds like your DDS plugin works. So
I guess the question is: Why is it that when you view a FLT file, the DDS
textures don't show up? First thing to check would be: Is it loading the DDS
files? To find out, set OSG_NOTIFY_LEVEL=DEBUG and then run osgviewer on your
FLT file. Look through the output to see if it is finding and loading your DDS
files correctly.
If it is loading them correctly, then next thing is to compare your first OSG
file with your second OSG file to see what's wrong. For example, in your first
post, you said you used osgvolume to create an OSG file called output.osg. Then
you convert it to FLT and can't view it. So the question is why? The way to find
out: convert that FLT file back to OSG, call it "output2.osg". Then open both
OSG files in a text editor and compare them side by side and look for
differences to explain why the first file works and the second doesn't.
It could be the case that your first OSG file, output.osg, uses features of OSG
that aren't supported in FLT. I don't have enough information to say for sure.
You just need to investigate and debug.
--
-Paul Martz Skew Matrix Software
http://www.skew-matrix.com/
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
