Hi Johannes,
On Wed, 2004-11-10 at 07:59, Johannes Behr wrote:
>
> Well, not really (not going to construct some really strange
> case) :)
Though so. ;)
> OK, fine. I can change it back next week.
OK.
> Agree. SliceDistance would be more flexible. You only have to be
> carefull that the sliceDistance is used int geo-bbox-space and not
> in the 0-1 range of the texture date.
Good point.
> Maybe we can provide the current sliceDistane in tex-space as
> axtra parameter (e.g. stored in the 'q' values of the second tex
> coord)
Would make sense, yes.
> BTW: If you are experimenting with advanced volume allgos:
> I have some simple code which generates gradients (with a
> 3d-sobel) from a scalar volume and stores it as normalmap
> in the same image. I could include the code in the Image
> class. Something like:
>
> void Image::createNormalMap (void)
>
> Works on scalar (OSG_L_PF) volume and creates a normalmap +
> scalar in Alpha volume (OSG_RGBAL_PF). Could be extended
> to work also on 2d-images to create a 2D-normalmap.
>
> Should we include it as Image method or is this
> really out of scope for the image class?
It seems a little too specialized for the Image class. You could add an
OSGImageTools file.
Yours
Dirk
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
