This appears to be caused by another bug, which I will report separately. >From the headers: /// A <i>gradient</i>-noise function generates better-quality noise than a /// <i>value</i>-noise function. Most noise modules use gradient noise for /// this reason, although it takes much longer to calculate. /// /// The return value ranges from -1.0 to +1.0.
Actual test cases: WAAAAAY out of bounds. GradientNoise3D(0.95,0.9,0.9,0,0,0)=-3.14675 GradientNoise3D(0.95,0.9,0.95,0,0,0)=-3.17288 GradientNoise3D(0.95,0.95,-1,0,0,-2)=1.37768 GradientNoise3D(0.95,0.95,-0.95,0,0,-1)=2.76058 GradientNoise3D(0.95,0.95,-0.9,0,0,-1)=2.78524 GradientNoise3D(0.95,0.95,-0.85,0,0,-1)=2.8099 GradientNoise3D(0.95,0.95,-0.8,0,0,-1)=2.83456 GradientNoise3D(0.95,0.95,-0.75,0,0,-1)=2.85921 GradientNoise3D(0.95,0.95,-0.7,0,0,-1)=2.88387 GradientNoise3D(0.95,0.95,-0.65,0,0,-1)=2.90853 GradientNoise3D(0.95,0.95,-0.6,0,0,-1)=2.93319 GradientNoise3D(0.95,0.95,-0.55,0,0,-1)=2.95785 GradientNoise3D(0.95,0.95,-0.5,0,0,-1)=2.98251 GradientNoise3D(0.95,0.95,-0.45,0,0,-1)=3.00717 GradientNoise3D(0.95,0.95,-0.4,0,0,-1)=3.03183 GradientNoise3D(0.95,0.95,-0.35,0,0,-1)=3.05649 GradientNoise3D(0.95,0.95,-0.3,0,0,-1)=3.08115 GradientNoise3D(0.95,0.95,-0.25,0,0,-1)=3.10581 GradientNoise3D(0.95,0.95,-0.2,0,0,-1)=3.13047 GradientNoise3D(0.95,0.95,-0.15,0,0,-1)=3.15513 GradientNoise3D(0.95,0.95,-0.1,0,0,-1)=3.17979 GradientNoise3D(0.95,0.95,-0.05,0,0,-1)=3.20445
