So I'll do that - but for now, I'm going to share with you my discovery of how to improve the state of your fractal if it's full of annoying little noisy pixels. As an example, I zoomed into an appropriate area using the Amazing Box formula, with lots of pixelation happening along the edges and in various spots, etc.
Now before I start, let me tell you this: The better you want your image to look like, the longer it will take to render. As I'm sure you already know, when you use the "preview" mode to render, it goes quickly, but the image is often riddled with pixels. As you go up in quality, using the "Video", "Mid" and "High" modes, renders take longer but the pixels start disappearing into nice smooth satisfying surfaces/curves.
(Something to note is that, sometimes (really, not always) a render with "High" mode comes out looking very different (and usually much better-looking) than in "Preview" mode. So do not give up after "Viewing to Main" once. Try Video and Mid, see if the fractal changes for the better, etc)
Something else very important to note is that often, as I'm sure you've already encountered, what you see in the Navigator window is not all what comes out in the Render window. This is just one of those things... Sometimes, it'll just be the colouring that's different, and sometimes, it's the whole shape of everything, as is the case with the example I used for this Tut page. In fact, let me start here. I said I used Amazing Box:
|Zoom somewhere in Amazing Box in navigator window - 20 iterations|
|The above image, rendered in Preview mode|
Not very nice, you know. Still, what can we do to this to improve it a little? I tried simply rendering it in "Mid" mode:
Aha! Much better, even if not good yet. So now, have you noticed the numbers changing in the little "Calculations" tab every time you changed from one mode to another? From Preview to Mid, for example. I decided I wanted to try changing them myself instead of choosing "High" .. So I kept it on "Mid" and just changed the Raystep multiplier and Stepwidth limiter values (see image below).
I changed them from the values above to 0.1 and 0.1 (which are even lower than the default settings of High Mode) and got this:
Much better! But still rather visible pixelation... If we lower the values even more, say 0.05 for both of them.. :
Almost there! The pixels are STILL visible though. So I dropped the values even lower, to 0.02. :
And voila! No pixels. But remember:
The lower you go with those two values, the longer the render is going to take. My first render of the above image in Mid mode took only a few seconds, whereas the above one took around 12 minutes. So if you have some awesome fractal image loaded, at 4000x3000 resolution, and try rendering it with Raystep Multiplier and Stepwidth limiter at 0.02, expect to wait a very long time for your render! ... I tried it, and ended up with something that took 21 hours!
The good news is that my above example here I chose for this tutorial page exactly because it had a lot of pixelation. This is truly not always the case. Most of the time you'll probably only have a little bit, so then you can lower the values little by little, until you're happy with the quality. If some pixels persist but you really don't want to wait for another long render, then Photoshop to the rescue! Manually sorting out those pixels can often be a much easier solution.
If my tutorial is helping you, please consider supporting me over at my Patreon page.
I also have a deviantArt gallery.
Next Mandelbulb 3D tutorial : Julia Mode