Hi! I'm curious. How do you know that a pixel is "buggy"? Is this seen by looking at the screen, and if so, what are the symptoms? Does it happen with formulas other than Niekamp's? What is the cause of it? TIA. ----- Original Message ----- From: Lee H. Skinner <skinner@thuntek.net> To: Fractint and General Fractals Discussion <fractint@mailman.xmission.com> Sent: Sunday, May 18, 2003 5:37 PM Subject: Re: [Fractint] Multifractal
Hi Albrecht,
Easter_eggs { ; Time 0.29.47.49 <<
One of the best ones yet! Beautiful!
Wonderland { ; Albrecht Niekamp May, 03 <<
On this one, I ran into 1 bad buggy pixel (out of 1,920,000) about 2/3 of the way through line 458 of 1200. But I was doing it at passes=1. At passes=t, this pixel may have been a color fill-in pixel and not calculated directly. I do them all at passes=1, because passes=t, although faster, can introduce errors, and I guess I'm somewhat of a purist.
About 90% of the images I've generated have no buggy pixels at all. This one had one (and the image is not deep!). Some have had 20 or more bad pixels. The method I've used on ones like that is like playing an intensive video game. You must catch the showdot hitting the bad pixel within about a second or you'll have to start over with a previous saved good image.
This can be difficult while gazing at a complex image, so I use a special palette with color 0 black and all other pixels white, then replace the original palette when the image is completed. While babysitting the image, when the showdot stops, immediately save the image and exit Fractint. Restart Fractint with the saved image until you hit another bad pixel. If you miss it, you will have to restart again with the previously saved image.
In about a week, I should have several of these posted on a website.
Lee
_______________________________________________ Fractint mailing list Fractint@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/fractint