HEIFs are about 1/3rd the file size of PNGs, which are the smallest lossless files Ultra Fractal can write.

I’m converting the PNGs to HEIFs with another app but it doesn’t batch-process very well. It’d be sweet to have lossless HEIF right from UF. Even better if the files are saved with the .heif extension not .heic because Final Cut Pro and other apps don’t recogni

In arbitrary-precision arithmetics, the sign of the result of trigonometric and exponential functions is sometimes wrong.

Here's an excerpt of a formula printing some debug results:

complex m1 = exp(flip(#pi))
print("exp(i * #pi)=",m1)
float sin1=sin(#pi)
float cos1=cos(#pi)
print("cos(#pi)=",cos1, ", sin(#pi)=", sin1)
When I run this without additional precision, I get the following res

Something curious is happening. Here's an exported image from UF. Looks right.


Here's what I get when rendered (normal anti-aliasing, forced linear drawing).


Noticeable differences, not subtle. Not solved by changing anti-aliasing parameters or precision. And if I render the same thing again, different results!



These are done with all 12 of my CPU's cores (6 real co

When rendering animations with motion blur, all is well for the first 90% of each frame. This is when UF is calculating the fractal and antialiasing. The four CPU cores are maxed out and the CPU is 0% idle, as shown below on Activity Monitor.



But then comes the final 10% of the frame, which is when motion blur is being calculated. UF suddenly gets a lot slower. The CPU is 70% idle.

In a float param block, the compiler allows

default = 1/#magn
which can be useful, but doesn't allow

min = 1/#magn
which also can be useful.

Also the help entry "min setting" has a typo. The sentence "If this setting is not specified, there is no maximum value for the parameter." Obviously it should say minimum.

Here's a fractal with 100% of points Inside; no points reach the bailout criterion. The Statistics tab says that the Min and Max iterations are both zero. I would have expected that both Min and Max would be set to #maxiter.

This is either a bug or a feature.

Here's an example:
/>test {
fractal:
title="test" width=800 height=600 layers=1
credits="Jim Blue;10/5/2022" ant

Currently #numiter is readable only in the Final section of a ucl coloring formula. It is not even readable in the ResultIndex function of a ulb Coloring formula, where one might expect to be able to use it.

If #numiter were readable in any coloring formula, whether in a .ucl or. ulb file, some interesting coloring options would be available. For example, if coloring according to distance fro

Hello,

I just ran into this new problem. When I render to disk in high resolution, it tells me that I have to render in tiles because the image size would exceed 2 GB. This didn't happen before. Just to make sure, I tried to re-render an older image which previously worked, and UF is now also refusing to render it.

In one instance, the predicted file size was around 900 MB, the sum total

Here's a test case, a base layer all white, a second layer with a small black dot in the center. (The fractal where the problem came up was more complicated!) The black dot is a circle with a radius of .01 in a window of width 4, so at 800x800 it's 4 pixels wide and shows up clearly in the UF window, with or without anti-aliasing.

Problem: sometimes the rendered image does not show the black

I would like an option to turn off all the sounds.

Currently (on Windows) when I exit a fractal without saving it, or save over an existing upr or render over an existing image, a window pops up and Windows Background.wav plays. The popup without the sound is sufficient.

(Preference/Fractal does have options to turn off the sound when the fractal window finishes and when a render job fin

When loading an old fractal after changing my formulas (without proper attention to old fractals), I got this error message:


In fact, the missing parameter is not in SwitchComboFormula in jlb.ufm. SwitchComboFormula calls SwitchCombo in jlb.ulb, which calls Mandelbrot in jlb.ulb, which has the missing parameter.

If the error message could be improved, that would save some debugging

Hello,

I upgraded to UF 6.04 today and every time I open the explorer window for any parameter I get a huge CPU spike. This happens even if my mouse is nowhere near the window and nothing else is rendering. This takes several seconds and despite having a 12C/24T CPU it drains my computer of resources to an extent that even the playback of windowed Youtube Videos starts to stutter.

Oddly e

Hello!

I'm currently rendering a fractal that told me it would take 8 hours initially, quickly rose to 9 hours, then 10 hours. Now it has been running for almost 3 hours and it still predicts between 9 and 10 hours.

Here's my guess of what is happening: The fractal is basically a spiral with the highest iteration counts toward the center of the image, so I would expect the rendering to sl

Hello,

I recently ran into the problem of wanting to use the switch to Julia mode on a pretty multi-layer fractal. It would be great to have a way of using all layers for the new Julia fractal, rather than just the active layer. I get that it's possible to do them one by one and copy-paste them into the same window, it just seems a lot more tedious that it has to be.

Best regards,
Phi

Hello,

I'm not sure what this isn't a thing, when using the explorer I can press escape to exit, but when I'm in eyedropper mode, this doesn't work. It should be straightforward to add this and would make it a lot more convenient.

best regards,
Phillip

(I may have asked for this before.)

When debugging a formula, I don't need 15 decimal digits of precision in a printed line to see what's happening. A setting like
$decimals 4
would be nice to have. Not necessary, but nice.

This coloring UCL file is supposed to detect period of an orbit, and assign color index accordingly. Testing on plain mandelbrot set gives a noisy result (can't attach image here I guess, any color map, linear 0.1; values are in 0-20 range). I can see nothing wrong with the code and I have turned of guessing, normal periodicity checking, messed with tolerance, max iters, even tried extra decimals

Hello,

this one might be a low priority one, but it's something I noticed and thought I should let you know. From what I can tell, UF uses image pixel column count to separate the image into pieces that are being worked on by each thread. This works fine in almost all cases, but I encountered something interesting. If only a small area is left for calculation, and it is comparatively narrow,

This is an example of what has happened to me any number of times while developing plug-in formulas.

I changed a couple of parameter names in a plug-in. When loading an old upr, I got this message:

The mistake is actually in a plug-in of a plug-in of a plug-in, but the error message refers only to the top-level formula, which is not in error. The missing parameters are not in the top-

This fractal has "dirt" on it (speckles). If you zoom in on the mandelbar the noise pattern changes so it's not correct. I tried everything with bailout and even added precision but the problem remains. Actually with added precision the picture completely disappears.
I guess I can't attach here, so I'll give upr and Bugs.ufm below,

````
/>bug1 {
::8s1Schn21J1yutNMQw7CQ/DE8elpolss