That's the thing on the right. It's just a preview, the final export will be of higher quality. Scroll to zoom, drag right click to pan. If you are on mobile, switch to desktop.
The size of the canvas. Not the size of the final render, this is just a preview.
x:
y:
The amount of times the algorithm loops. Higher values cause more detail in certain areas, lower values can reduce noise. Find a balance for whatever shot you're trying to get. Or just leave it at the default and never look at it again.
The amount of samples to get for each single rendered pixel. High values mean high rendering intensity, but also more quality and less noise.
Does something, the fuck do I know. I'm no omnipotent being. That's up to the creature in my basement.
These values are responsible for controlling the shape and appearance of the output structure.
a: This parameter is responsible for an effect somewhat close to pinching in and out of the structure.
b: This parameter is responsible for "condensing" or "spreading" the structure, with values close to 0 meaning it is more condensed.
c: This parameter is responsible for the amount of "petals" the structure has, heavily modifying the petal structure. g does this without changing the petal structure much. The amount of petals will always be c-1.
d: This parameter is responsible for ...something. It changes the colors slightly, and around small values also the structure, especially on the outward ends.
e: This parameter is responsible for an effect as b, but creating entirely different effects.
f: This parameter is responsible for a similar effect to a, except in its fully own way.
g: This parameter is responsible for changing the amount of petals just like c, except it preserves the petal structure pretty well. Petal count is multiplicative, not additive. Use multiples of 1/c for clean results.
h: This parameter is responsible for... something? It changes the shape of the structure is the only thing I can say for sure.
i: This parameter is responsible for twisting or turning the structure.
j: This parameter sucks. Besides that, I implemented it in a way that it only applies if the value isn't 0. Just don't use it, I guess.
Skeleton mode displays a b/w render that may often reveal different structure, hence the name "skeleton".
Skeleton's clamp fix implements a fix not present in old versions often causing skeleton renders to not be able to be multisampled correctly, causing multiple quality issues. As I liked the stylistic aspect to some degree though, I decided to make it toggleable.
Import a preset from a link. You could also just paste the link in your browser, but hey, we all feel special sometimes.
Import a preset from an exported image. Must be the original, when converted or resized the preset will get removed most of the time. You can also just drag and drop the image into this tab.
Render and export a high-quality image based on the preview inside the canvas. Configure the options as you wish, the export button is at the bottom. Expect the process to take a bit, especially for chunked high-resolution renders.
The resolution the final image will be exported at. Can be any size, although chunking is advised (even required) at big scales. Size limit with chunks is currently the browser canvas size, although for extremely high resolutions (~5 digits), you should turn off chunk merging, and merge them yourself. What's that? There's no option for that? Too bad, I haven't implemented that yet.
x:
y:
Whether to do a chunked render. If off, everything will be rendered in a single pass. If on, rendering will be split into smaller chunks.
Only does something if chunked rendering is enabled. The resolution of the individual chunks. Final resolution must be divisible by chunk resolution. How else do you expect me to fit the chunks inside the image properly?
x:
y:
Enable 2x Supersampling-Antialiasing, using the lanczos downsampling filter. Drastically increases image quality, reduces noise and artifacts. Has to render everything at 2x scale, so think about halvening your chunk size if you want roughly the same computational load.
Embed the preset link inside the exported image. This saves you the work of additionally saving the preset link. Preset link may or may not get preserved when sending or converting the image. Embedding does not happen via EXIF metadata, it instead just gets appended at the end of the file.