In mb3d formulas are executed in the selected order with the selected iteration count so you can do eg 3 iters of Mandelbox, then 1 of Menger. afterwards restarts with 3 box 1 menger etc.
So you can do 3 iters of Mandelbox, then 1 of Menger, repeat from Mandelbulb. afterwards you will calculate only mandelbulb for all following iters.
So it looks like it's exactly the same. How DE is calculated for hybrids? Is it just "delta DE" algorithm?
- the ability to hit undo after crashing: it already saves auto-recovery information. When you restart information there should be message with question about recovering of settings. Is this doesn't work or you prefer to have something like was in od Mandelbulber?
Didn't see such a message. Maybe has to do with the fact, that I did not install v2.05, only downloaded zip file and extracted to program folder of 2.04.
Crashed reproducible after pushing an arrow button in a quick sequence (no matter what arrow). Window stays in the state like in attached jpg and remains operational (tooltips work, arrows changes coordinates etc.) but rendering does not start (0% cpu).
as far as speed goes, when compiling for yourself you may as well add -march=native to take advantage of simd and any other instructions added to modern cpus in the last 30 years i personally also roll with -Ofast, which enables -ffast-math and the like. i dont know how buddhi feels about that. personally i figure if a computation is going to behave badly once in a while its going to happen anyway, id rather have the speed improvements than the strict IEEE compliance.
If anybody wants to optimize code for his machine it just enough to export CXXFLAGS=-march=native (that flags are not hardcoded in .pro file). Only which is hardcoded is -ffast-math flag (enabled by default to speed up floating point operations and doesn't make problems on different platforms).
interjectionDidn't see such a message. Maybe has to do with the fact, that I did not install v2.05, only downloaded zip file and extracted to program folder of 2.04.
I see. The problem is that the program doesn't crash, but just hang. I will try to fix this problem.
there is a good explanation by luca on how mandelbulb3d works with custom alternation of formula based on iteration number.
In respect to the current MandelbulberV2 it has 4 formula tabs (V 1.## had 5)and more could be added. More would be useful with boolean operators, however with hybrids more often means more difficultly with quality.
It is very likely! Jesse was a close follower of your program.
But I never checked that. Anyone can?
in CalcDEfull there is something about hybridization.
as i read this "..Even running OpenCL on my old cpu was faster, but then it is only single precision." i think, it is not possible to get OpenCL with double precision ??
Mandelbulber Version 1.21 has OpenCL single precision. I think it may have been because of the limited amount of GPUs that could run double precision .
I do not know if when OpenCl is added to MandelbulberV2, whether it will be double precision, but I hope there is a way to choose between single or double precision. For me the speed of single precision OpenCL is what I like, I assume double precision would be a bit slower.
with consumer cards its more like 1/3 - 1/8 or even far worse with Nvidia cards.
when it gets to implementing new opencl shaders we will certainly take double precision into consideration.
only an marginal benefits over an consumer card - in DX it is slower as the actual cosnumer top modell - and even this is much cheaper ..
In openGL it depend on the app - maya is at best 20 times as fast as with an consumer card .. this is nice - but only few apps get this hugh performance boost from the highly optimized drivers .. most times i get 1,5-2 times faster as the "same" consumer GPU.
On the good side, it is nice to have GFX on an 4K 60Hz display in 10bit ... and i get an good support from AMD if i need it..