Hi Richard, Right. That would be real cool. Following your idea (I didn't think such low-level things could be manipulated), I looked around and came across javax.media.j3d.DepthComponent. I've searched specification, documentation and tutorials, yet I can't seem to find out how I replace the default DepthComponent (presumably DepthComponentNative) with DepthComponentFloat. Could you give me a hint?
If I can get this working, I'm pretty sure that would be the best solution. Even if using floats is slower than int, there's now way it could be as slow as rendering several times over. Also I think it would make for some much cleaner code. Regards /Jørn From: Richard Smith - Systems Engineer - Melbourne <[EMAIL PROTECTED]> One other possibility is to use a framebuffer that implements a floating point Z-buffer rather than integer. That should give much greater dynamic range. =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA3D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
