Minor Update - v1.0.2 Fractal Generator Improvements

This updates contains a variety of changes and improvements to fractal noise generators and their associated monobehaviour components. fractal noise generators can now use multiple textures as their input and will change textures each octave if possible. If fewer textures are provided than the number of octaves the final texture will be repeated for all remaining octaves. Furthermore, the inputs are no longer required to be render textures, but now can be any object inheriting from the texture class.

The monobehaviour component provided for using the fractal noise generator has also had its inspector updated. This update adds the texture preview feature added to other monobehaviour generators in update 1.0.1, as well as a switch to change between using a separate monobehaviour generator to create the texture input, and selecting texture assets from your project files to use as input. A slider for the desired number of inputs has also been added (if the inputs are being generated the seed will be incremented for each of the textures)

Going forward it is strongly recommended that input textures are provided to a fractal noise generator directly rather than providing it with a separate generator object to use. While using a separate generator object is currently still supported, that support will be removed as of the patch 1.1.0, anticipated to be released in the first week of January. When using a monobehaviour component for fractal texture generation, creating input textures through a separate component will continue to be

Changelog

1.0.2 - 12/5/22

• Added support for multiple textures as input to a fractal noise generator as well as input textures which are not RenderTextures
  • A new input texture will be used for each octave of noise if possible.
    • if fewer input textures than the number of octaves are provided, the final input texture will be reused for all the subsequent octaves.
  • Methods have been added to set a list of textures as the input for a fractal noise generator, as well as methods to add individual textures as additional inputs
  • An additional constructor for FractalNoiseGenerators has been added using a list of textures as an input.
  • An additional constructor for FractalNoiseGenerators has been added that only sets initial texture width and height, without an input initialized
  • Controls have been added to prevent input textures from having a different size than each other or the final noise texture
    • If texture size is changed after construction the current input will be discarded
  • Controls have been added to prevent a fractal noise generator from running with inputs set unless its constructor used an additional noise generator object object for generating textures
  • Due to the increasing number of ways to use the fractal noise generator object (with a separate generator to create its input, with a single input texture, with multiple input textures) support for using fractal noise generators without pre-generating an input texture will be sunset in 1.1.0
    • If you use fractal noise generators that don’t use pre-generated textures, you will need to migrate to ones that do before 1.1.0 (this should be after one more minor update, 1.0.3)
    • You can do this by replacing the additional noise generator object you where using in the fractal noise generator’s constructor with a list of textures, or an individual texture, generated separately.
    • Alternatively you could replace the generator object with the size of the final noise texture and set the inputs post-construction
• Added the ability to use Texture2D assets as input to a fractal noise generator component
  • Unlike with the underlying generator objects, fractal noise components will maintain support for using a separate component to generate the input texture
    • this is due to the greater control its inspector gives over how it is used and the more predicable lifecycle bounds
  • Currently all texture assets must be the same size
  • The full collection of texture assets must be emptied to change them once selected
• added various features to the inspector for fractal generator components
  • added the texture preview feature introduced to other generator components in 1.0.1
  • added a slider to set the desired number of input textures to use, up to the number of octaves
  • added the ability to switch between using a separate generator component and Texture2D assets
    • added a field to add texture assets as input if that mode is selected
    • currently to change the selected texture assets the list of assets must be first cleared