Feature request: Specify seed for initial Z value

[TheRedshiftRider]

Seeds seem to reset if large integer seeds are used, is there a current limit on how precise the seeds can be?

[Kalles Fraktaler]

the seeds are of double datatypes.
The dialog shows max 7 seven decimals, but you can specify a more precise value
Max value is not useful if it is larger than 2.
The AP library cannot have a too large value, since its puprose is to handle values less than 2

[TheRedshiftRider]

I have noticed values larger than two don't work. Im currently trying to prepare for a zoom I am planning to make. The zoom itself isn't any different but the final minibrot will be different. But for that I would need to use a seed value of 1.0E-100 or smaller which did not work. Would it be possible to specify the seeds in scientific notation?

[Kalles Fraktaler]

I have noticed values larger than two don't work. Im currently trying to prepare for a zoom I am planning to make. The zoom itself isn't any different but the final minibrot will be different. But for that I would need to use a seed value of 1.0E-100 or smaller which did not work. Would it be possible to specify the seeds in scientific notation?

Yes you should be able to enter "1.0E-100"
But if you open the dialog again it will unfortunately only display 0, since I display only 7 digits.
That's something that should be improved

[stardust4ever]

I'm just glad we have the option now. It's always nice...

[TheRedshiftRider]

Thank you.

[TheRedshiftRider]

I managed to get it working by editing the save-file.

[stardust4ever]

I managed to get it working by editing the save-file.

I'm glad he made it where you could just edit the file in notepad. In my "Dense Tapestries" video (inspired by Kalles Fraktaler's "Engine Block") I needed to set the angle to .15014 degrees, because with a 5.5 million percent stretch (55 thousand pixel aspect ratio) it did not display enough digits in the dialog box or in the saved file, but stored them in memory. 0.1501 and 0.1502 were both markedly skewed. Editing the save file was tempting, but ultimately I didn't have to as the extra "4" at the end was easy enough to type.

Perhaps for the HPDZ Buffalo, typing "0.5000000" followed by a wall of text worth of zeros up until the number of digits exceeds the precision needed, might fix the e30 bug. I have not tested this out yet. I noticed KF seems to always round down when calculating floats. You can tell in the numeric display in zoom movies, sometimes it reads for instance "3.9" instead of "4.0" when the final zoom depth was an exact power of 2 carried out to many digits.