Cloning and saving modifies textures

[davidh]

1. create a texture using the Texture transformation
2. use Clone Entire Branch to duplicate the texture -> you get a modified darker version of it

The same happens if you save the texture into a (workspace)script and then open the script.

To get the texture unchanged you need first to save it as an image and then save it as a part of the script.

[jsachs]

Yes, the Texture transformation generates a new random texture every time you use it.

The current algorithm does not permit re-creating a given pattern since it splits the image intro strips and computes them in parallel so there is no way to know what order the pixels are computed in. The CUDA version that uses a special random number generator that I do not have control over. Theoretically, I could create a much slower version that ran in sequence and then save the initial random seed in the command line so the same pattern would be generated every time.

So, for now you need to save the texture in a file if you want a specific one.

[davidh]

If the Texture transformation generates a new random texture every time you use it, there is no need for the Settings button with the commands as neither of them does what it is expected to do, which is misleading. If you hit a really good texture, unless you know you have to save it as an image, you will lose it and never recreate it for future use.
Perhaps a warning with the option to save the texture in a file once it is created might be another solution.