You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -319,10 +319,3 @@ Use `libnoise` if you don't need a ton of configuration, are using relatively sm
319
319
If you absolutely need `f64` support, use `libnoise`, but again, the permutation table rng makes the large domain kinda a moot point. Same goes for `noise`.
320
320
If you are integrating with `bevy`, need lots of customization, need general, high performance, or need serialization and reflection, use `noiz`.
321
321
I am not aware of a reason to use `noise` (though there may well be one I'm missing).
322
-
323
-
## Rough Roadmap
324
-
325
-
-[ ] Optimize with fastmath coming in rust 1.88
326
-
-[ ] Add dynamic types to switch between noise functions via reflection.
327
-
-[ ] (Maybe) Let noise types generate WESL code. (Specify noise in rust, build to WESL.) Possible, but maybe not worth it.
This is a small release, mostly focusing on rounding some rough edges from 0.1.
4
+
If there are any issues you run across, please don't hesitate to open an issue!
5
+
6
+
## Enhancements
7
+
8
+
When collecting results of layered noise, `Normed` and `NormedByDerivative` can now collect gradients. Ex: `Normed<WithGradient<f32, Vec2>>`.
9
+
This is the proper way to collect gradient information of fractal layered noise and is very useful for things like analytical normals for mesh generation.
10
+
11
+
A new noise function, `WithGradientOf`, can now be used to "fudge" a gradient value.
12
+
Although this will not be correct, it can be artistically useful when paired with `NormedByDerivative`, or other systems that use gradient information to affect the output.
13
+
14
+
A new `Lerped` curve now allows interpolating between vector space values.
15
+
This is particularly helpful when combined with the new `RemapCurve` noise function.
16
+
17
+
A noise function, `Translated`, has been added to replace the `Offset<Constant>` pattern.
18
+
19
+
The `prelude::common_noise` module has been expanded to include derivatives of common noise.
20
+
In general, I prefer to use the noise types directly, rather than these aliases; that opens up more customization and demystifies the actual algorithm.
21
+
However, in some places, shorter names are preferred, and now derivatives are possible there too.
22
+
23
+
## Bug Fixes
24
+
25
+
It's hard to define a "bug" when it comes to noise, since there's no real correct vs incorrect for most systems; just whether or not it "feels" random enough in the right ways.
26
+
That said, there were a few bug-like fixes over 0.1.
27
+
28
+
Some gradients were not mathematically rigorous; they were often "good enough", but they weren't correct.
29
+
Many of these are now fixed, including simplex noise, fractal noise, masked noise, and linearly mapped noise (like `UNormToSNorm`).
30
+
Notably, `Abs`, `Billow`, and `NormedByDerivative` are still not mathematically rigorous.
31
+
These do not appear to be classically differentiable, but "good enough" implementations are still provided.
32
+
33
+
Perlin noise is now normalized to ±1; it was ±(1/√N) where N was the number of dimensions.
34
+
This was previously not normalized for performance (it's a linear scale, which the user will configure anyway), but it has been fixed to help with usability.
35
+
With fast-math coming in rust 1.88, this will be made zero cost in the future.
36
+
37
+
## Migration Guide
38
+
39
+
`Blender` and `DiferentiableGradientBlender` have been replaced by `ValueBlender`, `DifferentiableValueBlender`, `GradientBlender`, and `DifferentiableGradientBlender`.
40
+
The functionality of these traits remains the same, but this separation allows more specific implementations.
41
+
42
+
The `LayerOperationFor` trait has been expanded over the new `LayerResultContextFor`.
43
+
This will not affect most users, but if you were making custom layers, this will need to be migrated.
44
+
45
+
`Scaled` now scales directly rather than going through a nested noise function.
46
+
If you want the previous behavior, use `Masked`.
47
+
48
+
I have deliberately kept this brief, as these changes are unlikely to affect anyone, but if you have any trouble migrating, please open an issue!
49
+
50
+
## What's next
51
+
52
+
It's hard to predict the future here, as I have limited time, and lots of my ideas here depend on other projects.
53
+
However, there are some things I'd like to explore for the future:
54
+
55
+
- 64 bit support: Noiz is powered by bevy_math, which is growing to support 64 bit precision.
56
+
When that work is complete, Noiz will upgrade to support `f64` based inputs and outputs.
57
+
- even faster: Rust 1.88 brings support for fast-math, offering some insane performance opportunities at the cost of precision.
58
+
This will probably be an opt-out feature, as it is not without downsides, but this is still up for debate.
59
+
- Other rng backends: Noiz is powered by a *very* specialized and optimized random number generator.
60
+
Some power users may want to make their own generators to either sacrifice quality for speed or speed for quality.
61
+
- GPU support: This is especially tricky to think about.
62
+
Some forms of noise don't even make sense on the GPU (but lots do!).
63
+
As projects like WESL and rust GPU make more progress, I'd like to explore getting noiz on the GPU.
64
+
This is still a long way off but is something I'm looking into.
65
+
- Reflection noise types: As bevy editor prototypes and progress continues, making the noise types more customizable and changeable at runtime is important.
66
+
Adding more reflection support will help with this.
67
+
Designing this features is difficult without compromising speed, so don't expect this too soon, but know that it is in the works!
68
+
69
+
If you have any other requests, please open an issue or PR!
70
+
Feedback is always welcome as I work to make this the "go to" noise library for bevy and rust.
0 commit comments