Mandel Machine

[aleph0]

Thanks Botond, v1.2.3 starts OK for me. Will do some further testing tonight.

SeryZone - Try this page for SP1 and probably grab the ISO: http://www.microsoft.com/en-gb/download/details.aspx?id=5842

[Kalles Fraktaler]

Hello

I tried tick-tock, but it looks like it is glitches now?

Also, the attached location, Verstoppertje from Dinkydau, doesn't work at all...

[SeryZone]

SeryZone - Try this page for SP1 and probably grab the ISO: http://www.microsoft.com/en-gb/download/details.aspx?id=5842

I was set up SP 1 one day ago after advice!

Karl - Verstoppertje really have unsolvable glitches on 2-nd Julia. Mandel Machine don't have glitch solving by new method.

So, my proc. intel core i5 2400M support AVX2 but MandelMachine don't use it... Why?

[Botond Kósa]

So, my proc. intel core i5 2400M support AVX2 but MandelMachine don't use it... Why?

The reason for that is simple: my current CPU (Ivy Bridge) doesn't support AVX2. It would be possible to write and compile AVX2 code on it, but I would not be able to test it. That's a pity because AVX2/FMA instruction would yield another speedup close to 2x.

[Botond Kósa]

I tried tick-tock, but it looks like it is glitches now?

Also, the attached location, Verstoppertje from Dinkydau, doesn't work at all...

I see no glitches in tick-tock, could you attach an image?
Verstoppertje is completely broken in Mandel Machine, and I don't know the exact reason for it. It renders correctly with perturbation turned off. One of the optimizations might break the image, I'll have to investigate it.

[Kalles Fraktaler]

I see no glitches in tick-tock, could you attach an image?
Verstoppertje is completely broken in Mandel Machine, and I don't know the exact reason for it. It renders correctly with perturbation turned off. One of the optimizations might break the image, I'll have to investigate it.

I have attached a comparison. Seems that the glitch only occurs in the original ratio 640x480. Image from MM on top, no additional references are added in KF.

Karl - Verstoppertje really have unsolvable glitches on 2-nd Julia. Mandel Machine don't have glitch solving by new method.

No it is not unsolvable. So far I have not found any unsolvable glitches. KF need 4 references in 640x360.

[stardust4ever]

If you encounter crashes on a regular basis, please let me know the details. Also be aware of the known issues described in the changelog, the most important being the application may hang when adjusting a parameter during calculation - always cancel the calculation first with the Esc key before changing a parameter.

Yep, that's exactly what was screwing it up. I am constantly tweaking the params, LOL!

Another issue which is easily reproducable: When zooming into certain regions, ie seahorse or elephant valley, the extended float precision fails about 60-something zooms in and the image is badly pixellated. Note I have not observed this in the needle area, just locations with lots of spirals. Currently the workaround is to manually select an arbitrary precision, zoom in, sufficiently deep, then reset to "auto."

Another bug I discovered: I tend to like big renders but am running into issues. 14400x10800 works but 19200x14400 bugs out the software. I'm running a 64-bit AMD on windows 7 desktop and 8.1 notebook. Both PCs are pure 64-bit and both have 8 Gigs RAM. Above some preset amount of megapixels, the software fails to render. I can still save my progress but must close and reopen Mandel Machine to continue using.

PS - I'm glad to have the option to selectively load pieces of the parameter file. That way if I save using parameters that don't work (for instance ginormous image size), I can still reload the rest of the data.

[stardust4ever]

Silly me. There is a new version (v1.2.3) of Mandel Machine posted as of August 11th. 5300 zooms, w00t!
http://web.t-online.hu/kbotond/mandelmachine/#changelog

Thank you so much for this update! Off to download...  

I got a problem with extremely large renders. I rendered an image @19200x10800. When I try to save said image, I get an empty PNG file (0kb). PNG saves fine @12800x7200.

[Botond Kósa]

A new beta is available, addressing a few recently reported bugs:

• Tick-tock location is now rendered correctly, without glitches
• Verstoppertje location was completely broken previously, fixed now (automatic glitch correction is still disabled though)
• The saving of PNG files runs a little faster now and consumes less RAM, enabling to save images up to 19200x10800

[stardust4ever]

I discovered a weird anomaly with disconnected locus at 4551.131 zoom levels.

Curious bug (it displays in both versions 1.2.3 and 1.2.4), but fortunately upon zooming in further, the anomaly disappeared allowing me to continue the zoom sequence.

Zip contains the .mmf parameter file.

[stardust4ever]

Anomaly II. I have a feeling these will become more frequent the deeper I zoom... 

[stardust4ever]

Derp. 

[Botond Kósa]

I discovered a weird anomaly with disconnected locus at 4551.131 zoom levels.

Curious bug (it displays in both versions 1.2.3 and 1.2.4), but fortunately upon zooming in further, the anomaly disappeared allowing me to continue the zoom sequence.

This might be caused by some over- or underflow in series approximation (turning off SA fixes the image). Reminds me of the patterned glitches in Dinkydau's Flake location.
Will be fixed in the next release.

[Chillheimer]

you know guys, if this "glitch" works and doesn't do any harm, PLEASE don't see this as a glitch or a mistake you need to correct!
See it as Evolution! There has been a strange mutation in the formula! creating something new!

You should feature it! Try to push it further! Try to make it repeat and evolve itself!
A really NEW branch of the M-Set. And you want to "correct it"?! Noooooooooooooo!!!!

Why always "perfect" things.
zooming into the m-set is so diverse, but in can become boring, as the main patterns always nearly stay the same

THIS is something DIFFERENT.
I see it as EVOLUTION!
By random mutation, just as it happens in the real world.
Mistakes aren't bad, if you make the best out of them and improve on them.
Now Botond, please, make the evolution conscious and don't kill of the first spark! Let it grow, let it branch, let the m-set become multifractal!

[youhn]

Sounds pretty much good to me, since I'm all for variety and evolution. But it's probably not random, but offspring from the calculation method.

The magic of fractal formulas is in part that different programs can generate the SAME output, even for unexplored areas. I would rather keep this strength. So maybe branch off the programs which exploit the wonderful shapes caused by approximations/calculations? Maybe help the mutations a bit, by giving and offset to the values every ... hmm ... few millions iterations (on the whole zoom path). Then I would also like a way to store these deviations, as some kind of DNA.