At 10:55 PM 5/19/03 -0600, Lee H. Skinner wrote:
Ricardo M. Forno wrote:
Hi! I'm curious. How do you know that a pixel is "buggy"?
After the showdot hits a buggy pixel, every pixel after that is colored the same. And the showdot usually slows down as if every pixel had the value maxiter. And it continues if you change passes or resolutions! You have to exit fractint and then restart it. I've not seen it in other than the multifractal formula. I'm told it only happens at 1600x1200. So far, no one knows the cause.
Maybe I'm barking up the wrong tree, but when I have encountered this it is usually caused by periodicity checking and can be cured by turning it off. What the exact cause is I have no idea. It occurs under certain conditions (hitting a point inside the set, plus some unknown factor) with certain fractal formulas (my "gravijul" being one). Aloha, Bud
Mark Christianson wrote:
Maybe I'm barking up the wrong tree, but when I have encountered this it is usually caused by periodicity checking and can be cured by turning it off. What the exact cause is I have no idea. It occurs under certain conditions (hitting a point inside the set, plus some unknown factor) with certain fractal formulas (my "gravijul" being one). <<
This behaves differently than periodicity checking. Once the bug occurs, EVERY pixel is returned the same from that pixel on until the end of the image. If you change passes mode or image resolution, every pixel in the new image will be the same. If you do a save immediately upon hitting the bad pixel (there may only be 1 or 2 such pixels in the whole image!), exit fractint, and then restart with the saved image, the image will continue normally. Lee
participants (2)
-
Lee H. Skinner -
Mark Christenson