I have a fix. Local testing works. I have no idea how to get it to you.
Fixes both bugs, and allows for users to revert to this (broken) function
in the future, if required, following the author's existing pattern for
internal versioning.
30c30,31
< // - Set to 2 to use the current version.
---
> /
Forgive the mess, but I'm not savvy in makefile testing, I use cmake+boost,
so.
Given:
inc=0.05;
for (x=-10.0;x<10.0;x+=inc){
for (y=-10.0;x<10.0;x+=inc){
for (z=-10.0;x<10.0;x+=inc){
int x0 = (x > 0.0? (int)x: (int)x - 1);
int y0 = (y > 0.0? (int)y: (int)y - 1);
int z0 = (z > 0.0? (int)z: (int)z -
Package: libnoise0
X-Debbugs-Cc: cliffjki...@gmail.com
Version: 1.0.0+repack-1+b1
Severity: important
Tags: upstream
Dear Maintainer,
While investigating #1093633, I found a source of the problem in
GradientNoise3D.
Per the headers for GradientNoise3D, GradientNoise3D is supposed to return
in the
This appears to be caused by another bug, which I will report separately.
>From the headers:
/// A gradient-noise function generates better-quality noise than a
/// value-noise function. Most noise modules use gradient noise for
/// this reason, although it takes much longer to calculate.
///
///
Package: libnoise0
X-Debbugs-Cc: cliffjki...@gmail.com
Version: 1.0.0+repack-1+b1
Severity: important
Tags: upstream
Dear Maintainer,
I observed out of bounds condition with GradientCoherentNoise3D.
Per source header documentation:
/// @returns The generated gradient-coherent-noise value.
//
5 matches
Mail list logo
