last week i got an error when I tried to start UF version 5. I had been planning to upgrade to version 6, and I thought this might solve the problem, but it persisted following the new installation.

Liesbeth posed basically the same question in January.

Liesbeth Quak
https://www.ultrafractal.com/forum/index.php?u=/user/profile/10posted Jan 5 at 3:52 pm

She was able to fix

Hello,

I'm on a roll, so here's a 3rd post. I have intermittently run into an error message when using the explorer to vary color density. This happens when something else (preview or job) is also rendering at the same time. As I move the mouse back and forth over the explorer window, errors occasionally pop up, usually complaining that something is not a floating point value:


Th

In the Formula window, bool params have their caption to the right of their check box. If the check box were to the left of the window, there would be room for a longer caption to be visible.

A very minor request for the next minor release.

Thanks to Frederik for this terrific program.

I tried changing fonts in the formula editor from the default Consolas to something else, like Times New Roman or another serif font. These other fonts are not mono-space, but they display as if they were mono-space, fixed-width and ugly, so not really usable. Of the Windows fonts, only the true mono-space fonts—Consolas, Courier New, and Lucida Sans Typewriter—are useful.

Not a b

Hi, after I downloaded UF6 on my new pc I get a bug report and can't open the program. What could have happened?
Here is the report:

In the Range field of the Exploring tab, I can't enter a number like 1e-7 or 1e5. However, if I enter .00001, UF changes this to 1e-5 and I can edit the number.

Also in the Range field, I can't enter a number like 1.5, as the decimal point is immediately deleted. However, I can enter .5, which UF changes to 0.5, and I can then change the 0 to 1.

This behavior seems limited to the Range fi

Hello,

I'm pretty sure this isn't intentional. The anti-aliasing in the working window has become noticeably worse in the latest version, to the point that I had to double check whether it was active at all. Here's an example comparison:
It's even more obvious with the default image, but i haven't saved a copy of that from the older version.

Best regards,
Phillip

Hello,

I was about to explore the Mandelbrot set when I ran into a glitch while rendering. It looks exactly like the kind of artifact I get when periodicity checking fails. I can usually just turn it of, but this was using perturbation (precise).

Here's an image:


The problem occurs only in one of the two layers (the one that uses Triangle Inequality Average)

Parameters:

gl

Hello,

I recently worked on a few relatively slow rendering fractals and I frequently run into previews that take serveral minutes to render. However, I can already see what I want and I would like to use the explorer to change parameters. I know I can turn off AA and/or change the size of the image too.

It would be awesome if we had a button to pause the automatic rendering of the previe

My default upr uses SwitchComboFormula in jlb.ufm plus JLB_SwitchFormula, JLB_SwitchCombo, and JLB_MandelbrotSFormula in jlb.ulb. I had a typo in the Mandelbrot,
default = 1"
in a parameter block. When starting up UF, I got a large number of confusing and not helpful error messages, as in the screen shot below.

When the (blank) fractal loaded, I clicked on the top line, SwitchCombo

This .upr runs in a few seconds at 640X360.
On 6.02 it takes about 3 hours at 19200X10800 (no AA).
On 4.03 it takes about 10 mins at 19200X10800 (no AA).

dot25 {
fractal:
title="dot25" width=640 height=360 layers=1
credits=""
layer:
caption="Background" opacity=100 method=multipass
mapping:
center=0/0 magn=1.3
formula:
maxiter=1000000000 filename="Standard.ufm" entry="FastJuli

Why do I get this blurred distorted coloring? An inverse julia zoom:

MandelbrotJuliaZoomIncorrectColoring {
fractal:
title="Mandelbrot Julia zoom incorrect coloring" width=800
height=600 layers=1 credits="Kathy;6/23/2020"
layer:
caption="Background" opacity=100
mapping:
center=0.000993846291914812695705/0.000381483804274999567745
magn=1.2142773E10
formula:

log(1.20515621346031e463) outputs INF in normal precision, NAN in extended precision (tried with up to 1e6 extra digits).

In the default section of a formula, I would like to be able to do the commented line below but the compiler does not allow it:

int param n1
min=1
endparam
int param n2
min=1
max=@n1 ; compiler says invalid setting
endparam

Rendering animations to png image sequence usually has several unfinished images. This also happens often when just editing a fractal. Refreshing zoom then gets rid of it.
Typical example included.

Just purchased Ultra Fractal 6 Extended Edition and loaded up the animation example. Clicked run and in a few seconds it crashed. Not off to a good start.

Win10 v1909, GeForce GTX 1080 Ti (442.74) 64 Gb DDR4 Mem.

Any idea what's causing the black to appear over the fractal image? I suppose one of the variables is out of range but I happen to like the design I'm seeing on screen and don't wish to vary it too much. Thanks!
Params:

LambdaJuliaWithBlackStripe {
fractal:
title="Lambda Julia with black stripe" width=800 height=650 layers=1
credits="Kathy;12/31/2019" antialiasing=yes

I usually render to disk with a resolution far higher than that of the fractal window. Sometimes, this means that perturbation mode would probably be used for the rendering, but I have no way of setting the precision level because it's only shown when that mode is also used for the fractal window.

Hence, I'd either suggest such an option in the rendering dialog, or to make the perturbation pr

Doing an animation of a zoom. Occasionally I get a bad frame, like this one. What happened? Details available upon request.

I've tried to reproduce the image posted here but failed, even at the "Precise" setting for Perturbation: essentially, the whole center is 'missing'. While such problems can always occur, I thought I'd report this in case you want to make the algorithm a bit more robust.

Re = -0.1539465335054964690901834505221291075155694452817396340987201
Im = -1.030516765000659787821940789035664424026379794