Adam James-Liebau Johnson

The normalization code looks generated, possibly based on system architecture, so I'll mention I'm on Windows 10 with an intel i7-6700K CPU and an NVidia GTX 1080 GPU. More information...

Popping in to say upon further investigation, it looks like the vector alignment issue is actually a debugger display issue. Logging the value (by forking Heron) provides correct values. I'm...

I am getting this issue on release version 1.1.4 (not compiled from source, downloaded from Github) on Windows 10.

Using the automatic upgrade mechanism from 1.1.4 to 1.1.5 fixed this for me (again, Github release version, Windows 10), but it doesn't seem like there were any commits that directly...

Recently spent quite a bit of time debugging an issue with this as the root. This would be an excellent feature to add. However, in the meantime, I would appreciate...

Hey! I'm running into this issue currently. For now, I think I'll experimentally generate a huge number of noise values with my preferred settings, then hardcode the results to avoid...

Looking at `simplex_2d`, it looks like it generates a value from -1 to 1 `fbm_2d` is implemented here: https://github.com/jackmott/rust-simd-noise/blob/master/src/simplex.rs#L322 and can be simplified to: ```rust let mut result = simplex_2d(x,...

I'm pretty lost. I wrote this code to experimentally detect the range of `simplex_2d` which is documented as `-1

Altering to ```rust let mut max: f32 = 0.0; for a in 0..100 { for b in 0..100 { unsafe { let mut result = simplex_2d::( F32x1(a as f32 *...

I copied the implementation from the test and ran the following: ```rust fn simplex_2d_range() { for seed in 0..10 { let mut min = f32::INFINITY; let mut max = -f32::INFINITY;...