After reading Syntopia's excellent post on using dual numbers to create a multi-scale box ...
http://www.fractalforums.com/new-theories-and-research/dual-numbers-for-creating-distance-estimators/I decided to dust off an old script that used a vector derivative for doing same. (When dual numbers become standard types I will abandon this quest.) The idea is simple and I am sure others have tried it and I'm hoping they can explain it to me! I simply changed all the scalars to vectors so the code looks much the same (in glsl).
const vec3 minRadius=vec3(0.25,0.25,0.25);
const vec3 fixRadius=vec3(1.0,1.0,1.0);
const vec3 foldLimit=vec3(1.0,1.0,1.0);
const vec3 SCALE=vec3(-2.5,-2.5,-2.5);
const vec3 scale=SCALE/minRadius;
const vec3 boundingVolume=abs(SCALE*foldLimit)*3.0;//????
const vec3 dc=vec3(1.0,1.0,1.0);
float DE(vec3 z0)
{
vec3 z=z0;
vec3 dz=dc;
for (int n=0;n<iters;n++) {
z=clamp(z,-foldLimit,foldLimit)*2.0-z;
vec3 scl=scale*clamp(minRadius/dot(z,z),minRadius,fixRadius);
z*=scl;dz*=abs(scl);
z+=z0;dz+=dc;
}
return length(z)/length(dz);
//...or for a rect signed value
//z=(abs(z)-boundingVolume)/dz;
//return max(z.x,max(z.y,z.z));
}
All the constants minRadius,fixRadius,foldLimit and SCALE can be different in each dimension.
The code above "works" but it raises more questions.
First what should the return value be for a signed and scaled sphere?
Should dz really be initialized to vec3(1.0) or normalize(vec3(1.0))?
I assumed if I rotate z I must also rotate dz. This isn't true and creates a worse estimate. Why?
If we now have an idea of how the function is changing in each dimension can we use the ray march direction to look only at the change in the direction we are marching???
Has anyone tried this and can give their insight?
Here's the output...
<![CDATA[<a href="http://www.youtube.com/v/mmmRg-oVOoM&rel=1&fs=1&hd=1" target="_blank">http://www.youtube.com/v/mmmRg-oVOoM&rel=1&fs=1&hd=1</a>]]>
December 31, 2009, 11:40:08 AM
Dilber MC Theme by HarzeM