@ darkbeam, I had a look and it turned out to be basically a standard aBox with an additional plusAbsoluteCpixel which was applied based on the current axis point's sign()
z.x += sign(z.x) * abs(c.x) * scale;
void TransfAddCpixelSymmetricalIteration(CVector3 &z, CVector3 c, const cFractal *fractal)
{
CVector3 tempFAB = c;
if (EnabledxTrue) tempFAB.x = fabs(tempFAB.x);
if (EnabledyTrue) tempFAB.y = fabs(tempFAB.y);
if (EnabledzTrue) tempFAB.z = fabs(tempFAB.z);
tempFAB *= scale111;
z.x += sign(z.x) * tempFAB.x;
z.y += sign(z.y) * tempFAB.y;
z.z += sign(z.z) * tempFAB.z;
}
But the DE calc is no good, and there are cuts
Since then I explored a bit, and found it is was somewhat better when reduced to a aSurf.
or as a box rearranged to a simple sequence of
z += plusAbsoluteCpixel,
z = abox formula (with no addCpixel and no cut-forming rotations).
So I am thinking because I have altered original point c then this could be called a "domain change"
February 28, 2015, 11:16:03 PM
Dilber MC Theme by HarzeM